navigate_assignment_previous

Move back to the prior step in a multi-step form or screen flow assignment, retaining breadcrumb details. Requires assignment ID and eTag for optimistic locking to prevent conflicts. Optionally update fields, attachments, or perform page operations during navigation.

Instructions

Navigate back to the previously visited step in a screen flow or multi-step form assignment. Jumps to the previously visited navigation step from the current step. For multi-step forms and screen flows, navigation path steps are determined by the Enable navigation link checkbox. Returns assignment details with navigation breadcrumb information under uiResources when viewType is not "none". This operation requires an eTag from a previous assignment API call for optimistic locking.

Input Schema

Name	Required	Description	Default
`assignmentID`	Yes	Full handle of the assignment to navigate. Format: ASSIGN-WORKLIST {caseID}!{processID}. Example: "ASSIGN-WORKLIST PBANK-LOAN-WORK V-76003!REVIEW_FLOW". Must be a complete assignment identifier that uniquely identifies the specific assignment instance.
`attachments`	No	Optional list of attachments to be added to or deleted from specific attachment fields during navigation. Each attachment entry specifies the operation (add/delete) and attachment details. Only attachment fields included in the assignment view can be modified.
`content`	No	Optional map of scalar properties and embedded page properties to be set during navigation. Only fields that are part of the assignment view can be modified. Field names should match property names defined in the Pega application. Values will be applied when navigating to the previous step.
`eTag`	Yes	Required eTag unique value representing the most recent save date time (pxSaveDateTime) of the case. Must be obtained from a previous assignment API call (get_assignment, get_assignment_action, etc.). Used for optimistic locking to prevent concurrent modification conflicts.
`pageInstructions`	No	Optional list of page-related operations to be performed on embedded pages, page lists, or page groups during navigation. Each instruction specifies the operation type and target page structure. Only pages included in the assignment view can be modified.
`viewType`	No	Type of view data to return. "none" returns no UI resources (default), "form" returns form UI metadata in read-only review mode, "page" returns full page UI metadata in read-only review mode. Navigation breadcrumb information is included under uiResources when not "none".	none

Input Schema (JSON Schema)

{
  "properties": {
    "assignmentID": {
      "description": "Full handle of the assignment to navigate. Format: ASSIGN-WORKLIST {caseID}!{processID}. Example: \"ASSIGN-WORKLIST PBANK-LOAN-WORK V-76003!REVIEW_FLOW\". Must be a complete assignment identifier that uniquely identifies the specific assignment instance.",
      "type": "string"
    },
    "attachments": {
      "description": "Optional list of attachments to be added to or deleted from specific attachment fields during navigation. Each attachment entry specifies the operation (add/delete) and attachment details. Only attachment fields included in the assignment view can be modified.",
      "items": {
        "description": "Attachment object with file details and metadata",
        "properties": {
          "fileContent": {
            "description": "Base64 encoded file content",
            "type": "string"
          },
          "fileName": {
            "description": "Name of the attachment file",
            "type": "string"
          },
          "mimeType": {
            "description": "MIME type of the attachment",
            "type": "string"
          }
        },
        "type": "object"
      },
      "type": "array"
    },
    "content": {
      "description": "Optional map of scalar properties and embedded page properties to be set during navigation. Only fields that are part of the assignment view can be modified. Field names should match property names defined in the Pega application. Values will be applied when navigating to the previous step.",
      "type": "object"
    },
    "eTag": {
      "description": "Required eTag unique value representing the most recent save date time (pxSaveDateTime) of the case. Must be obtained from a previous assignment API call (get_assignment, get_assignment_action, etc.). Used for optimistic locking to prevent concurrent modification conflicts.",
      "type": "string"
    },
    "pageInstructions": {
      "description": "Optional list of page-related operations to be performed on embedded pages, page lists, or page groups during navigation. Each instruction specifies the operation type and target page structure. Only pages included in the assignment view can be modified.",
      "items": {
        "description": "Page operation object with instruction type and target",
        "properties": {
          "instruction": {
            "description": "The type of page instruction to perform",
            "type": "string"
          },
          "target": {
            "description": "The target page or page list for the instruction",
            "type": "string"
          }
        },
        "type": "object"
      },
      "type": "array"
    },
    "viewType": {
      "default": "none",
      "description": "Type of view data to return. \"none\" returns no UI resources (default), \"form\" returns form UI metadata in read-only review mode, \"page\" returns full page UI metadata in read-only review mode. Navigation breadcrumb information is included under uiResources when not \"none\".",
      "enum": [
        "none",
        "form",
        "page"
      ],
      "type": "string"
    }
  },
  "required": [
    "assignmentID",
    "eTag"
  ],
  "type": "object"
}

Pega DX MCP Server