Question
Rabobank Netherlands
NL
Last activity: 8 Aug 2016 6:39 EDT
Best practice to use circumstance
Hi,
In my application in pega 7.2, I have a flow action connected to an assignment. I need to execute 2 different pre activities depending on a value of a property.
I have 2 option-
1>write an wrapper activity and call both pre activities from there using pre condition.
2>circumstance flow action rule depending on that property value and call respective pre activities .
I prefer number 2 to get run time execution advantage. but I want to know what could be the best practice.
Regards,
Siddhartha
***Updated by moderator: Lochan to update Categories***
Pega Systems
IN
Though option 2 may give you run time execution, option 1is a cleaner way of executing.
This scenario may not qualify the need for circumstancing of a flow action just to change the pre-activity!!
Pegasystems Inc.
IN
If you prefer Circumstancing, it will not allow you/its built on applications to circumstance same rule on different property. Also, its overhead during debugging as well. Circumstance should be used in very specilized cases.
As @Viswa suggested, Option#1 is better choice.
LANIT JSC
RU
Using circumstance always leads to worse code readability and complicate debugging applications. To use circumstances you need to understand why it is very good to use it (i agree with Ravi Prakash Reddy "Circumstance should be used in very specilized cases.").
In option 2. You need create circumstance for pre-activity, not the flow action. I would not recommend in this situation to use it.
In option 1. I recommend use this approach. You can also think about to perform this activity directly on the flow (using utility shape with decision shape), if applicable in your case (#1. There is no need to perform an pre-activity action each time you open the flow action; #2. Activity are business value and can be reflected in the flow)