Page-related operation queuing with page instructions in Pega APIs
You can use the page instructions provided in Pega APIs so that your application queues a list of page-related operations and sends them to the server after the user performs a submit or refresh. The server then plays back the user operations in the order that they were received. For example, if the user edited a row, appended a row, and inserted a row, your application passes only the instructions and fields for those three rows to the server instead of the entire table.
The page instructions are provided in the following Pega APIs:
PUT /casetypes/{ID}/refreshPOST /casesPUT /cases/{ID}PUT /cases/{ID}/actions/{actionID}/refreshPOST /assignments/{ID}PUT /assignments/{ID}/actions/{actionID}/refresh
Understand how to use page instructions for each of the following:
- Page instructions for embedded pages
You can use the following page instructions to specify whether an embedded page within the post data is to be updated, replaced, or removed from your case.
- Page instructions for page lists
You can use the following page instructions to specify whether an embedded page in a page list within the post data is to be updated, replaced, appended, inserted, moved, or deleted from your case.
- Page instructions for page groups
You can use the following page instructions to specify whether an embedded page in a page group within the post data is to be updated, replaced, added to, or removed from your case.
Previous topic Append or insert rows in page lists and page groups by using newRow Next topic Page instructions for embedded pages