Support Article
Call pxChangeStage activity to jump to other stage directly.
SA-12105
Summary
When attempting to change stage using a custom menu with action to call the pxChangeStage Activity followed by Harness refresh a message appears on screen stating that there are no actions specified for the assignment.
Error Messages
No errors, but the following message is displayed on the screen.
Either no actions are specified for this assignment or you do not have the permission to access any of them.
Steps to Reproduce
1. Configure a menu (sourced from Navigation Rule) with actions to call pxChangeStage followed by a Harness refresh.
2. Test changing stage.
Root Cause
The problem occurs when only refreshing the Harness as this does not refresh the case data from the database. This issue is not encountered if you remove the refresh harness configuration and then manually refresh the screen (via the Other Actions / Refresh menu option) after running pxChangeStage. This is because the Refresh option from the Other Actions menu performs a full case refresh including getting updated data from the database.
Resolution
Add the following configuration to the Refresh action. This mimics the refresh functionality from the standard menu option which can be reviewed in the standard Navigation rule Work- pyWorkActionsPerform.
- Enable the “Disable submit on refresh” setting
- Specify Work- class.
- Add call to the RefreshOnConflicts activity
Published July 15, 2015 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.