Video Walk Through of This Use Case

If you would like to see the "Purchase Request in Form.io" in action, watch video below.

https://www.youtube.com/embed/-Pgg82Bc5bQ

General Description

This use case demonstrates how to use ProcessMaker I/O in combination with Form.io for a purchase request process. In this example, use Form.io to create form interfaces to enter information for a purchase request and to approve or reject a purchase request. Form.io provides powerful tools to create both simple and complex forms with drag-and-drop functionality that makes it easy to implement user tasks in business processes. ProcessMaker I/O provides robust workflow functionality within Form.io forms.

This example also uses Slack to notify the purchase requester and approver regarding changes in workflow.

Refer to the following topics regarding the description of this example:

Prerequisites

The following are prerequisites to use this example:

  • A Form.io account that is within a free 30-day trial period or a paid plan
  • A Slack workspace in which you or your Slack administrator can add an app to your workspace
  • An XML-compliant text editor to edit the BPMN file used in this example

Process Scheme of This Example

Below is the process scheme:
"Purchase Request" process scheme

Process Description

Below is a description of the process:

  1. The requester enters information into the Purchase Order form. This form is designed in Form.io. For more information about this form, refer to the Purchase Order Form.

    Purchase_Order_Form designed on Form.io

  2. The requester submits the purchase request.
  3. In this example, Slack sends a message to the purchase-request channel that a new purchase request has been submitted. The approver must be a member of this channel. However, you can specify a private channel to the approver. See the "Leave Absence Request Using Slack" use case to learn how.
  4. The approver browses to the Purchase Approval Form. This form is also designed in Form.io. For more information about this form, refer to the Purchase Approval Form.

    Purchase Approval Form designed on Form.io

  5. The approver decides whether to approve or reject the purchase request based on information entered in the Purchase Order Form.
  6. Slacks sends a message to the purchase-request channel regarding the approver's decision.
  7. The requester receives an email regarding the approver's decision.

Get Started with the Use Case

Refer to the following topics in this order to get started with the use case:

Run a ProcessMaker I/O Environment and Download the BPMN File

ProcessMaker I/O is an "always on" cloud service. In this document, an Environment refers to an installation of ProcessMaker I/O in a virtual machine or a container. This environment is created, run, and managed directly through the ProcessMaker I/O web management console.

If you don't have a ProcessMaker I/O Environment yet, do the following:

  1. Log on to your ProcessMaker I/O account. If you do not have a free ProcessMaker I/O account, please create one.
  2. Click Environments from the top menu.
  3. Click the Create Environment button.

If you already have a ProcessMaker I/O Environment, do the following:

  1. Log on to your ProcessMaker I/O account.
  2. Click Environments from the top menu, and then run a ProcessMaker I/O Environment. Ensure that your Environment is running. If your Environment is stopped, click the Run button.
  3. Click the Environment name to display your Environment's dashboard.
  4. Click the Info tab.
  5. From the API URL: field, copy the API URL link. This URL is your Environment's URL, and is required. Example: https://MYENVIRONMENT.api.processmaker.io/api/v1, where MYENVIRONMENT is your ProcessMaker I/O Environment name. Paste the URL into a text file to remember it for later.

    Copying the API URL for the ProcessMaker I/O Environment

  6. Click the Copy button to the right of the Access token: field, and then paste your Environment's access token into your text file.
  7. Save the text file because you will paste more information into it.
  8. From the Examples: field, click the Example: Click to open link to display the ProcessMaker I/O Examples Portal.
  9. From the left menu, click the TAB LABEL tab.
  10. Click the Purchase-Request-Formio link to download the BPMN file to your computer. You will use this BPMN file for this example.

Develop the Form.io Forms

Refer to the following topics regarding how to develop the Form.io forms:

Create the Forms

