| Section | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Invalid Form Notification for Users
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 ( 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.
and the invalid controls are highlighted with a background color. Refer to this documentation for the details.
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:
...
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.
...
Saving forms/flows to complete at a later time
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:
- Logon to your space as f_tom.
- Select a form/flow from the tab you created. Fill in some parts of the form/flow but do not complete it. Click the Save button. The "Save Successful" message will display.
- Click the
icon to display your Saved forms.
- Click the
- Save the form a third time then complete the form/flow.
| Note |
|---|
If your form/flow does not have a Save button, contact the form/flow designer. |
Searching for Tasks
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, submission status or only tasks that ended with errors. Search will only show tasks that the user has participated in.
Notification Email
...
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:
Sending Emails in
offers the flow designer many ways to send emails from workflows. You can:
- Configure Task Notification emails - users receive an email informing them that there is a task on their Task List that requires their attention.
- Send an email when a flow is completed. This email is configured through the Doc Action wizard and can be customized.
- Send an email when one of the steps in the middle of the flow is executed. This email is configured through the Activity Doc action wizard and can be customized.
- An email is sent to a user when a task is rejected. This is an automatic function of the rejection feature and the email cannot be customized at this time.
- Escalation emails - tasks must be completed before a deadline. Designers configure the users that receive reminder emails and an email that is sent when the deadline expires.
- Route a workflow to someone who does not have a Live Forms login (anonymous user) - discussed below:
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.