0% found this document useful (0 votes)
50 views2 pages

Parentand Child Case

Upon submitting a child case, the flow transitions to the parent case if both share the same flowaction name. If the flowaction names differ, users must manually navigate to the parent case after completing the child case. This behavior highlights the importance of consistent naming in flowactions for seamless transitions.

Uploaded by

hello
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
50 views2 pages

Parentand Child Case

Upon submitting a child case, the flow transitions to the parent case if both share the same flowaction name. If the flowaction names differ, users must manually navigate to the parent case after completing the child case. This behavior highlights the importance of consistent naming in flowactions for seamless transitions.

Uploaded by

hello
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

On clicking Submit, I am taken to the next assignment of the parent flow.

Observations:

I have noticed that if the child case and parent case have a flowaction name that is the same (in this
case Approve- even though the sections vary), the flow automatically switches from the child case to
parent case. If they vary, once the child case is completed, you will have to click on the link to the
parent case on the top to get to the parent case’s current assignment.

You might also like