Approve and reject — gateways and going back

Create 「Sales Proposal Approval」, reject a proposal, and revise it for approval. Follow the branches chosen by the review result and the loop back to review.

Add a decision to the flow#

The process in Chapter 3 had no branches. This time, ask for approval and rejection from the start. You will create a new process, 「Sales Proposal Approval」.

The customer enters a request, and Minji writes a proposal. Jinyoung reviews it. If Jinyoung rejects it, Minji revises it and sends it through review again. If Jinyoung approves it, Minji handles the step for sending it to the customer.

Try it 1 — Create the process through conversation#

1. Open a new conversation as in Chapter 3 and choose 「Basic Agent」.
2. Enter the prompt below.
3. When 「Shall I create the process from this draft?」 appears, choose 「Create the process as is」.

Create a sales proposal approval process. The customer enters their request, then a sales representative writes a proposal and the sales team lead reviews it. If the sales team lead approves, the sales representative sends the proposal to the customer; if the lead rejects it, the sales representative reads the review comments and rewrites the proposal. Put a review result (approve or reject) and review comments in the team lead review form, and make an input form for each step.

When asking for a branch, say who reviews, where approval leads, and where rejection leads. Also ask for the form field that supplies the decision: 「Review Result」.

After 「Created a work item to generate the process from the consultation.」, a progress indicator appears. Our run paused at 「waiting_for_user」 and 「72%」 for a confirmation.

Try it 2 — Answer the single confirmation panel#

This English run shows one confirmation panel. It asks whether to create a decision table (DMN) for the gateway. There are no separate skill or agent pages in this run.

The candidate is 「Proposal Approval Decision」 for 「Sales Proposal Approval」. It lists the approval and rejection branches.

1. Leave the gateway candidate unselected. This exercise uses the BPMN branch conditions.
2. Find 「Write your own (optional)」. Its placeholder is 「Type anything you'd like」.
3. Enter No decision table is needed — use the BPMN gateway conditions.
4. Click 「Submit response」 once it becomes enabled.

「Submit response」 is disabled while nothing is selected or typed. Entering the response lets you continue without selecting a gateway for DMN conversion.

About ten seconds after submission, our run showed 「BPMN process generation complete」 and reported that one process had been created and saved.

The result card is titled 「BPMN process generation result」 and includes 「Full graph」 and 「Saved」. The definition is saved automatically. There is no separate save button to click here.

Read the gateway and the return arrow#

The generated definition has three lanes: 「Customer」, 「Sales Representative」, and 「Sales Team Lead」.

The flow starts with 「Submit Sales Request」, then moves to 「Write Proposal」 and 「Review Proposal」.

The diamond after review is 「Proposal Approval Decision」. An X inside a diamond means an exclusive gateway. The flow takes one outgoing branch whose condition matches.

The arrow from rewriting back to review makes a loop. Rejection does not end this instance. Minji revises the proposal, and Jinyoung handles the same review step again.

Try it 3 — Assign the lane owners#

Use the same method as Chapter 5. In this definition's edit mode, the lanes are vertical columns with their names at the top.

1. Open 「Sales Proposal Approval」 and click 「Edit」. Double-click the 「Sales Representative」 lane name.
2. Choose 「Role Resolution By Direct user」 and select Minji Kim in 「User ID」. Save the panel.
3. Double-click 「Sales Team Lead」. Use 「Role Resolution By Direct user」 to select Jinyoung Jang, then save and close the panel.
4. Save the definition through 「Version Up」. Our version changes from v0.0 to v0.1.

The automatic save after generation and this version save are separate. The version now includes the role owners. Jinyoung will also take the 「Customer」 role when opening the run.

Try it 4 — Enter the customer request as Jinyoung#

1. As Jinyoung, click 「Execute」 for 「Sales Proposal Approval」.
2. Check 「Role Mapping」: 「Customer」 is Jinyoung Jang, 「Sales Representative」 is Minji Kim, and 「Sales Team Lead」 is Jinyoung Jang.
3. Enter the request below in 「Sales Request Details」, then click 「Submit Complete」.

Hanbit Trading’s Daejeon branch is moving offices. It needs 30 work desks and 30 chairs, with a budget of KRW 20,000,000, installed before move-in in the first week of December.

Our instance name appears as 「Sales Proposal Approval · Hanbit Daejeon Office Fu…」. Use this instance name to find the right cards when switching between Jinyoung and Minji.

Try it 5 — Write the proposal as Minji#