To create the forms in Form.io, follow these steps:

  1. Log on to your Form.io account. If you don't have an account, create one.
  2. Select the Stand Alone Forms framework.

    Select the Stand Alone Forms framework

  3. The Create a New Stand-Alone Forms screen displays. Enter a project title (which is required) and a description, and then click the Create Project button.

    Create a new Form.io project

  4. Click the Forms option from the left menu.

    Forms option

  5. Click the New Form button.

    Click the "New Form" button to create a new form

  6. Click the API Web Form option. The New Form screen displays.
  7. Copy the API Path URL, and then save it in your text file. This URL is used to integrate with the form from your ProcessMaker I/O Environment.
  8. Create the Purchase Order Form and Purchase Approval Form used in this example. For information about these forms, refer to Forms.
  9. As you create each form, copy each form's API URL from the API Path field, and then save each in your text file. The API URL for each form is used to integrate that form with your ProcessMaker I/O Environment.

    API URL for a Form.io form

Integrate the Forms to Your Environment

After creating the forms in Form.io, integrate your forms with your ProcessMaker I/O Environment to pass form data. Below is a description of each way to do so:

  • Use a Form.io Webhook Premium action. This action allows you to integrate form submissions into a custom application by providing a means to call an external API with the form submission data in real time. The Webhook Premium action expires after a 30-day trial period unless you upgrade your project plan.
  • Use an HTTP request.

For this example, both methods involve creating HTML files to render each form. Follow these guidelines depending on which integration method you choose:

Create a Webhook Premium Action

To integrate your forms to your ProcessMaker I/O Environment using Form.io's Webhook Premium action, follow these steps:

  1. Log on to your Form.io account and then access your Form.io project.
  2. Click the Forms option from the left menu. The forms you created for the project display.
  3. Click the Actions button for the form in which to integrate a Webhook into your ProcessMaker I/O Environment.

    Click the Actions button for the form in which to integrate a Webhook

  4. From the Select an Action drop-down menu, select the Webhook (Premium) option, and then click the Add Action button.

    Select the Webhook (Premium) action option

  5. In the Webhook URL field, enter your ProcessMaker I/O Environment's API URL that you pasted into a text file. Example: https://MYENVIRONMENT.api.processmaker.io/api/v1, where MYENVIRONMENT is your ProcessMaker I/O Environment's API URL subdomain.
  6. Click the Save Action button.
  7. Click the Launch button. Form.io renders a preview of your form.

    Click the Launch button to render a preview of your form

  8. Along with the preview, Form.io provides a URL to share the form with others. Copy this URL and paste it into your text file, and then save.

    Copy the URL to share your form with others

  9. Repeat Steps 2 through 8 for the other form.
Create HTML Files

As an alternative to using Form.io's Webhook action, use an embedded rendering form for each Form.io form. For this example, ProcessMaker I/O provides HTML scripts to render each form. The scripts for each form are different. Both scripts provide functionality to use Form.io's Premium Webhook action. If you do not intend to use the Premium Webhook action, you must comment the function within each script so that it does not execute.

The HTML script representing the "Purchase Order Form" requires the following:

  • the unique API URL to access its form on Form.io
  • your ProcessMaker I/O Environment URL

The HTML file script representing the "Purchase Approval Form" requires the following:

  • the unique API URL to access its form on Form.io
  • your ProcessMaker I/O Environment token key

Refer to the following topics regarding how to configure each HTML file for your forms:

Configure an HTML file for the Purchase Order Form

