I have Parent Case P1. Child Cases C1 & C2. C1 is created from P1 from Case Designer - One Of Stages in Parent Case P1. Till C1 resolve, P1 case status: Pending-C1. As soon as C1 is resolved, C2 should create immediately. Till C1 resolve, P1 case status: Pending-C2.
Parent Case P1
Update Status P1( Pending-C1)
Create C1 case
Flow F1: start ==> Wait ( Config: Case Dependency. Case: C1. Scope: Org-FW-SampleApplnFW-Work-C1)) ==> Update Status P1( Pending-C2) ==> End
Stage 2: (Tried with : Automatic transition/Wait for user action)
Thank you for your question. Is this question directly related to the Lead System Architect course? If not, I can transfer this question to the Product Support Community where a subject matter expert can help you.
Thanks for your rapid reply. Actually, the post for LSA 6.2 - LES Corp Online Shop Case Study.
The Requirement is,,
Direct Order- Parent Case
Fulfillment- Child case. Keep parent in Pending-Fulfill till Fulfill is resolved.
Shipment- Child case.Auto create it once Fulfill is resolved. Keep parent in Pending-Shipmment till shipment is resolved.
Please find attachment for more info. My understanding on case study is, We have to make halt the Parent Case till Fulfillment. Once Fulfillment is resolve. Syetem will do auto create shipment case. Now make Parent case halt till shipmen is resolved.
We have three approaches,
1. Create Orphan Workbasket assign with orphan flow action connector. Raise ticket from Child case. But need obj-refresh-lock on Cover before set ticket. So I am not considering this.
2. Create Wait shape. For this only I post this questions. What I did is in flow is
1. Create Fulfillment case
2. Wait shape: Case Dependency is Fulfillment is resolved.
3. Assign-1 ( some other UI Actions)
Here Once Fulfillment case created, the parent case is not in halt , autmatically moving to Assign-1. But one good observation I see here is, Though we submit Assign-1 UI action but UIAction is same screen flow is moving. But still, My understanfding is ti should not open assign for Assign-1.
Once more question here, Wait shape is good option ? Here we have to WB assign. Who create online order/who following may be best to assign. But Wait shape not accomdate it. So we may put some common WB. Make available to WG.
3. Create infinite WL assignment action untill Fulfillment is resolved. Here we can make assignment to order maker/order follower. I decide it as good option. But the When AllCoverResolved Can not apply here to decide whether Fulfillment is reolved or not. Because once fulfillment is over. System create another chidl case Shipment. So system willl do infinite loop. But this is not actual requirment.
So I write customize When to check whether fulfill completed( Let Say isFulfillComplete is when)