jump_to_step
Navigate directly to a specific step within multi-step assignments or complex processes in Pega DX MCP Server. Use step ID to jump to the desired step, enabling efficient navigation and process management. Supports breadcrumb generation, content updates, and page operations.
Instructions
Jump to the specified step within an assignment's navigation flow and return the details of the step based on step ID passed. Additional "navigation" node will be returned under "uiResources" to build navigation breadcrumb. This is useful for multi-step assignments, screen flows, and complex processes where you need to navigate directly to a specific step rather than progressing sequentially. To discover valid step IDs: use get_assignment to see current step context, check navigation breadcrumb information for available steps, or examine the assignment's process flow. Step IDs typically follow formats like "SubProcessSF1_ASSIGNMENT66" or "ProcessStep_123".
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| assignmentID | Yes | Full handle of the assignment to navigate within. Format: ASSIGN-WORKLIST {caseID}!{processID}. Example: "ASSIGN-WORKLIST MYORG-SERVICES-WORK S-293001!APPROVAL_FLOW". This is the complete assignment identifier that uniquely identifies the specific assignment instance containing the navigation steps. | |
| attachments | No | Optional list of attachments to be added to or deleted from specific attachment fields during the step navigation. Each attachment entry specifies the operation (add/delete) and attachment details. Only attachment fields included in the assignment's view can be modified during navigation. | |
| content | No | Optional map of scalar properties and embedded page properties to be set during the navigation to the specified step. Only fields that are part of the assignment's view can be modified. Field names should match the property names defined in the Pega application. Example: {"ReviewComments": "Approved with conditions", "Priority": "High"}. Values will be applied when jumping to the target step. | |
| eTag | Yes | Required eTag unique value representing the most recent save date time (pxSaveDateTime) of the case. This must be equal to the eTag header from the response of the most recent assignment update request, or from a get_assignment or get_assignment_action request. Used for optimistic locking to prevent concurrent modification conflicts during navigation. | |
| pageInstructions | No | Optional list of page-related operations to be performed on embedded pages, page lists, or page groups during the step navigation. 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's view can be modified. | |
| stepID | Yes | Navigation step path to jump to within the assignment. This identifies the specific step in the assignment's navigation flow. Examples: "SubProcessSF1_ASSIGNMENT66", "ProcessStep_123", "ReviewStep_1". To find valid step IDs: use get_assignment to see current navigation context, examine the assignment's process definition, or check previous navigation responses for available step identifiers. | |
| viewType | No | Type of view data to return in the response. "none" returns no UI resources (default), "form" returns form UI metadata in read-only review mode without page-specific metadata, "page" returns full page UI metadata in read-only review mode. The response will include navigation breadcrumb information under uiResources.navigation regardless of viewType to support navigation UI construction. | form |