Optimizing action sets
Consolidating actions in the action set
Each action in the action set generates at least one HTTP request to the server and runs in the sequential order of configuration.
It is important to optimize the actions and reduce the number of HTTP requests to the server using the following best practices:
- Use wrapper activity or wrapper data transform to consolidate all the actions.
- If the pre-activity or pre-data transform runs in the same context as the section refresh, configure them in the refresh section action.
- Modify the content of your pre-activity if needed when running it in the context of the refresh section.
Differentiating between post and refresh section actions
By default, the refresh section action submits all the pending changes applied to the form back to the server. There is no need to use a post action before a refresh section action.
Use the post action in conjunction with refresh when conditions.
Note: The run activity, run data transform, and set value actions do not post the changes made to a form back to the server. If you want to pass some of the changes that are made on a form to an activity or a data transform, you need to pass them as parameters.
Check your knowledge with the following interaction.
If you are having problems with your training, please review the Pega Academy Support FAQs.
Want to help us improve this content?