Follow these steps to configure the "index.html" form for the "Purchase Order Form":

  1. Create an HTML file for the "Purchase Order Form." Example: index.html.
  2. Go to this GitHub repository where ProcessMaker I/O provides a script for the "Purchase Order Form." Since the first form's script requires different information than the second form's script, do not use this script for the second form.
  3. Copy, then paste the code into your index.html file.
  4. Search for var formUrl, and then replace the value with Form.io's API URL you copied from the API Path field in their portal for that form.
  5. In the index.html file that represents the "Purchase Approval Form," search for var webhookUrl, replace the value with your ProcessMaker I/O Environment URL, and then add /processes/Purchase/events/StartEvent/webhook to the end of your ProcessMaker I/O Environment URL. Example: https://MYENVIRONMENT.api.processmaker.io/api/v1/processes/Purchase/events/StartEvent/webhook, where MYENVIRONMENT is your ProcessMaker I/O Environment name.
  6. If you intend to publish the HTML files onto a hosting site, such as GitHub, change the header information in the script to reference the site you intend to host these files. To do so, follow these guidelines:
    • Search for the comment <!--Change this navigation links before publishing forms on some other place-->.
    • Change the URL to reference the hosting domain and file name for your form.
  7. Save the HTML file.

Note: If you use Form.io's Webhook Premium action in the future with this use case, comment the function for the Form.io Webhook Premium action if you do not intend to use it (so the function does not run when the form is submitted). To do so, follow these guidelines:

  • Search for the comment //Start comment this function, if used Form IO Webhook Premium Action.
  • Comment all lines in the function through the ending comment //End comment this function, if used Form IO Webhook Premium Action.
Configure an HTML file for the Purchase Approval Form

Follow these steps to configure the "index.html" form for the "Purchase Approval Form":

  1. Create an HTML file for the "Purchase Approval Form." Example: index2.html.
  2. Go to this GitHub repository where ProcessMaker I/O provides a script for the "Purchase Approval Form." Since the second form's script requires different information than the first form's script, do not use this script for the first form.
  3. Copy, then paste the code into your index.html file.
  4. Search for var formUrl, and then replace the value with Form.io's API URL you copied from the API Path field in their portal for that form.
  5. Search for envUrl, and then replace the value with your ProcessMaker I/O Environment URL. Example: https://MYENVIRONMENT.api.processmaker.io where MYENVIRONMENT is your ProcessMaker I/O Environment name.
  6. Search for accessToken, and then replace the value with your ProcessMaker I/O Environment access token.
  7. If you intend to publish the HTML files onto a hosting site, such as GitHub, change the header information in the script to reference the site you intend to host these files. To do so, follow these guidelines:
    • Search for the comment <!--Change this navigation links before publishing forms on some other place-->.
    • Change the URL to reference the hosting domain and file name for your form.
  8. Save the HTML file.

Open the Forms

To open the forms, follow these guidelines:

  • Open the files from a Web browser on a local computer.
  • Put the files on any hosting site, such as GitHub. If you did not change the header information in the HTML code ProcessMaker I/O provided, you will open ProcessMaker I/O's example forms when you view your HTML files.

ProcessMaker I/O provides examples of these forms in this GitHub repository.

Configure a Slack App

Refer to the following topics to configure a Slack app:

Create a Slack App

Follow these steps to create your Slack app with which your ProcessMaker I/O Environment will interact:

  1. Ensure you are signed into your Slack workspace.
  2. Go to the Slack API, and then click on the Create New App button. The Create a Slack App screen displays.

    Create a Slack App screen

  3. In the App Name field, enter the name of your Slack app.
  4. From the Development Slack Workspace drop-down menu, select the workspace from which your Slack app is to function.
  5. Click the Create App button.

Create an Incoming Webhook for Your Slack App

Follow these steps to create an incoming webhook that will read incoming messages from your ProcessMaker I/O Environment and Form.io:

  1. After creating your app, click Incoming Webhooks from the Basic Information page.

    Incoming Webhooks

  2. The Incoming Webhooks screen displays. Click the Activate Incoming Webhooks slider so it reads On. The Webhook URLs for Your Workspace section displays.

    Activate incoming webhooks

  3. Click the Request to Add New Webhook. If your Slack administrator requires permission to use external webhooks in your workspace and/or install Slack apps, the Request to install screen displays. If you do not require permission to install your app, this screen does not display; skip to Step 5.

    Request to install your app

  4. Request your Slack workspace administrator permission to install your app to the workspace, and then click the Submit Request button.
  5. Install your app to your Slack Workspace. For more information how to do so, go here.

