Question

Child Case Type Change Stage / Move Into Parent Case Type (with property Can Reuse in Both (Parent & Child))

hi,

I have a case type (Parent) named Business and case type (Child) named Collection.

on the third stage, I use a utility shape (create case) for Child Case Type ( look the screenshot)

My goal is when Flow Create Collection Case, Work ID Collection created for Workbasket/Workpool Collection Team and Work ID 
Business Next Process move into Alternate Stage if Work ID collection not done(use when-conditions rule for validation flag Business & Collection Is Done ).
So, when Work ID Collection Done (Resolved), i want to move Work ID Business From Alternate Stage into Next Stage (Main Stage).

Can Pega OOTB do This ?

Thanks

***Updated by moderator: Lochan to update Categories***

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Correct Answer
May 31, 2017 - 5:27am

hi,

i found another solution.

i'm using wait shape in alternate shape for waiting child case resolved and continue the parent case into the next step using decision & change stage.

 

thanks

Comments

Keep up to date on this post and subscribe to comments

April 13, 2017 - 2:11pm

Hello,

Conceptually, I think that should all be doable, although it may not be entirely straightforward and I don't know of an out of the box option that just does that for you. What version are you using? 

Thanks,
Mike

April 16, 2017 - 11:26pm
Response to MikeTownsend_GCS

hi,

i'm using 7.2.1, I've tried looking at the PDN and find this discussion :

https://pdn.pega.com/community/product-support/question/change-stage-child-parent,

https://pdn.pega.com/community/product-support/question/spinoff-split-join-split-each

but i'm still don't understand how to use Split Join ( according to the recommendations from links) for my requirement, Can you help me to give some example using split join.

thanks

 

April 18, 2017 - 9:36am

 

The split-join would be most useful when you have several tasks you want performed on one piece of work, and you're willing for those tasks to occur literally simultaneously.  Then when all the tasks are done, you want to proceed with your main flow.

For instance, if the main flow were a house-deal, there might be a home inspection task where a professional walks through the home, as well as a title search, where a bank lawyer searches for historical data about the house.  Those two things can be done simultaneously.  So a split-join could be used.  When both the inspection and title search are done, the main work continues, which for the case of a house-deal might be to schedule the closing meeting to finish the deal.

 

April 19, 2017 - 9:40pm
Response to ericosman_GCS

hi ericosman,

thanks for the explanation , Can you give an example How to use split-join in the designer studio ?

 

thanks

April 26, 2017 - 11:50pm

hi,

can anyone help me about using split - join for my case in this discussion.

According to : https://pdn.pega.com/community/product-support/question/change-stage-child-parent .

 

thanks

May 31, 2017 - 5:27am

hi,

i found another solution.

i'm using wait shape in alternate shape for waiting child case resolved and continue the parent case into the next step using decision & change stage.

 

thanks