Page-related operation queuing with page instructions
Pega APIs provide page instructions that you can use to make your application queue a list of page-related operations and send them to the server after the user performs a submit or a refresh. The server then runs the user operations in the order in which 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 APIs:
PUT /casetypes/{ID}/refreshPOST /casesPUT /cases/{ID}PUT /cases/{ID}/actions/{actionID}/refreshPOST /assignments/{ID}PUT /assignments/{ID}/actions/{actionID}/refresh
- Page instructions for embedded pages
You can use page instructions to specify whether an embedded page within the post data should be updated, replaced, or removed from your case.
- Page instructions for page groups
You can use 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.
- Page instructions for page lists
You can use 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.
- Updates to page lists and page groups with newRow
You can update the visible page list or page group without multiple trips to the server to insert or append multiple rows with the newRow object. You can either send a full page list or page group in content or by using pageInstructions.
Previous topic Feature support with stateless DX API Next topic Page instructions for embedded pages