Install Your App to Your Slack Workspace

Install your app to your Slack workspace. Your Slack workspace administrator may require permission to install an app to the workspace. Refer to one of the following topics depending on whether you must request permission:

Install Your App to the Workspace If Permission Is Not Required

Follow these steps to install your Slack app to your workspace if you do not need to request permission to do so:

  1. Under Settings in the left menu, click Install App for your app. The Install App to Your Team screen displays.

    Install App to Your Team screen

  2. Click the Install App to Workspace button.
  3. From the Post to drop-down menu, select from which channel to install your app.

    Select from which channel to install your app

  4. Click the Authorize button on the following page.

    Authorize installation of your app
Install Your App to the Workspace If Permission Is Required

Follow these steps to install your Slack app to your workspace if you must request permission to do so:

  1. Under Settings in the left menu, click Install App for your app. The Install App to Your Team screen displays.

    Install App to Your Team screen

  2. Click the Request Approval button. The Request to install {your app name} screen displays.

    Request to install your app

  3. Request your Slack workspace administrator permission to install your app to the workspace.
  4. Click the Submit Request button.
  5. After your app has been approved for installation, go to Basic Information (under Settings in the left menu), and then expand the Install your app to your workspace section.
  6. Click the Install App to Workspace button.
  7. From the Post to drop-down menu, select from which channel to install your app.

    Select from which channel to install your app

  8. Click the Authorize button on the following page.

Make Revisions to the BPMN File

Refer to the following topics how to make revisions to the Purchase-Request-Formio.bpmn file that you downloaded from the ProcessMaker I/O Examples Portal:

Replace the Webhook URL for Your Slack App into the BPMN file

After your Slack app has been created and installed to your team workspace, you must replace your app's webhook URL in the Purchase-Request-Formio.bpmn file with the default URL in the file. This allows your app to receive incoming messages.

Follow these steps to get your app's webhook URL, and then revise the BPMN file:

  1. Under Features in the left menu, click Incoming Webhooks for your app. The Incoming Webhooks page displays.
  2. In the Webhook URLs for Your Workspace section, click Copy in the Webhook URL field to copy the webhook URL to your Clipboard.

    Copy the webhook URL

  3. Open the Purchase-Request-Formio.bpmn file in any XML-compliant text editor.
  4. Search for all instances of webhook_url. In each instance, replace the default URL value with your app's webhook URL. Example: https://hooks.slack.com/services/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.
  5. Save the Purchase-Request-Formio.bpmn file.

Optionally Customize the Default Messages Used in This Example

Though not necessary for this example to function, you can change the default messages that display through your Slack app and email. These messages are performed by the Slack\SendMessageConnector and the Email connector. For information in which tasks messages occur, refer to Messages.

Refer to the following topics how to customize these default messages:

Customize the Slack Message That Displays When a New Purchase Request is Submitted

After a purchase request is submitted, the Slack\SendMessageConnector uses the following content in the BPMN file that includes variable placeholders:

[The new request for the purchase {request.data.itemName} for sum {request.data.purchaseSum}  from {request.data.orderDate} {request.data.email} is created!

The case number is {request.data.orderNumber}.


]

This message contains the following variable placeholders:

  • {request.data.itemName}: Represents the purchase request item entered into the Purchase Order Form
  • {request.data.purchaseSum}: Represents the sum of all purchase request items
  • {request.data.orderDate}: Represents the date the purchase request was submitted
  • {request.data.email}: Represents the purchase requester's email address
  • {request.data.orderNumber}: Represents the process case number associated with the purchase request

If you customize this message, save the BPMN file after making changes.

Customize the Slack Message That Displays When a Purchase Request is Approved

After a purchase request is approved, the Slack\SendMessageConnector uses the following content in the BPMN file that includes variable placeholders:

