When refreshing section, pre-processing results lost
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?
***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.
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.
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.
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.