With process management enabled, you can create workflows—such as request and approval flows—that integrate seamlessly into your apps.
This page provides examples of how to set up process management for request workflows.

• Workflow that allows requests to be sent back and rejected
• Workflow with multiple approvers
• Workflow with conditional branching
• Workflow with proxy approval
• Workflow that allows taking requests back to be corrected
• Workflow that allows approval to be skipped

Here, "request workflow" refers to a workflow set up in a Kintone app using process management that begins when a user makes a request and ends when the request is approved.

The following example is of a workflow that allows requests to be sent back or rejected.

• First status: Before applying
• Next statuses:
  • Applying
  • Sent back
  • Approved
  • Rejected

• Status: Before applying
• Assignee: User in "Created by" field
• Conditions: None
• Action: Apply
• Status after action taken: Applying

• Status: Applying
• Assignee: Approver
  The approver is specified in a User selection field placed on the app form.
• Conditions: None
• Actions:
  • Approve
  • Reject
  • Send back
• Status after action taken:
  • If the "Approve" action is performed: Approved
  • If the "Reject" action is performed: Rejected
  • If the "Send back" action is performed: Sent back

• Status: Sent back
• Assignee: User in "Created by" field
• Conditions: None
• Action: Reapply
• Status after action taken: Applying

The following example is of a workflow that needs to be approved by multiple users.

• First status: Before applying
• Next statuses:
  • Pending legal review
  • Pending director approval
  • Approved

• Status: Before applying
• Assignee: User in "Created by" field
• Conditions: None
• Action: Apply
• Status after action taken: Pending legal review

• Status: Pending legal review
• Assignees: Legal reviewers
  If you create a "Legal reviewer" group (role) in Users & system administration, you can select the group as an assignee in process management. For details, refer to the following page.
  Group (or role) settings
• Conditions: Needs to be approved by all legal reviewers
  Select All assignees in the list must take action from the drop-down list for selecting how to specify assignees.
  For details on how to configure these settings, refer to the following page.
  Setting assignees
• Action: Approve
• Status after action taken: Pending director approval

• Status: Pending director approval
• Assignee: Legal director
• Conditions: None
• Action: Approve
• Status after action taken: Approved

The following example is of a workflow that has conditional branching.

• First status: Before applying
• Next statuses:
  • Pending director approval
  • Pending manager approval
  • Approved

• Status: Before applying
• Assignee: User in "Created by" field
• Conditions:
  • Cost is 10,000 USD or more
  • Cost is less than 10,000 USD
• Action: Apply
• Status after action taken:
  • If the cost is 10,000 USD or more: Pending director approval
  • If the cost is less than 10,000 USD: Pending manager approval

• Status: Pending director approval
• Assignee: Director
• Actions:
  • Approve
  • Send back
• Status after action taken:
  • If the "Approve" action is performed: Approved
  • If the "Send back" action is performed: Before applying

• Status: Pending manager approval
• Assignee: Manager
• Actions:
  • Approve
  • Send back
• Status after action taken:
  • If the "Approve" action is performed: Approved
  • If the "Send back" action is performed: Before applying

The following example is of a workflow that lets another user approve a request instead of the assignee.

• First status: Before applying
• Next statuses:
  • Pending director approval
  • Pending manager approval
  • Approved

• Status: Before applying
• Assignee: User in "Created by" field
• Conditions:
  • Cost is 10,000 USD or more
  • Cost is less than 10,000 USD
• Action: Apply
• Status after action taken:
  • If the cost is 10,000 USD or more: Pending director approval
  • If the cost is less than 10,000 USD: Pending manager approval

• Status: Pending director approval
• Assignee: Approver (Director)
• Condition: Comment has been entered by approver
• Action: Approve
• User who can perform action usable by non-assignees: Proxy approver (Assistant director)
• Action usable by non-assignees: Approve as proxy
• Status after action taken: Approved

• Status: Pending manager approval
• Assignee: Approver (Manager)
• Action: Approve
• Status after action taken: Approved

The following example is of a workflow that allows users who made a mistake in their application to take it back and correct it.

• First status: Before applying
• Next statuses:
  • Applying
  • Approved

• Status: Before applying
• Assignee: User in "Created by" field
• Conditions: None
• Action: Apply
• Status after action taken: Applying

• Status: Applying
• Assignee: Manager
  The manager is specified in a User selection field placed on the app form.
• Conditions: None
• Actions:
  • Approve
  • Send back
• User who can perform action usable by non-assignees: User in "Created by" field
• Action usable by non-assignees: Take back
• Status after action taken:
  • If the "Approve" action is performed: Approved
  • If the "Send back" action is performed: Before applying
  • If the "Take back" action usable by non-assignees is performed: Before applying

The following example is of a workflow that can be completed by skipping the approval step.

• First status: Before applying
• Next statuses:
  • Pending assistant director approval
  • Pending director approval
  • Approved
  • Rejected

• Status: Before applying
• Assignee: User in "Created by" field
• Conditions: None
• Action: Apply
• Status after action taken: Pending assistant director approval

• Status: Pending assistant director approval
• Assignee: Assistant director
• Conditions: None
• Assignee actions:
  • Approve
  • Reject
  • Send back
• User who can perform actions usable by non-assignees: Director
• Actions usable by non-assignees:
  • Approve
  • Reject
  • Send back
• Status after action taken:
  • If the assignee performs the "Approve" action: Pending director approval
  • If the assignee performs the "Reject" action: Rejected
  • If the assignee performs the "Send back" action: Before applying
  • If the "Approve" action usable by non-assignees is performed: Approved
  • If the "Reject" action usable by non-assignees is performed: Rejected
  • If the "Send back" action usable by non-assignees is performed: Before applying

• Status: Pending director approval
• Assignee: Director
• Conditions: None
• Actions:
  • Approve
  • Reject
  • Send back
• Status after action taken:
  • If the "Approve" action is performed: Approved
  • If the "Reject" action is performed: Rejected
  • If the "Send back" action is performed: Before applying