[The request for the purchase {request.data.itemName} for sum {request.data.purchaseSum}  from {request.data.orderDate} has been approved!

The case number is {request.data.orderNumber}.


]

This message contains the following variable placeholders:

  • {request.data.itemName}: Represents the purchase request item entered into the Purchase Order Form
  • {request.data.purchaseSum}: Represents the sum of all purchase request items
  • {request.data.orderDate}: Represents the date the purchase request was submitted
  • {request.data.orderNumber}: Represents the process case number associated with the purchase request

If you customize this message, save the BPMN file after making changes.

Customize the Slack Message That Displays When a Purchase Request is Rejected

After a purchase request is rejected, the Slack\SendMessageConnector uses the following content in the BPMN file that includes variable placeholders:

[The request for the purchase {request.data.itemName} for sum {request.data.purchaseSum}  from {request.data.orderDate} has been rejected!

The case number is {request.data.orderNumber}.
]

This message contains the following variable placeholders:

  • {request.data.itemName}: Represents the purchase request item entered into the Purchase Order Form
  • {request.data.purchaseSum}: Represents the sum of all purchase request items
  • {request.data.orderDate}: Represents the date the purchase request was submitted
  • {request.data.orderNumber}: Represents the process case number associated with the purchase request

If you customize this message, save the BPMN file after making changes.

Customize the Approval and Rejection Email Messages That Are Delivered to the Purchase Requester

After the requester's purchase order is approved or rejected, the Email connector delivers an email to the requester's email address. In this example, the email message varies depending on whether the requester's purchase order was approved or rejected.

The Email connector uses the following content in the BPMN file:

<bpmn:extensionElements>
<pmio:connector>
<pmio:inputOutput>
<pmio:inputParameter name="to">{request.data.requesterEmail}</pmio:inputParameter>
<pmio:inputParameter name="from">demo@processmaker.com</pmio:inputParameter>
<pmio:inputParameter name="body"><![CDATA[Hello {user_name},

We just wanted to let you know, that your request for the purchase {Purchase_Item} for sum {Purchase_Sum} from {Request_Date} has been approved!

For your records, the case number is {AppNumber}.

Thank you for your job!]]></pmio:inputParameter>
<pmio:inputParameter name="subj">Your request is completed!</pmio:inputParameter>
<pmio:inputParameter name="options"><![CDATA[{"ignore_exception":true}]]></pmio:inputParameter>
<pmio:inputParameter name="to_name">{request.data.requesterName}</pmio:inputParameter>
<pmio:inputParameter name="from_name">Approver</pmio:inputParameter>
<pmio:inputParameter name="reply_to">demo@processmaker.com</pmio:inputParameter>
<pmio:inputParameter name="reply_to_name">Approver</pmio:inputParameter>
</pmio:inputOutput>
<pmio:connectorId>SendMailConnector</pmio:connectorId>
</pmio:connector>
</bpmn:extensionElements>

This part of the script is used when a purchase request is approved:

[Hello {user_name},

We just wanted to let you know, that your request for the purchase {Purchase_Item} for sum {Purchase_Sum} from {Request_Date} has been approved!

For your records, the case number is {AppNumber}.

Thank you for your job!]

This part of the script is used when a purchase request is rejected:

[Hello {request.data.requesterName},

We regret to inform you that your  request for the purchase {request.data.itemName}  for sum  {request.data.purchaseSum} from {request.data.orderDate} has been rejected.

For your records, the case number is {request.data.orderNumber}.

Better luck next time!]

If you customize these messages, save the BPMN file after making changes.

Import the Revised BPMN File to Your ProcessMaker I/O Environment

Follow these steps to import the revised Purchase-Request-Formio.bpmn file into your ProcessMaker I/O Environment:

  1. Log on to your ProcessMaker I/O account, and then access your running Environment if you have not done so. For information how to do so, go here.
  2. Click the Environment name to display your Environment's dashboard.
  3. Click the Import tab, and then click the Choose File button to upload the revised BPMN file from your computer to your Environment.

