Nintex Workflow Cloud - Part 6 - Building a Workflow

Document created by butlerj Support on Oct 23, 2018Last modified by butlerj Support on Oct 26, 2018
Version 3Show Document
  • View in full screen mode

Prepare for Success

  • You must have at least the following permissions within Nintex Workflow Cloud to complete this step
    • Designer

 

Building Workflows

Every Nintex Workflow Cloud tenant comes with several draft workflows loaded in the dashboard. This part will walk you through configuring a couple of the workflows as a training exercise.

 

My First Workflow

{Template 1} My First Workflow demonstrates how to use a workflow to let people know when a business process has started. The workflow collects an email address and message from a form and then sends the message as a pre-formatted email. This simple workflow is actually a very powerful prototype that you can reuse in an enterprise workflow. By immediately replying to users, you set their expectations and give them the confidence that the Submit button has actually started a workflow process.

 

Manual “process started” notifications tend to be inconsistent as each notification is handled in a slightly different manner. This results in lost time, missed opportunities, and false starts.

 

With an automated system using the Nintex Workflow Cloud, you create a consistent process where each workflow start is handled with a best practice response.

 

The basic workflow

This workflow responds to an email address added to an  form by sending a customized email to that address.

 

Steps:

  1. Workflow starts when the user fills out an  form (with the information below) and clicks Submit.
    1. Recipient email
    2. Message
  2. Workflow sends email combining the message and pre-formatted text to the recipient email address.
  3. Workflow ends.

 

Quick start

  1. Open {Template 1} My First Workflow from the Workflows list on the dashboard.
  2. Select Publish, Assigned use = Development from the toolbar to publish your workflow. 
  3. Test your workflow by entering your email address and a message in the  form and clicking Submit.

 

Video walkthrough

 

 

Email Approval

{Template 2} Email Approval demonstrates how to add an approval process to {Template 1} My First Workflow. Say a seller wants an email sent to potential customers with an introduction customized by a salesperson. The email requires approval as it may include discounts the seller only offers to select customers.

 

A similar manual approval process would tend to be inconsistent as each request and reply would be handled in a slightly different manner. This can result in lost time, missed opportunities and false starts.

 

With an automated system based on this template, you can create a consistent process where each request for information is met with a best practice response. From here you can add a couple actions and connectors to create a quick prototype of almost any forms-based approval process.

 

The basic workflow

This workflow supports an  “Request to send information” by collecting a recipient email address and message, as well as a reviewer’s email address. If the reviewer approves, the workflow sends the message to the recipient.

 

Steps:

  1. Workflow starts when the user fills in an  form (with the information below) and clicks Submit:
    1. Recipient email
    2. Recipient message
    3. Reviewer email
  2. Workflow sends a pre-formatted email to the reviewer asking for approval or rejection.
  3. Workflow handles approval/rejection:
    1. Approval sends the message to the recipient.
    2. Rejection sends the reviewer an email.
  4. Workflow ends.

 

Quick-start

  1. Open {Template 2} Email Approval from the dashboard.
  2. Select Publish and copy the URL for the form.
  3. Test your workflow:
    1. Enter a message and two email addresses in the form and click Submit.
    2. Reply to the Request for approval to send a message… email with Approve or Reject.
  4. Verify the workflow.

 

Video Walkthrough

 

Check for Success

  • Were you able to publish a workflow successfully?
  • Were you able to approve the task through email?

 

 

 

Attachments

    Outcomes