Connect Request Quotations to the Process
Key Lesson: Complete a terminal Process branch by connecting a task Screen, mapping Process data into it, returning a route name from its output handler, and matching that name to an End Event route.
Connect PurchaseQuotationCreate to the existing Request Quotation from Vendors User Task, then add the terminal Procurement path:
Approve PR → approve → Request Quotation from Vendors → sendRequest → End Event
This stage completes the first full path through PurchaseRequestProcessing. The reject, revise, and resubmit path remains available, but its complete journey is verified in the final end-to-end stage.
1. Configure the Request Quotation from Vendors User Task
Section titled “1. Configure the Request Quotation from Vendors User Task”- In Design, under Object Types, select Process.
- Open
PurchaseRequestProcessing. - Select the existing Request Quotation from Vendors User Task in the Procurement swimlane.
- Set the task’s Screen property to
Purchasing.PurchaseQuotationCreate. - Save the Process, then reselect Request Quotation from Vendors before configuring its Inputs and Output handlers.
- Configure the task as follows:
| Tab | Property | Value |
|---|---|---|
| Properties | Name | Request Quotation from Vendors |
| Screen | Purchasing.PurchaseQuotationCreate | |
| Inputs | request | |
| Output handlers | submit | |
-
Save your changes before continuing.
The input mapping passes the current process.request into the Screen. Submit RFQs submits screen.request through the Screen’s submit output, and the User Task output handler returns the route name sendRequest. The source procedure does not require an additional Process-variable assignment before completion.
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.
2. Connect the approve and sendRequest routes
Section titled “2. Connect the approve and sendRequest routes”The Process Foundation retained the Start Event and End Event from the default diagram. Connect the existing tasks to the existing End Event.
- Use the Process Editor connector to create each connection listed in the table.
- Select each route, then set its Name in the Properties panel to the corresponding route name.
| Route name | From | To |
|---|---|---|
| approve | Approve PR | Request Quotation from Vendors |
| sendRequest | Request Quotation from Vendors | End Event |
-
Save your changes before continuing.
Route names are case-sensitive and must match the values returned by the User Task output handlers. The existing Approve PR handler returns approve for an approved request, and the Procurement handler returns sendRequest.
Attention
Before testing, ask the application owner or administrator to confirm that the Approver test user is linked to the Approver role and the Procurement test user is linked to the Procurement role. The repository does not contain a verified user-to-role assignment procedure.
Outcome
An approved request can now move from Approve PR to Request Quotation from Vendors. Submitting RFQs returns sendRequest, follows the matching route, and gives the Process its first terminal path through the End Event.
Verify Procurement
Section titled “Verify Procurement”Verify the Procurement completion path:
Create request → Submit → Approve → Request Quotations → Add RFQ data → Submit RFQs → End Event
Use a fresh Process instance after every task configuration change. Existing instances and tasks retain the configuration that was active when they were created.
Attention
Before testing, ask the application owner or administrator to confirm that the Approver test user is linked to the Approver role and the Procurement test user is linked to the Procurement role. The repository does not contain a verified user-to-role assignment procedure.
1. Start a fresh Process instance and open Approve PR
Section titled “1. Start a fresh Process instance and open Approve PR”- Run the Purchasing app.
- Open Purchase Request → Create New.
- Select a Cost Center.
- Add at least one item and complete its request fields.
- Select Submit Request.
- On Home, open Approve PR as the Approver test user.
- Select Assign Task To Myself if the action appears.
A new PurchaseRequestProcessing instance creates Approve PR, and the task opens PurchaseRequestApprove with the submitted request.
-
If the Process does not create Approve PR, complete Verify Approve Request before continuing.
-
If the task is unavailable, ask the application owner or administrator to verify the test user’s Approver role membership.
2. Approve the request and open Procurement
Section titled “2. Approve the request and open Procurement”- Confirm that the submitted request values appear in
PurchaseRequestApprove. - Optionally enter an approval comment.
- Select Approve.
- Return to Home and locate Request Quotation from Vendors.
- Open the task as the Procurement test user.
- Select Assign Task To Myself if the action appears.
The Approve PR task completes, the approve route moves the same Process instance to Request Quotation from Vendors, and the task opens PurchaseQuotationCreate.
-
If the Process does not reach Request Quotation from Vendors, confirm that the Approve action submits
isApproved: true, the Approve PR output handler returnsapprove, and the outgoing route is namedapprove. -
If the task is unavailable, ask the application owner or administrator to verify the test user’s Procurement role membership. Also confirm that Request Quotation from Vendors is in the Procurement swimlane.
-
If the wrong Screen opens, compare the User Task Screen property with Configure the Request Quotation from Vendors User Task.
3. Verify the request and add RFQ data
Section titled “3. Verify the request and add RFQ data”- Confirm that the approved request data and line items are displayed.
- Confirm that the request detail fields are read-only.
- Select Add RFQ.
- Enter a distinctive value in Vendor name.
- Confirm that the vendor value remains visible in the quotation entry.
PurchaseQuotationCreate receives the current process.request, keeps its request details read-only, and adds a new This.Quotation entry to screen.request.quotations.
-
If request data is missing, confirm that the User Task maps its
requestinput fromprocess.request. -
If the request fields are editable, compare the Disable configuration with Build the Request Quotations Screen.
-
If Add RFQ does not add an entry, confirm that its action runs
screen.request.quotations.push(new This.Quotation)and that the quotation relationships were completed in Define Quotation Relationships.
4. Submit RFQs and verify completion
Section titled “4. Submit RFQs and verify completion”- Select Submit RFQs.
- Return to Home.
- Confirm that Request Quotation from Vendors is no longer active.
- Confirm that no follow-on User Task is created for this Process instance.
Submit RFQs completes the Procurement task. Its submit output invokes the User Task handler, the handler returns sendRequest, and the matching route moves the Process to the End Event.
-
If the task does not submit, confirm that Submit RFQs runs
await output.submit(screen.request). -
If the task submits but the Process does not reach the End Event, confirm that the Request Quotation from Vendors output handler returns
sendRequestand that its outgoing route to the End Event is namedsendRequest. For exact matching rules, see the Process Routes reference.
The final stage verifies the complete end-to-end journey, including Reject → Revise PR → Resubmit → Approve → Procurement → Complete. Do not repeat that revision loop in this checkpoint.