Process Execution

After completing all these steps, you're ready to use this example. Refer to the following topics regarding process execution:

Initiate the Process

To initiate a case of this process, follow these guidelines:

  1. Open the Purchase Order Form.
  2. Enter the following information for a purchase request, and then submit the form:
    • Requester Name
    • Requester Email
    • Purchase Order Number
    • Order Date
    • Item
    • Item Cost
    • Quantity
    • Business Need
  3. Slack notifies the configured channel that a new purchase order was submitted.

Complete the Process

To complete a case of the process, follow these steps:

  1. Open the Purchase Approval Form after submitting the Purchase Request Form. Information entered into the Purchase Request Form displays in the Purchase Approval Form.
  2. Enter approver comments, and then approve or reject the purchase request.
  3. Slack notifies the configured channel that a new purchase order was submitted.
  4. The purchase requester receives an email whether the purchase order was approved or rejected.

View and Delete Processes

To view cases (or instances) run against a process, follow these steps:

  1. Log on to your ProcessMaker I/O account, and then access the Environment running the process.
  2. Click the Processes tab. If the process has cases against it, an arrow displays to the left of the process name.
  3. Click the arrow to display information about that process's cases.

To delete a process (and all cases for that process), click the Delete button for that process. To delete all processes for this example, delete Purchase.

Detailed Description of the "Purchase Request Use Case Using Form.io"

Refer to the following topics regarding a detailed description of this use case:

Process Lane Descriptions

Each process lane in this process is briefly described below.

Process Lane Description
Financial Department This example uses one process lane.

Process Task Descriptions

Tasks in this process are described below in the order they appear in the process scheme from left to right, top to bottom.

