Skip to content

Connect Approve Request to the Process

Key Lesson: Extend the submission checkpoint by mapping Process data into the approval Screen, handling its output, and routing the submitted request to Approve PR.

Complete Connect and Test Request Submission, including its verified save procedure and persistence checks, before this stage. Connect the approval Screen to the existing Approve PR User Task, then extend the working submission path to reach it.

Do not connect the approve or reject decision routes yet. Those routes require later task stages.

  1. In Design, under Object Types, select Process.
  2. Open PurchaseRequestProcessing.
  3. Select the existing Approve PR User Task in the Approver swimlane.
  4. Set the task’s Screen property to Purchasing.PurchaseRequestApprove.
  5. Save the Process, then reselect Approve PR before configuring its Inputs and Output handlers.
  6. Configure the task as follows:
TabPropertyValue
PropertiesNameApprove PR
ScreenPurchasing.PurchaseRequestApprove
Inputsrequest
process.request
Output handlerssubmit
process.request.comment = data.comment

return data.isApproved ? "approve" : "reject"
  1. Save your changes before continuing.

The input mapping passes the Process request into the Screen. The output handler preserves the submitted comment and returns the documented route name for the later decision paths.

Attention

If the Inputs or Output handlers tabs do not appear after assigning the Screen, see User Task Inputs and Output Handlers Do Not Appear.

Replace the submission checkpoint’s Start-to-End route so that new requests reach Approve PR after the existing save completes.

  1. Open PurchaseRequestProcessing and select the submit connection from Start Event to End Event.
  2. Preserve its verified save code before removing the connection.
  3. Use the Process Editor connector to connect Start Event to Approve PR.
  4. Select the new connection and set Name to submit.
  5. Transfer the existing verified connection code unchanged to the new connection. Keep the awaited save before the Process enters Approve PR; use the save configuration established in Connect and Test Request Submission.
  6. Confirm that no direct Start-to-End connection remains, then

    Save your changes before continuing.

Leave Approve PR unconnected to Revise PR and Request Quotation from Vendors. The approve and reject decision routes remain deferred.

Verify the first approval task checkpoint:

Create Purchase Request → Submit Request → PurchaseRequestProcessing starts → Approve PR becomes available → PurchaseRequestApprove opens

Use a fresh Process instance after every Process configuration change. Existing instances and tasks retain the configuration with which they were created.

Attention

Before testing, ask the application owner or administrator to confirm that the test user is linked to the Approver role. The Approve PR task is assigned through the Approver swimlane, and the repository does not contain a verified user-to-role assignment procedure.

Submit a fresh request using the action configured and tested in Connect and Test Request Submission. The completed instance from that checkpoint cannot create an approval task. Confirm that the new instance uses the updated submit route to Approve PR, then continue with the task checks below.

  1. On Home, locate Approve PR under My Team Tasks. If the task list is not displayed, select Task list in the sidebar.
  2. Open Approve PR.
  3. Select Assign Task To Myself.
Expected result:

The task is available to a user linked to the Approver role and opens the PurchaseRequestApprove Screen.

If this does not happen:
  • If the task is unavailable, ask the application owner or administrator to verify the test user’s Approver role membership. Also confirm that the Approver swimlane’s Assignee expression contains roles: [This.$Roles.Approver].

  • If the wrong Screen opens, compare the Approve PR task’s Screen property with Configure the Approve PR User Task.

  1. Compare the displayed Cost Center and line-item values with the request you submitted.
  2. Confirm that the request detail fields cannot be edited.
  3. Confirm that the Approver comment field is editable.
  4. Confirm that the Approve and Reject buttons are visible and enabled.
  5. Do not select either decision button during this checkpoint.
Expected result:

PurchaseRequestApprove receives the Process request input and displays the submitted request details and items as read-only. The Approver comment, Approve, and Reject controls render and remain enabled.

If this does not happen:
  • If the request is missing or differs from the submitted values, confirm that the Approve PR task maps its request input to process.request and that the embedded PurchaseRequestInclude receives screen.request.

  • If the request fields are editable, confirm that only the embedded PurchaseRequestInclude is inside a Disable component with Disabled set to true.

  • If all controls appear enabled, including the request fields, confirm that Enable everything is not selected in the Dev Tools Bar.

The approve and reject decision paths are tested in the next stage, after PurchaseRequestUpdate and the reject/resubmit routes are configured. This stage does not add or test temporary downstream routes.