Skip to main content
Glama

Pega DX MCP Server

by marco-looy

refresh_assignment_action

Refreshes assignment action forms by updating values post-property changes, executing Data Transforms, and handling table row operations in modals. Validates inputs, retrieves view data, and returns affected field details, supporting form refresh settings and embedded list operations.

Instructions

Refresh assignment action form data with updated values after property changes, execute Data Transforms, and handle table row operations in modals. Supports form refresh settings configured in Flow Action rules, generative AI form filling, and embedded list operations with comprehensive validation and preprocessing execution. The API validates assignment and action IDs, retrieves view data, and returns information about fields affected by the refresh action. Supports Pega Infinity '25 features including table row operations in modals.

Input Schema

NameRequiredDescriptionDefault
actionIDYesName of the assignment action - ID of the flow action rule. This corresponds to the Flow Action rule configured in the Pega application where form refresh settings are defined. Example: CompleteVerification, Approve, Reject.
assignmentIDYesFull handle of an assignment. Example: ASSIGN-WORKLIST MYORG-SERVICES-WORK S-293001!APPROVAL_FLOW. This uniquely identifies the specific assignment instance where the refresh action will be performed.
contentNoMap of scalar properties and embedded page properties to be merged into the case during the refresh operation. Field values provided here will overwrite any settings made from preprocessing Data Transforms. Only fields that are present in the assignment action's view and are editable can be effectively updated. Non-visible fields cannot be set and updates to them may be lost in subsequent operations.
fillFormWithAINoBoolean value indicating whether to fill form with sample values using generative AI. This parameter works in conjunction with the EnableGenerativeAI toggle. When EnableGenerativeAI is turned on and fillFormWithAI=true, the system will attempt to generate appropriate form values using AI. Default: false.
interestPageNoTarget page specification for table row operations on embedded list properties. Example: ".OrderItems(1)" to target the first item in the OrderItems page list. This parameter is required when operation parameter is specified. Used with interestPageActionID to identify the specific embedded page and action for modal-based table operations.
interestPageActionIDNoAction ID for the embedded list operation Action rule. Example: "EmbeddedAction". This specifies the Flow Action rule that defines the preprocessing, validation, and post-processing logic for the table row operation. Required when operation parameter is specified. Only fields present in this Action's view can be modified during pre/post-processing.
operationNoString value indicating table row operation type for embedded list properties using modals (Pega Infinity '25+ feature). "showRow" is used when a row is being added or edited in a modal, triggering preprocessing of the interestPageActionID Action. "submitRow" is used when a row is being submitted, triggering validation and post-processing of the interestPageActionID Action. Only supported for table row operations in modals.
pageInstructionsNoList of page-related operations to be performed on embedded pages, page lists, or page group properties included in the assignment action's view during the refresh. These operations allow manipulation of complex data structures within the assignment. Each instruction specifies the operation type and target page structure. Only pages included in the assignment action's view can be modified.
refreshForNoName of the property which, when changed, triggers refresh after executing the Data Transform configured under form refresh settings of the flow action. When provided, the corresponding Data Transform is executed to provide updated default values. Replaces the deprecated pyRefreshData Data Transform approach. Only change property events are supported in form refresh settings.

Input Schema (JSON Schema)

{ "properties": { "actionID": { "description": "Name of the assignment action - ID of the flow action rule. This corresponds to the Flow Action rule configured in the Pega application where form refresh settings are defined. Example: CompleteVerification, Approve, Reject.", "type": "string" }, "assignmentID": { "description": "Full handle of an assignment. Example: ASSIGN-WORKLIST MYORG-SERVICES-WORK S-293001!APPROVAL_FLOW. This uniquely identifies the specific assignment instance where the refresh action will be performed.", "type": "string" }, "content": { "description": "Map of scalar properties and embedded page properties to be merged into the case during the refresh operation. Field values provided here will overwrite any settings made from preprocessing Data Transforms. Only fields that are present in the assignment action's view and are editable can be effectively updated. Non-visible fields cannot be set and updates to them may be lost in subsequent operations.", "type": "object" }, "fillFormWithAI": { "description": "Boolean value indicating whether to fill form with sample values using generative AI. This parameter works in conjunction with the EnableGenerativeAI toggle. When EnableGenerativeAI is turned on and fillFormWithAI=true, the system will attempt to generate appropriate form values using AI. Default: false.", "type": "boolean" }, "interestPage": { "description": "Target page specification for table row operations on embedded list properties. Example: \".OrderItems(1)\" to target the first item in the OrderItems page list. This parameter is required when operation parameter is specified. Used with interestPageActionID to identify the specific embedded page and action for modal-based table operations.", "type": "string" }, "interestPageActionID": { "description": "Action ID for the embedded list operation Action rule. Example: \"EmbeddedAction\". This specifies the Flow Action rule that defines the preprocessing, validation, and post-processing logic for the table row operation. Required when operation parameter is specified. Only fields present in this Action's view can be modified during pre/post-processing.", "type": "string" }, "operation": { "description": "String value indicating table row operation type for embedded list properties using modals (Pega Infinity '25+ feature). \"showRow\" is used when a row is being added or edited in a modal, triggering preprocessing of the interestPageActionID Action. \"submitRow\" is used when a row is being submitted, triggering validation and post-processing of the interestPageActionID Action. Only supported for table row operations in modals.", "enum": [ "showRow", "submitRow" ], "type": "string" }, "pageInstructions": { "description": "List of page-related operations to be performed on embedded pages, page lists, or page group properties included in the assignment action's view during the refresh. These operations allow manipulation of complex data structures within the assignment. Each instruction specifies the operation type and target page structure. Only pages included in the assignment action's view can be modified.", "items": { "type": "object" }, "type": "array" }, "refreshFor": { "description": "Name of the property which, when changed, triggers refresh after executing the Data Transform configured under form refresh settings of the flow action. When provided, the corresponding Data Transform is executed to provide updated default values. Replaces the deprecated pyRefreshData Data Transform approach. Only change property events are supported in form refresh settings.", "type": "string" } }, "required": [ "assignmentID", "actionID" ], "type": "object" }
Install Server

Other Tools from Pega DX MCP Server

Related Tools

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/marco-looy/pega-dx-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server