Task Type Process Lane Connector Description
Form IO Webhook start event Financial Department Starts the process after a purchase requester submits a Purchase Order Form.
Send Notification to Slack service task Financial Department SendMessageConnector](https://www.processmaker.io/connectors-list/#classes/App_Models_Process_Processor_Connectors_Slack_SendMessageConnector.xhtml) This task sends a message to the designated Slack channel that a new purchase request has been created.
Form.IO Purchase request for approval user task Financial Department The purchase order approver views the Purchase Approval Form, and then approves or rejects the purchase request. After the approver makes a decision, process routing depends on that decision.
Send Approval to Slack service task Financial Department SendMessageConnector](https://www.processmaker.io/connectors-list/#classes/App_Models_Process_Processor_Connectors_Slack_SendMessageConnector.xhtml) This Slack connector sends a message to the designated Slack channel that the purchase request is approved only if the purchase order was approved.
Send Decline to Slack service task Financial Department SendMessageConnector](https://www.processmaker.io/connectors-list/#classes/App_Models_Process_Processor_Connectors_Slack_SendMessageConnector.xhtml) This Slack connector sends a message to the designated Slack channel that the purchase request is declined only if the purchase order was rejected.
Send email with approval service task Financial Department ConnectorMail The email connector sends a message to the requester that the approver approved the purchase request only if the purchase order was approved.
Send email with rejection service task Financial Department ConnectorMail The email connector sends a message to the requester that the approver rejected the purchase request only if the purchase order was rejected.

Forms

Refer to the following topics regarding forms in this use case:

Purchase Order Form

In this example, the Purchase Order form is designed in Form.io. The purchase requester enters information into this form to submit a purchase request.

Element Label Element Type Enabled Required Data Type Element Description
Requester Name Text Box Y Y String Requester's full name. Displays in the Purchase Approval Form field of the same name.
Requester Email Text Box Y Y String Requester's email address. Displays in the Purchase Approval Form field of the same name.
Order Number Text Box Y Y String Number for the Purchase Order. In this example, this is can be any number. Displays in the Purchase Approval Form field of the same name.
Order Date Date Control Y Y Date Date the purchase request is submitted. Displays in the Purchase Approval Form field of the same name.
Item Text Box Y Y String String representing the item to be purchased. Displays in the Purchase Approval Form field of the same name.
Item Cost Text Box Y Y Integer Cost of one item. In this example, US dollars are the units of currency. Displays in the Purchase Approval Form field of the same name.
Quantity Text Box Y Y Integer Number of items to purchase. Displays in the Purchase Approval Form field of the same name.
Purchase Sum Text Box N N/A Integer Calculates the cost of the purchase request using entered values to the Item Cost and Quantity fields using this formula: Item Cost x Quantity.
Purchase goal Text Box Y N String Describe the business value that fulfilling the purchase request brings. Displays in the Comments field within the Purchase Approval Form.
Submit Button Y Y N/A Click to submit the purchase request.

Purchase Approval Form

In this example, the Purchase Approval Form is designed in Form.io. The approver reviews the purchase request, and then decides to approve or reject the purchase request.

Element Label Element Type Enabled Required Data Type Element Description
Requester Name Text Box N N/A String Requester's full name. Displayed from the Purchase Order Form field of the same name.
Requester Email Text Box N N/A String Requester's email address. Displayed from the Purchase Order Form field of the same name.
Order Number Text Box N N/A String Number for the Purchase Order. Displayed from the Purchase Order Form field of the same name.
Order Date Date Control N N/A Date Date the purchase request was submitted. Displayed from the Purchase Order Form field of the same name.
Item Text Box N N/A String String representing the item to be purchased. Displayed from the Purchase Order Form field of the same name.
Item Cost Text Box N N/A Integer Cost of one item. In this example, US dollars are the units of currency. Displayed from the Purchase Order Form field of the same name.
Quantity Text Box N N/A Integer Number of items to purchase. Displayed from the Purchase Order Form field of the same name.
Purchase Sum Text Box N N/A Integer Displayed from the Purchase Order Form field of the same name.
Comments Text Box N N/A String Describes the business value that fulfilling the purchase request brings. Displayed from the Purchase goal field within the Purchase Approval Form.
Approver comments Text Box Y N String Describe the decision to approve or reject the purchase request.
Approve Button Y N N/A Click to approve the purchase request.
Reject Button Y N N/A Click to reject the purchase request.

Messages

All messages are performed by the Slack\SendMessageConnector and the Email connector.

Message Title Task Connector Content
New purchase Send Notification to Slack SendMessageConnector](https://www.processmaker.io/connectors-list/#classes/App_Models_Process_Processor_Connectors_Slack_SendMessageConnector.xhtml) The new request for the purchase {request.data.itemName} for sum {request.data.purchaseSum} from {request.data.orderDate} {request.data.email} is created!
The case number is {request.data.orderNumber}
Approval notification to approver Send approval to Slack SendMessageConnector](https://www.processmaker.io/connectors-list/#classes/App_Models_Process_Processor_Connectors_Slack_SendMessageConnector.xhtml) The request for the purchase {request.data.itemName} for sum {request.data.purchaseSum} from {request.data.orderDate} has been approved!
The case number is {request.data.orderNumber}
Decline notification to approver Send decline to Slack SendMessageConnector](https://www.processmaker.io/connectors-list/#classes/App_Models_Process_Processor_Connectors_Slack_SendMessageConnector.xhtml) The request for the purchase {request.data.itemName} for sum {request.data.purchaseSum} from {request.data.orderDate} has been rejected!
The case number is {request.data.orderNumber}
Approval notification to requester Send email with approval Email connector Hello {request.data.requesterName},
We just wanted to let you know, that your request for the purchase {Purchase_Item} for sum {Purchase_Sum} from {Request_Date} has been approved!
For your records, the case number is {request.data.orderNumber}
Rejection notification to requester Send email with decline Email connector Hello {request.data.requesterName},
We regret to inform you that your request for the purchase for sum {request.data.itemName} from {request.data.orderDate} has been rejected.
For your records, the case number is {request.data.orderNumber}.
Better luck next time!