In Minji's 「Task List」, open 「Write Proposal」 for this instance. 「Previous Activity Input」 includes 「Submit Sales Request · Jinyoung Jang」.

The current form is 「Write Proposal Layout」. Its 「Proposal Details」 field is a plain text box.

1. Read Jinyoung's request in 「Previous Activity Input」.
2. Enter the proposal below directly in 「Proposal Details」.
3. Check the text, then click 「Submit Complete」.

Daejeon branch move proposal: 30 work desks and 30 mesh chairs. Estimated about KRW 18,000,000 (VAT excluded).

There is no Report editor for this field. Type into the text box itself. In our run, 「Review Proposal」 reached Jinyoung about three seconds after submission.

Try it 6 — Reject the proposal as Jinyoung#

In Jinyoung's 「Task List」, open 「Review Proposal」. 「Previous Activity Input」 contains two entries: 「Submit Sales Request · Jinyoung Jang」 and 「Write Proposal · Minji Kim」.

The current form is 「Review Proposal Layout」.

1. Read the request and proposal in 「Previous Activity Input」.
2. Change 「Review Result」 from 「Approve」 to 「Reject」.
3. Enter the comment below in 「Review Comments」.
4. Check that 「Review Result」 is 「Reject」, then click 「Submit Complete」.

The installation fee and schedule are missing. Please add the installation fee for the Daejeon area and an installation schedule before move-in, then rewrite it.

About eight seconds later, Minji received 「Read Comments & Rewrite Proposal」. 「Send Proposal to Customer」 did not open. The gateway took the rejection branch.

Try it 7 — Revise the proposal as Minji#

Open 「Read Comments & Rewrite Proposal」 as Minji. 「Previous Activity Input」 now includes the request, the first proposal, and Jinyoung's review.

The current form is 「Read Comments & Rewrite Proposal Layout」. It has two Report cards: 「Review Comments」 and 「Revised Proposal」.

1. Read the rejection comment in Jinyoung's 「Review Proposal」 entry under 「Previous Activity Input」.
2. Open the 「Revised Proposal」 Report card for editing.
3. Enter the revised proposal below in 「Content Editor」, then click 「Save」.
4. Check the saved preview and click 「Submit Complete」.

Revised Daejeon branch move proposal: 30 work desks and 30 mesh chairs, products about KRW 18,000,000 (VAT excluded). Includes the Daejeon installation fee; installed over two days in the first week of December, before move-in.

About three seconds after submission, 「Review Proposal」 returned to Jinyoung. The flow followed the return arrow to the same review step.

Try it 8 — Approve and record sending to the customer#

Open 「Review Proposal」 again as Jinyoung. This time, the form keeps the previous values. It opens with 「Reject」 and the old comment already filled in.

1. Read Minji's revised proposal in the previous inputs.
2. Change 「Review Result」 from 「Reject」 to 「Approve」.
3. Replace 「Review Comments」 with Good — the installation schedule is included. Please send it to the customer.
4. Check both values, then click 「Submit Complete」.
5. Switch to Minji and open 「Send Proposal to Customer」 when it arrives.
6. In 「Send Proposal to Customer Layout」, leave the 「Draft Proposal」 file field empty for this exercise. In the 「Review Result」 text field, enter Approved — sent the revised proposal with the installation schedule.
7. Click 「Submit Complete」.

The customer-sending task reached Minji about five seconds after approval in our run. This time, the gateway took the approval branch.

This exercise records the sending step in a form. Submitting the text is not itself an email-sending action.

Try it 9 — Check that the instance is complete#

1. Check that the instance status is 「COMPLETED」.
2. In Jinyoung's window, open 「Kanban Board」 and count the five cards under 「Done」.
3. Check that there is only one 「Review Proposal」 card, even though Jinyoung reviewed twice.

The five cards are:

• 「Send Proposal to Customer」 — Minji Kim
• 「Read Comments & Rewrite Proposal」 — Minji Kim
• 「Review Proposal」 — 「My task」
• 「Write Proposal」 — Minji Kim
• 「Submit Sales Request」 — 「My task」

There is one review card because the same step reopened. A separate second review step was not created. The instance finished after rejection, revision, another review, and the final customer-sending submission.

Next chapter#

You followed a branch based on a review result and a loop that returned work for revision. You have now created and run processes handled by people.

In Chapter 8, you will upload company documents to the Knowledge Base so agents can use them as sources. In Chapter 13, you will run an agent-assisted quote process whose approval path depends on whether the total is below KRW 30,000,000 or at least that amount.