Posted: 11 Jan 2018 11:12 EST Last activity: 14 Jan 2018 8:16 EST
Help me how to implement DCR for below requirement.
Hi Pega experts,
Can you help me how to implement DCR for below requirement. (pls tolerate my over intelligence questions or silly questions as I have more theoretical exposure and limited practical pega development exp, kindly help it wold be grateful)
1.Have a "rolemodelFWFlow" Defined in FW with two assignments -1st assignment routed to "currentoperator" , 2nd assignment routed to "WorkQueue"[workQueue in 2nd assignment should be configurable].
2. Need Two Applications with Flows namely "App1.FollowerFlow1" and "App2.FollowerFlow1" with same steps as "rolemodelFWFlow" Defined in FW but the 2nd assignment need to be routed to supplied App1.WB1 and App2.WB1 for respective application Flows App1 and App2.
1a.Do we need to define two separate flows in two applications App1.FollowerFlow1 and App2.FollowerFlow1 and call "rolemodelFWFlow" while passing the relevant work queues - App1.WB1 and App2.WB1 for respective application Flows from App1 and App2.? or 1b.launch the "rolemodelFWFlow" while passing the relevant work queues - App1.WB1 and App2.WB1 for respective application Flows from App1 and App2.?
2. If approach 1a is suggested then we need to duplicate same flow in three different places which is defeating the idea of reusability !! Or If 1b is suggested - If each application (App1 and App2) users are different and they are tied with (App1 built on FW) and (App2 built on FW) will they need to switch to the FW application to create the case? 3
. Request you to suggest a correct step by step implementation.
***Updated by moderator: Lochan to branch reply and create new post***
Are you asking if the workbasket to be routed to can be parameterized?
Offhand, I don't know, but if your number of choices for workbasket are small, you could design your flow to have a decision shape that fans out to a small number of assignment shapes, each identical except that it has a different workbasket specified as the route-to, and then the connectors for the several assignment shapes rejoin to a common path.
not just workbaskets but little more... it goes like below.
consider having 1 FW and 2 implementations Applications.
and have a flow with same assignments and flow path for the 2 implementations Applications, However have long list of Work baskets like App1.Wb1, App1.Wb2 ,.........App1.Wb15.. and App2.Wb1, App2.Wb2 ,.........App2.Wb15..
1.Question at flow level(Flow Reuse):-
Reuse of a common flow Defined in Fw without defining again in App1 and App2.-How
According to DCR we can place/save/write a common flow into FW(since both impl apps direct inherit) and re-use it in/from two implementation Applications (App1,App2)- how to do it
can you point me with specific steps/Article with detailed steps to do above for this scenario leave Wb fixed.
2.Once qstn#1 above is done (or both combined if both the qstns go hand in hand) pass the respective wbs for each assignments like App1.Wb1, App1.Wb2 ,.........App1.Wb15.. and App2.Wb1, App2.Wb2 ,.........App2.Wb15..