pyWorkPage has unexpectedly been reverted to an older version.
Developers are using Obj-Refresh-And-Lock after commit to acquire a lock on work Object using TaskStatus-Set method in the activity for calling a flow. An error is encountered.
Warning: The work page pyWorkPage has unexpectedly been reverted to an older version.
Steps to Reproduce
After commit, use Obj-Refresh-And-Lock Method and call connector in the flow using TaskStatus-Set Method.
Issue was not reproducible in house. In the User environment it was noticed that warning message was coming after a custom activity is executed,
pyWorkPage has unexpectedly been reverted to an older version
After the warning appears, the changes done to the work page(pyWorkPage) are reverted.
The custom activity is involved in updating two Work objects and includes steps which renames the pyWorkPage and obj-refresh-and-lock.
Suggested following local change,
1)Remove Page-Rename and Page-Remove for pyWorkPage
2)Leave the existing pyWorkPage as it is
3)Open the new WO in the activity and provide a page name (anything other than pyWorkPage) say secondworkPage
4)Update the secondworkPage page and commit the data on the page
6)Remove the obj-refresh-and-lock, this is not needed as lock is already existing on the pyWorkPage