When refreshing section, pre-processing results lost
Hi all!
I'm working on Pega7.1 and I've met one problem. In Flow Action's pre-processing I've set Data Transform, which apply some changes to Work Object (without commit). But after refreshing all changes have disappeared.
Is there any solution for this problem?
Thanks.
***Updated by moderator: Lochan to close 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.
Accepted Solution
Pegasystems Inc.
GB
Interesting... I can replicate this in 7.1.8, but not in 6.3 SP1 (the values persist following the refresh).
This feels like a bug to me... I would assume that values set via preprocessing should be retained when the screen is refreshed.
Anyway, as for a possible solution the problem does not seem to occur if you attach the DT to the flow connector instead of using the flow action pre processing.
Pegasystems Inc.
IN
That's because we changed the logic for Refresh from 7.1 onward.
Before 7.1 it was just a harness refresh, now On refresh we retrieve the latest from DB and then refresh.
Pegasystems Inc.
IN
It's certainly not correct behavior. I was just explaining why different behaviors are observed in 6.3 and 7.1.
I will raise a defect for the same, meanwhile work around suggested by Mark should unblock you
LANIT
RU
Hi, Mark!
Thanks for fast reply.
Your solution helped, but I have from 3 to 6 connectors to each assignment, which affected by this problem. It would be great, if there was a better solution.
Pegasystems Inc.
GB
Anton,
Are you using the Refresh option from the "Other Actions" menu?
If so the Navigation rule that is the source for this is the Available Work- pyWorkActionsPerform so can be saved into an application ruleset and customised.
For example, I did a test where I made the following changes so that the Refresh menu option only refreshes the harness. If you do try this then make sure you fully test your application to ensure there are no undesirable side effects. Perhaps someone with more in depth knowledge of this refresh functionality in Pega 7 can comment on if this is a resonable change to make:
1. Disable the "Disable submit on refresh" option.
2. Remove the call to RefreshOnConflicts activity.
Before:
After:
Pegasystems Inc.
IN
Hi Marc,
We added RefreshOnConflicts in 7.1 release to get fresh data from DB and not just harness refresh (which was the case till 6.3). I have raised this issue to the team who implemented this feature.
The earlier workaround you suggested should be fine for now as it will unblock this issue.
Pegasystems Inc.
GB
Thanks Pankaj,
Yes, the first solution would be my preference too, as this keeps everything using out of the box features rather than having to customise the pyWorkActionsPerform rule.
Pegasystems
IN
Hi Pankaj,
It is a bug. I have added the fix and it should be there in ML9. The fix was to add a parameter PerformPreProcessing and set it to true before calling ProcessAssignment in step 8 of RefreshOnConflicts activity.
Regards,
Saikat
Pegasystems Inc.
GB
Should the preprocessing actually be run each time the screen is refreshed? I am not sure that this is always going to be desirable... what if it does something that you only want to happen once?
Pegasystems Inc.
IN
We can override the navigation rule and on refresh call our own activity. Now on that activity we can save the work object and then call RefreshOnConflicts. That should take care of all the scenario. I know saving work object manually is not ideal but for the time being should solve the purpose. And when hot fix is available we can just remove it in one place with out changing all the design.
-Saikat