Inflight WO
We need to retain the existing UI (section contents) for inflight work objects. New enhancements should be appearing only for the new cases created post deployment.
Since the section is embedded inside multiple section, and the same section is reused in Review screens as well, assignment restructuring in the flow couldn't be done.
Circumstancing/visibility can be used by setting some flag for the newly created cases. But the issue is, if there are more changes for the same section come up in future, again we need to repeat the process by setting new flag and use it for circumstance/visibility, which is tedious.
If any best approach available for the above issue. Please let me know.
Thanks!
Pegasystems Inc.
US
Hi Sowmya,
Why not circumstance based on pxcreatedatetime of work objects? This way you needn't create any more flags.
--Ravi.
Pegasystems Inc.
US
Maybe we can use circumstance template based on pxcreatedatetime. Just while deployment, you can just change the date in the template.
Wipro
IN
It has to cross through multiple environments. Date will also vary according to environments (like SIT, UAT, NFT, OAT, Prod). So couldnt determine the actual date.
I am not sure if DSS would be accepted in Definition to provide the date,but even in that case, it would be difficult to implement with date.
For instance, assume the following scenario: We have a section A, which is existing. Some changes are made to Section A for Jan release. We will deploy Section A & Section A_v1 (Circumstanced version) in Jan.
Post deployment, Again we got some enhancements to the same section A in Feb. So, Section A is now circumstanced with A_v2.
And in March, if we are planning to deploy, then for the cases created before Jan will display the A_v1, and cases created between Jan-March will display A_v2, and cases created after March will display A. This satisfies the requirement. But in future, many enhancements may come to the same section.
So, like this, Circumstanced versions should continue for every enhancement in the section. Is it the right approach? Please clarify
Pegasystems Inc.
AU
Using a Dynamic System Setting for the value of the date will facilitate the approach you recommend; the circumstance based on pxCreateDateTime > D_AppExtension.ReleaseDate then configuring release date to read form the DSS.
-Joel
Pegasystems Inc.
US
Hi Sowmya,
I believe the circumstancing approach mentioned above is the best option.
Regards,
-Meghan