Live Forms provides a method to show validation errors at the time of submission. Click on the Continue or Finish button in a flow that contains invalid data or required fields that are empty and the invalid controls are highlighted with a background color. Refer to this documentation for the details.
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.
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:
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 approves 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 Castle by selecting that step from the 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 a customized email asking him to attach the receipts.
William 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.
Click the icon on the Task List to search for a form you have saved and want to continue, that you have submitted in the past, or to search for a flow you have participated in. You can narrow your search to specific forms or flows, a date range when you performed a task or only tasks that ended with errors. You can check one or more task states (Saved, Submitted, WAITING, PENDING, ABORTED) to include/exclude tasks from the search results.
Search will only show tasks that the user has participated in.
Select a Form/Flow from the dropdown and Filter Form/Flow by Data" table becomes visible and enabled. You can use this table to optionally select fields that are set up as Searchable Fields in your form/flow by the designer as search criteria.
Tenant Admins and users with flow admin permission are able to search for tasks that were performed by other users. One very common function is to search for tasks that are locked by a particular user so that the flow admin can modify them and reassign them to another user or role -- for example if a person goes on vacation and you need to move a saved or pending form or flow to another user.
If no matching tasks are found as a result of your search, you will see this message:
Users may not have all the information required to complete a form/flow in a single session. offers a Save/Load feature that adds a Save button to the bottom of the form: Users can partially complete forms/flows including leaving required fields blank and even having invalid data in form fields then click Save. The partially completed form is saved to the user's Task List. Later the user can re-open the form either in the same browser or a different browser or even from a different computer, and reload the partially completed form and continue working on it. You can save the form/flow as many times as you like. Clicking the Saved Tasks icon displays all tasks partially completed by the user. Each time the Save button is clicked is tracked by creating entries in the Audit Trail. Saved forms are not the same as submitted forms. Saved forms do not appear in the Submissions Repository. Saved forms can contain invalid data and also contain required fields with no values yet entered. When such a form is re-loaded the missing and invalid values are again flagged as such by . And the form cannot be submitted (the submit button will be grey'd out) until corrections are made to those fields.
Follow these steps to Save a form:
If your form/flow does not have a Save button, contact the form/flow designer.
offers the flow designer many ways to send emails from workflows. You can:
The Email in the flow designer palette is ONLY used to route a workflow to someone who does not have a login(anoymous user). It does send an email to the anonymous user that contains a link to the step in the flow that the anonymous user performs. The anonymous user completes the step and then the workflow is routed back to a user who must login for the workflow to continue. Examples of workflows that would have an an anonymous email step would be a request to an outside vendor for a quote, or a Purchase Order that is sent to the customer for approval. Refer to the Flow Tutorial for step by step instructions to implement this feature for a Purchase Order workflow.
The link in the email sent to an anonymous user can be clicked more than once in a screenflow consisting of an Email step followed by multiple sequential anonymous steps. The anonymous user is brought back to the flow at the current/latest anonymous step if the Save on Navigate feature is selected.
For example, imagine a New Listing Agreement workflow where the Real Estate agent can elect to send an email to the seller (anonymous user) to collect the property details. In this scenario, the agent fills in steps 1 and 2 of the flow supplying the Seller's email address. The Seller receives an email with a link to the first anonymous step (Seller Information). The Seller clicks on the email link, completes the Seller Information and Property Information steps then the flow is routed back to the agent for review.
In the designer, the flow would look like this: Notice the Seller and Property information steps represent a screenflow since they are both filled out by the same person (Seller).
Let's say the Seller completes the Seller Information step then closes the browser. When the seller clicks on the link in the email again, the Seller will be directed to the Seller Information step.
If the Save on Navigate property is checked for this workflow then the anonymous user is brought back to the flow at the current/latest anonymous step (Property Info) when they click the email link a second time.
When a user has the role or user required to execute the next step in a flow the prior behavior was to allow the current user to immediately navigate to the next step. The flow was not saved to the submission repository. In effect, the consecutive flow steps became part of a screen flow rather than a workflow step as the designer intended. The new behavior correctly saves the flow to the submissions repository, puts the flow on the task list of the user(s) and sends task notification emails to the user(s).
The Navigation toolbar provides the ability for a user to navigate back and forth between the steps of a workflow. This is helpful if the user needs to return to a previously competed step to make a correction or review the entered data. Editing of previously completed steps in a workflow is no longer possible if the previous step was completed by a different user than the current user. Previously completed steps are now rendered as read only unless it is a prior step for the same user, with no intervening steps belonging to another user. This feature is referred to as View mode.
Navigating through completed steps rendered in View mode using the the Continue button, skips completed steps such as and anonymous Email. Configured document actions are not re-executed in View mode.
Let's consider the example of a new Employee On Boarding workflow, configured with the navigation toolbar. The first 4 steps in this workflow are referred to as a screenflow since they are all completed by the new employee. The screenflow in this example, consists of an Employee Information, W -4 Allowances, Education, Summary and Confirmation forms. New employee, Tom, realizes when he gets to the Confirmation step(4) that he needs to make a correction on the Allowances step (2).
Tom clicks the Allowance step in the navigation toolbar or the details button on the Summary step and is able to edit the data to make his correction. Tom clicks the Continue button to return to the confirmation step, signs the confirmation form then sends the workflow to his manager.
Before manager Jerry approves the workflow, he wants to review the previously completed steps to ensure all is in order. Jerry clicks on the Employee step of the navigation toolbar and is able to review the information but he will not be able to edit it.
Clicking the Continue button displays the subsequent tasks in View mode and eventually brings him back to the Manager Approval step where he can approve or reject the task.