PostClientFlow - Shared Flow

[#1]

Hi,

Need to implement Message Logging Policy in my Api's. Can I create a SharedFlow with Message Logging Policy and use that in the PostClientFlow

Can you let me know if this is achieveable?

Thanks in advance

Sample

<PostClientFlow>
<Response>
<Step>
<Name>FlowCallout.SharedFlowLogging</Name>
</Step>
</Response>
</PostClientFlow>

Exception Received

Bundle is invalid. Errors:[Entity : PostClientFlow, FlowCallout policy is not supported in the response flow;].

[anilsr]

@Deepa , Thank you for highlighting same.

Looks like it's a bug with UI. Can you try below, It worked for me.

• Create a new revision after you see above error.
• Deploy new revision, It should work.

[anilsr]

@Deepa , I have created a ticket with engineering, MGMT-4122 , Till it's resolved, use above workaround.

[#4]

This is a good feature but @Anil Sagar do you know if the functionality works? I tried this earlier and trace doesn't show the messagepolicy at all, it only shows the flow callout in the trace but not the message logging policy. Can you confirm?

[#5]

Yes Maruti...I don't see the policy getting involved when saved as per Anil

Anil can you please confirm

Thanks

[anilsr]

@Maruti Chand ,

Yes, Trace does show. Follow below steps.

• Drag & Drop Flow Callout to PostClientFlow response
• Try to save, It will display error.
• Create a new revision, Deploy it again.

See screenshot below.

[#7]

I don't have issues with the deployment but It shows the flowcallout in the trace but not Message logging policy, do you see that?

[udayjoshi]

This is fixed in private cloud 4.19.01. Edge cloud should already have this fix.

[#9]

@Anil Sagar

I am also experiencing the same issue. I created a proxy and used a shared flow with the message logging policy which is deployed on Prem with version 4.17.0.1.

When I called my proxy I am getting an successful 200 response but with in the trace i could see only the Flow Call out policy and no Message logging flow.

I have followed the steps that are explained above and have created many revisions and deployed, but still I see the same issue.

Could you please let me know if we are missing something in the policy.

[#10]

I am facing the similar issue as you @Kishor.

Were you able to resolve it?

[malenkavanommen]

Facing the same issue. The flow callout policy is visible in the trace, but clearly the logging policy is not executed.

[#12]

Similar issue here.

Shared flow is shown in the trace, but never executed.

Tested it on post flow to check if shared flow was working, and it was.

Is there any ways to solve this?

[udayjoshi]

This is fixed in private cloud 4.19.01. Edge cloud should already have a fix.

[bhatikuldeep]

That's super, just checked on cloud and it works! Many thanks for the update @Uday Joshi @Google!

[udayjoshi]

@Kuldeep Bhati Do you mind sharing a trace here for larger audience ? TIA

[bhatikuldeep]

@Uday Joshi @Google, Here it goes!

I am working on a git repo to include this proxy and SF as an example to demonstrate this flow; will share repo link later on for the community.

[udayjoshi]

Thank you @Kuldeep Bhati The image is broken. Do you mind re-uploading ?

[bhatikuldeep]

@Uday Joshi @Google humm, I was sure that I uploaded the screen shot, never-mind, uploaded again 🙂

[udayjoshi]

@Kuldeep Bhati

Thanks much !

[nagashree_b]

@Uday Joshi @Google

Is this feature also available for on-prem 4.19.01?