Invalid Form Notification for Users

Click on the Continue or Finish button in a flow that contains invalid data or required fields that are empty ( Buttons are greyed out), the message shown below will display. This alert is very helpful to users when trying to determine why a step in the does not submit.

Unchecking the enable if valid on the submit button of a form will not result in the alert and an invalid form will be submitted. You will not see this message if you enable the Fast Finish feature in your work flow.

Approval Flows

Approval workflows are very easy to automate in . The requestor fills out the original form (or set of forms) electronically and the flow is then routed it to the appropriate person or persons according to the desired business scenario. They’re notified with an email and can take action instantly using any device e.g. instant approval using a smart phone. E-signatures are collected and pdfs can be generated along the way.  offers multiple integration options so you can save your data. 

Approving a Task

Reviewing a task for approval is very easy in  using the Task List. The approver can use the  Quick Approval or the  Perform icons to  display the approval step. Quick Approval displays a Quick View of the task without displaying the entire form. It allows the user who's responsibility it is to review the task (manager, supervisor, reviewer etc.) to add a comment, approve or reject, sign and pass it to the next user in the flow. This works well on mobile devices. Of course, if the approver wants to see the entire form they can click the Details button.

 Follow these instructions to approve a task for the flow that you downloaded:

1. Access the flow from your space. Log in to . 
2. Click the appropriate tab then select the flow from the choices.
3. Run the flow to a step that requires an approval. - (manager, VP, Payroll) .
4. Check the email for any user whose role is manager. Click on the link in the email.
5. Log into  as the user that can perform this step. 
6. Access the task by clicking the Important Items tab and then click on the Task List.
   1. For a quick approval, click the    Quick View icon. If the task does not have a  Quick View icon, click the  Perform icon. Notice the task is now locked so no one else can review it.
   2. Here is an example of Quick Approval for the Expense Statement flow. If the approver wants to see the Expense Statement first, then click the Details button.
      
   3. Sign if required. If you clicked on the Quick View icon, click  the Approve button. a "Task successfully approved" message displays. Logout. 
7. If you clicked on the  Perform icon, fill in the required fields, clclick the button on the screen to advance to the next step or complete the flow. The label of the "Continue" button may differ as this is customizable by the flow designer. The task disappears from the task list.
8. If the flow has additional steps, then check for a task notification email with a link to the task, for a user who can perform that step, then login if required. For example, the third step in the Expense Report flow is performed by a user with the role of Finance and the final step is performed by a user with the role of CFO.
9. Access the task by clicking the Important Items tab and then click on the Task List. Approve each step. 
10. Complete the remaining steps for the flow. Logout. 

Rejecting a Task

A non-admin user can send a task back to a previous step by clicking the Reject button. The Reject button is configurable by the designer so all steps in the flow may not have one. 

Let's consider an Expense Report workflow where the first step is performed by the employee, then it is routed to the employee's manager for approval/rejection. If approved, the workflow is then routed to the Payroll department for final processing. A Reject button has been configured for the Manager and Payroll steps and email notification is turned on for all participating users.

Employee William accesses his company's HR portal and logs in to . He fills out and submits his Expense Report  then he logs out of .

William's manager, Jerry receives a task notification email informing him there is a task on his task list that requires his attention.

Jerry clicks the link in the email, logs into  from a mobile device and clicks the the  Quick View icon.

Jerry adds a comment, then aproves the task by clicking on the Approve button. The "Task successfully approved" message displays and Jerry logs out of .

All users who work in the Payroll department receive a notification email and the workflow is routed to their task lists.

Sue, who is a Payroll department employee, clicks the link in the email, logs into , performs the task and notices that William neglected to attach images of his receipts.

Sue clicks the Reject button. She rejects the task back to the step in the flow performed by William by selecting that step from the Prior Activity dropdown. Then she provides the reason for the rejection.

She clicks Submit on the Rejection screen and sees the "Task successfully rejected" message.

The task is removed from Sue's task list and she logs out. William receives an email asking him to attach the receipts. 

William clicks on the link in the email, logs into  and accesses the task from his Task List.

He uploads the receipts then resubmits the Expense Report. The workflow is routed to Jerry, who can reject the task and send it back to William or approve it. If approved, the workflow will once again be routed to the Payroll department employees. Now that the receipts are attached, the first employee in Payroll to perform the task can complete the final processing of William's Expense Report.  

Flows with an Email or HTTP  steps cannot be reset to those activities. You can reset a task to an activity with a precondition provided that activity was executed and the precondition still holds. You cannot reset a task to a Summary Step. 

Notification Email

There are many places that generate emails: task notification, activity document action, anonymous client activities, form action, escalation reminders.