Test & Verify the Process

Run the complete Purchase Request Process from submission through completion and verify each stage of the workflow.

📌

Attention

Finalize the Purchase Request Process before testing.

During testing, use a newly started Process instance so the task configuration you are validating reflects the latest saved Process definition.

📝

Note

Tasks and execution state belong to a specific running Process instance. After changing task configuration, start a new Process instance and test the newly created tasks. See Process instances, tokens, and User Tasks.

1. Start the Purchase Request Process

1. Run the Purchasing app.
2. Open Purchase Request → Create New.
3. Enter a Cost Center and add at least one completed item.
4. Click Submit Request.

Expected result:

The Submit Request action starts PurchaseRequestProcessing and navigates to the Home screen, where the Task list is displayed.

If this does not happen:

• If the Create Purchase Request screen does not close, review how to Start the Process from PurchaseRequestCreate.

• If an Access Denied based on Access control error appears, confirm that PurchaseRequestProcessing is selected under Covered business objects and that the start access control is configured for that Process. If access is still denied, see Access Control Errors.

• If the screen closes and the Home screen opens but Approve PR is not displayed in the Task list, confirm that the Approve PR User Task is assigned to the Approver swimlane and that the Process routes to Approve PR.

2. Verify the Approve PR task

1. On the Home page, locate Approve PR under My Team Tasks. If the task list is not displayed, select Task list in the sidebar.
2. Open the Approve PR task.
3. Click Assign Task To Myself.
4. Review the submitted purchase request and confirm that:
   • the request details and line items are displayed;
   • the request fields are read-only;
   • the Approver comment, Approve, and Reject controls are available.

Expected result:

• The Approve PR task opens the PurchaseRequestApprove screen. After assigning the task to yourself, the submitted Purchase Request details are displayed.

• The Purchase Request fields are read-only.

• The Approver comment is editable, and the Approve and Reject buttons are enabled.

If this does not happen:

• If the task is not available, confirm that the Approve PR User Task is assigned to the Approver swimlane.

• If the wrong screen opens, confirm that the Approve PR User Task uses Purchasing.PurchaseRequestApprove as configured in Approve PR User Task.

• If the purchase request fields are editable or the Remove button is active, review how to embed the Include screen and confirm that the request details are configured as read-only while the Approver comment, Approve, and Reject controls remain enabled.

• If the configuration is correct but the Purchase Request is still editable or the Add Item and Remove controls are still displayed, confirm that Enable everything is not selected in the Dev Tools floating panel.

3. Reject the request

1. In Approver comment, enter a distinctive test comment that you can identify in the next task.
2. Click Reject.
3. Return to Home and locate the task created by the Process.

Expected result:

The Approve PR task completes, and the reject route moves the same Process instance to a Revise PR task.

If this does not happen:

If the Process does not reach Revise PR, confirm:

• The Reject action on the Purchase Request Approve task screen submits isApproved: false as configured in Add Approve and Reject actions.

• The Approve PR submit output handler returns reject when data.isApproved is false, as described in how to configure the Approve PR task.

• The outgoing process route from Approve PR User Task is named reject, as configured in Connect the Process routes.

4. Verify the Update PR task screen

1. Open the Revise PR task.
2. If Assign Task to Myself appears, select it before continuing.
3. Confirm that the task opens the PurchaseRequestUpdate screen.
4. Confirm that the rejection comment entered by the Approver appears in the read-only Approver comment field.

Expected result:

The Approver comment field displays the comment entered when the request was rejected.

If this does not happen:

If the comment does not appear, confirm that the Approve PR output handling updates the current Purchase Request comment and that the Approver comment field on PurchaseRequestUpdate is bound to screen.request.comment.

5. Revise and resubmit the request

1. Change one or more purchase request values so that you can identify the revised request.
2. Click Resubmit.
3. Return to Home and locate the next Approve PR task.

Expected result:

Resubmit completes the existing Revise PR task, and the resubmit route returns the same Process instance to Approve PR. It does not start another PurchaseRequestProcessing instance.

If this does not happen:

If the Process does not return to Approve PR, confirm that the Resubmit action on PurchaseRequestUpdate uses await output.submit(screen.request), the Revise PR output handler returns resubmit, and the outgoing route is named resubmit. See Update Request Task Screen and the Process Routes reference.

6. Approve the revised request

1. Open the new Approve PR task.
2. If Assign Task to Myself appears, select it before continuing.
3. Confirm that the revised purchase request values appear on the PurchaseRequestApprove screen.
4. Optionally enter an approval comment, then click Approve.
5. Return to Home and locate the task created by the Process.

Expected result:

The Approve PR task completes, and the approve route moves the same Process instance to Request Quotation from Vendors.

If this does not happen:

If the revised values do not appear, confirm that Revise PR submits screen.request and that the Approve PR task receives the current Purchase Request.

If the Process does not reach Request Quotation from Vendors, confirm that the Approve action submits isApproved: true, the Approve PR output handler returns approve, and the outgoing route is named approve.

7. Complete the Procurement task

1. Open the Request Quotation from Vendors task.
2. If Assign Task to Myself appears, select it before continuing.
3. Confirm that the task opens the PurchaseQuotationCreate screen and displays the approved purchase request as read-only.
4. Click Add RFQ, enter a vendor name, and confirm that the value remains visible.
5. Click Submit RFQs.

Expected result:

The Request Quotation from Vendors task completes, and the sendRequest route moves the Process to the End Event.

If this does not happen:

If the task does not submit, confirm that the Submit RFQs action on PurchaseQuotationCreate uses await output.submit(screen.request) as configured in Request Quotations Task Screen.

If the task submits but the Process does not reach the End Event, confirm that the Request Quotation from Vendors output handler returns sendRequest and that its outgoing route is named sendRequest. For exact matching rules, see the Process Routes reference.

8. Confirm the Purchase Request Process is ready

Use this checklist to confirm that every part of the Process has been tested successfully.

• Submit Request starts PurchaseRequestProcessing and navigates to Home.
• Approve PR opens PurchaseRequestApprove.
• Reject routes the Process to Revise PR.
• The rejection comment appears in the Approver comment field on PurchaseRequestUpdate.
• Resubmit returns the same Process instance to Approve PR without starting a new instance.
• Approve routes the revised request to Request Quotation from Vendors.
• Request Quotation from Vendors opens PurchaseQuotationCreate.
• Submit RFQs completes the Procurement task.
• The sendRequest route moves the Process to the End Event.
• The complete Purchase Request Process runs successfully from submission through completion.