When you click on any step in the flow,  a series of action icons displays depending on the step type. Creating a flow step by dragging/dropping an existing form or a New Form from the Palette shows these icons:

• - Cog icon - Click this icon to edit Step Properties. This icon is displayed when you select the flow step and in the Properties Navigator on the left side of the designer. 
  • Clicking the Edit Step Properties icon on a flow step displays tabs to set up Settings, Assignment, Messages, Rejection, Precondition, Escalations, Emails, Web Hook, Quick Approval and Geo Location  as shown in the image above.
  • Clicking the Edit Step Properties from the Properties Navigator or simply clicking on a section of the Properties Navigator brings you directly to the tab for immediate editing.
• - Chain link icon - Click this icon to create Linked Steps. Refer to Linked Steps in a Flow for a discussion of this Flow Design pattern and when you should use it.
• - Download Arrow over bar - Use this icon to download the step of the workflow as a standalone form. You may want to do this if you update the step in the flow designer and you want to keep your Forms and Flow libraries in sync.
• -  Pencil icon - Click this icon to make changes to a flow step. The form will open in the Forms Designer inside of the Flow Designer. Remember, the form in the Flow Designer is a copy and any form changes will not automatically sync up with the original form in your Forms library.
  
• - Minus icon - Use this icon to delete a step in a workflow. You will NOT be asked to confirm the deletion. Once clicked, the deletion is permanent.

If your step is a Summary, HTTP or Linked step, you will only see the Edit Step Properties and Delete icons.

Properties Navigator

When you click on a flow step, a Properties Navigator panel displays in the lower-left portion of the Flow Designer. This panel shows information about important properties setup for this flow step. Not all of the configured properties are shown in this view. Clicking inside a section or clicking on the Edit Step Properties icon in a section of the Properties Navigator immediately displays the property tab for editing.

The Properties Tabs work the same way whether you open them from the Navigator or from the flow step. Here is what you need to know:

•  If you are working on several tabs at one time, you can navigate to other tabs and make changes there. Use the left and right arrows at the top of the screen to display additional tabs. You must click the Submit button when you are finished configuring Step Properties  to save your changes. Remember to save the workflow.
• will validate the Property Settings when you click Submit. If a property value is invalid, the tab(s) will not close and a  message will display telling the designer that there are corrections to be made before saving. The screen will stay on the current tab if there is a validation error.  Otherwise, another invalid tab will be auto selected (starting from left to right) if another tab needs attention. Tab labels with invalid entries display in red.
  
  
  
• Clicking on the Cancel button closes the tab(s). You will be asked to confirm if any changes were made.
• Hover over any field on the Properties tabs to see a helpful hint providing information about the property. Some fields contain instructions to guide you.
• Clicking on the down arrow for a property shows an unfiltered list of choices applicable to that property. For some properties, you may see templatized controls from your flow and flow/special templates provided in .
• In some cases, you can type ahead to narrow down the list. Use the up/down arrows, the Enter key or click an option with your mouse to select an option. Use the Backspace, Delete or click the x on a selected property to delete it.
• Typing a opening curly brace into some fields, followed by the name of a control, show a list of the fields in your flow that match the entered text and will be added to the field as a control template.
• On some tabs, you may have to slide the toggle to the right to turn on a feature.
  
  

Each step property setting is described below. 

Click the Help icon at the top of any tab for a quick tour of the features in that section. Currently tours are only available for Cloud customers.

Settings

Specify General Settings for a step in your flow on the Settings screen.

Name

This is the name of the form that you dragged from the flow designer palette and dropped into your flow. If you drag and drop a New Form from the palette, you can change this name to something meaningful. Form names longer than 60 characters will be truncated. The Flow Step name can also be edited from the Flow designer canvas by clicking the flow step then clicking the pencil icon above the Properties Navigator. Edit the name then click the checkmark to save or the cancel icon to discard your changes.

CSS Class

This CSS class name will be added to the XHTML markup generated for this step in the flow. Refer to the CSS class topic for details.

Continue Label

This is the label of the button that is displayed at the bottom of every step in the flow. The default label is Continue for all flow steps except the last step where it defaults to Finish. You can use templates to customize the label on different steps of the workflow. 

Save Label

The Save button label can be customized for each step in your workflow. For example, you can change the button text to Save for Later. This will help users understand what to do if they want to save a partially completed flow. To show the Save button on a flow step, the Editing Step Properties#Save/Load property must be checked on the entire flow and on the flow step.

Decorator

The designer can select a decorator for the steps in a flow by choosing an icon from the Decorator dropdown.  The selected decorator will replace the default number for the step of the flow on the Navigation toolbar. The image shows the navigation bar for a flow that does not have a decorator selected on the Employee Information step and then shows how the navigation bar looks when the pencil icon is selected for this step.

 Click here to see an image of the Navigation Bar with a Decorator selected

Printable

If this is unchecked, then this step will not appear in the printable PDF for the flow. This is commonly used when you add the same form to the flow multiple times or use the linked step feature to duplicate the same form for multiple steps. This is a common design pattern when the same form is passed among multiple people for approval (Approval Workflows). You will only be able to set printable on non-linked steps. The linked steps will not have the Printable property available in the designer. The setting for the non-linked step covers that step and all steps linked to it. The form for these step(s) will only be printed once in the pdf. It is no longer necessary to uncheck the printable property for all but one of the steps in this type of workflow . The designer can have fine grained control over which controls appear in the PDF by editing the step and setting the control's printable property.

Save/Load

If you check this checkbox on the flow level and on the step level, a Save button will be displayed for each step in your flow. If you don’t want users to be able to save partially completed flows and continue them later, uncheck the checkbox so users will not see this button.This feature is useful for flows containing lengthy forms where your users may not have all the information required to complete the form in a single session. By clicking on the Save button, a copy of the flow with all the current values is saved by Live Forms. Live Forms will also generate an entry in the user's task list. Users access the saved flow task from the to continue working on it at a later time.

If you are not authenticated, clicking the Save button will display an authentication dialog that requires you to login. Users can save the flow as many times as they wish.

Saved flows can be monitored in the Submissions Repository. Saved flows can contain invalid data and can also contain required fields with no values yet entered. When such a flow is re-loaded the missing and invalid values are again flagged as such by Live Forms. And the flow cannot be continued/finished until corrections are made to those fields.

This setting overrides the default Save/Load for the flow for this step only. If Save/Load is enabled for the flow as a whole, you can uncheck this property to disable it for specific steps. Click here for an explanation of how the Save/Load feature works.

Save to Role

When you click Save to save a partially completed flow, the saved flow will only appear on your own task list. If you check this box, then the saved flow is assigned to all users in the Role that is specified for the current step. For example, you may have an Issue Tracking workflow where an employee submits an Issue and the Issue can be acted upon by multiple users in the "Admin" role before it is resolved. The first step is filled in by any employee. When the employee clicks Continue, a task is generated for an "Admin" user. Any user with the "Admin" role can perform the task. The user can enter some data and click Save. The flow goes back into a pending state and is placed on the task list for any "Admin" user. A different "Admin" user can pick it up and continue working on the issue. In this manner, you can create a step in a flow that loops several times before continuing. Refer to the Looping between multiple users in a role topic for an example of a flow design pattern that uses Save to Role.

Save to User

When you click Save to save a partially completed flow, the saved flow will only appear on your own task list. If you check this box, then the saved flow is assigned to the user that is specified in the Users property. When you use this feature the User property should contain a template. For example, you may have form that needs to be reviewed and approved in an ad-hoc manner. In this manner, you can create a step in a flow that loops several times and that dynamically routes to different people before continuing. See the flow example Ad-hoc workflow: pass steps between arbitrary users for a deeper understanding of this feature.

Fast Finish

The Fast Finish feature is useful for workflows with many steps. If a user navigates to a previous step to change data, Fast Finish eliminates the need for the user to click the Continue button on the remaining steps of the flow to resubmit it with the changed data. Fast Finish can be selected at the flow level or at the step level. Refer to this feature announcement for more information.

Allow Signature Pad

Check this checkbox if the step in a flow will be using an external signature pad. Leave the property unchecked (default) on the steps that will not be using a signature pad.  See Topaz Electronic Signature Pads topic for the models supported and configuration information.

On This Page:

 

Assignment

Use the Assignment tab to:

• Assign a workflow step to a to a user, role(s) or an email address.

• CC a notification to any additional user(s) who should also know the flow is on this step.
• Customize the Task Notification email message that is sent when the generated task for that step is put on the user's Task List. This email informs the recipients that there is a task that requires their attention.

Assign a Workflow Step to a User, Role(s) or Email Address

Users are given the highest priority at runtime followed by roles and then any email address.

User

This field allows the designer to assign a workflow step to a specific user. Clicking the shows the first 10 users in your tenant in alphabetical order, followed by the first 10 fields in your flow in curly braces, making it a Control Template.

• You can enter a user id. Begin typing in the user id and a list of user names matching the text displays. Use the Enter key, the Up/Down arrows or click an option with your mouse to select a user.
• You can only enter a single username in this field. Ex: nancy. Setting the user property to a comma separated list of usernames, Ex: nancy, prajakta, will not work. This will be treated as a single username.
• This field can use templatized strings for dynamic content. For example, in a Vacation Request workflow, the first step is to be completed by an employee but the second (approval) step must be performed by the employee's manager. i.e. it can contain "{ManagerId}" where ManagerId is the name of a field in a form from a prior step.  will resolve the ManagerId string using the actual value of the ManagerId control and generate a task targeted at that specific user.
• To enter a Control Template, type the opening curly brace - {followed by the control name into the Assign to User field. A list of fields from your flow displays surrounded by curly brackets). Selecting an option enters the control name into the field with the closing curly brace.
  
  

Refer to the workflow topic sending a workflow step to a specific user for an example.

You may want to route a step in a workflow to the user's manager.  provides a built-in template that is available for every transaction. Simply type the template {subject.reports.to} in the User property for that step in your flow. The workflow will then be routed to the user who is specified in the Reports To field on the User's configuration screen

Role

Roles are created by your tenant administrator or automatically imported from your LDAP or Active Directory server. When a role is selected, the step in question can only be performed by users belonging to that role. For example, if you have a Purchase Request workflow where the first step is to be completed by any employee but the second (approval) step must be performed by someone with the "Manager" role, you can select the Manager role for the second step. When an employee uses the workflow, completes the first step and clicks Continue,  will generate a task and place it on the task list for users with the Manager role and display the Pending Msg to the employee.

• You can enter one or more roles. Begin typing in the role name and a list of roles in your tenant matching the text displays. Use the Enter key, the Up/Down arrows or click an option with your mouse to select a role.
• Repeat these actions to select additional roles i.e.Manager, HR 

• This field can use templatized strings to dynamically determine a role at runtime.  For example, you may have a workflow where the first step is a Purchase Order or a Loan Request and the second step is an approval; however the approval must be performed by a Manager if the amount is less than $1000 and a Supervisor otherwise. You will need a control in your form that is populated with the role that you want the flow to navigate to - in this case, Manager or Supervisor. To enter a Control Template, type the opening curly brace - {followed by the name of the control into the Assign to Role(s) field. A list of fields from your flow displays surrounded by curly braces. Selecting an option enters the control name into the field with the closing curly brace. Repeat these actions for the steps in your flow that are going to use the role entered for routing e.g. {ApproveRole}. At runtime.  will resolve the target role using the data in the ApproveRole control and will route the workflow to that specific role. See the workflow example topic determining the role at run-time.

Partial templates with prefixes and suffixes can be used to create a complex role such as floor-manager for workflow routing.

Email Address(No login required)

Use this field to assign a step in your workflow that is going to be performed by an anonymous user. This is a user who will not need to log into your tenant to perform their step. Let's say you have a Purchase Order workflow, where the Order Details are completed by someone in your company and one of the steps is routed to the customer for approval and signature.

• Edit the Purchase Order workflow in the Flows Designer.
• Click on the step(s) anonymous users will perform. Click the Edit Step Properties icon on the step then click on the Assignment tab or click the Edit Step Properties from the Assignment section in the Properties Navigator. This takes you directly to the Assignment tab.
• Enter a valid email address into the Assign to Email Address(No login required) field.
• will check if the address is entered in the correct format and notify the user if it is not.
• Only one email address is allowed.
• This field can use templatized strings to dynamically determine an email address at runtime. To enter a Control Template, type the opening curly brace - {followed by the name of the control that will contain the email address into the field. A list of fields from your flow displays surrounded by curly braces). Selecting an option enters the control name into the field with the closing curly brace. Repeat these actions for additional steps in your flow that are going to be performed by anonymous users.
  
• The flow can be rejected to a task performed by anonymous user.
• Tenant/flow admins can reassign the anonymous step to a different email address.
• The Task Assignment can be CC'd to another user so that in case the link is lost, there is another way to access the task, reassign or resend it. Be aware that first user to click the link will lock the task, so to ensure the intended user performs the task, consider including in the email message a warning such as "A copy of this message has been sent to your manager. Managers should not click the task link."
• Configure a History Message on the step before the Anonymous Task step if you want to see relevant information in the audit trail. The History Message can be templatized so you can see the email address of the recipient.
• The Who can start the flow permission does not need to be set to Public. The Anonymous step will work with any of the Flow Visibility choices.
  

• The Anonymous step uses the {task.perform.url} template in the Task Notification email Message by default. If the anonymous user submits their step of the flow then goes back into the email and re-clicks on the link, the following message displays:
  
  
  

Refer to the Anonymous Participant topic or the Flow Tutorial for an example.

Workflow Task Design Considerations

The designer defines task boundaries by setting assignments (user, role or email address), so each flow step with an assignment is considered a new task. Any subsequent flow steps without assignment are considered part of screen flow of the same task. If the next step is a new task and the current user is eligible to perform it, the user will be provided with a link to continue the flow in the same screen. When the user clicks the link to continue the flow execution, the flow will continue like a screenflow but a new task will be created behind the scenes. 

Here is a diagram that explains how step assignments define tasks:

Having an assignment to a flow step strictly enforces the task boundary and it is applicable for the first step of flow as well. This means to create a task for the first step simply configure the first step with an assignment. Designers can also define flow level Access Control by selecting Custom in the Who can start the flow property and entering user(s) or role(s).

Invalid Task Assignment

For workflows created in v9.0.x and later, when a task that is routed to templatized user, role, or email resolves to null or empty string, the task will be assigned to the "invalid-task-assignment" userId and a notification with be sent to flow admin users (or tenant admin user if no flow admin is configured.) This will enable flow admin users to easily search mis-routed tasks assigned to the "invalid-task-assignment" userId and re-assign to valid user.

One exception to this is when you have both a templatized user and a role assigned, the step will reroute to the Role(s) if the template resolves to null at run time. If the templatized user is valid, Role will be ignored.

Anonymous Steps and the Audit Trail

If your workflow was created in a version of previous to v8.0, then the step performed by the customer (anonymous user) was designed by dragging an EMail or Anonymous Task step from the Palette and dropping it on the Flow Designer canvas. Workflows designed in this manner will still work in v8.0 but the Audit Trail will show the task in a WAITING state.

In version 8.0, the same flow can be designed by simply assigning the step to an Email Address. The Audit Trail, shows the step performed by the customer (anonymous user) in a Pending state and displays the Email address it was sent to.

Setup Task Notification Email

When  generates a task and places it on a user's task list, a notification email is generated.  The email informs the user that there is something on their Task List that requires their attention. A clickable link to the task or the Task List depending on the template that you choose, is included in the email.

You can specify your own email subject and message. The message body can contain HTML and CSS, giving you the ability to generate nicely formatted emails. Form data values can be added to the message subject and body using control template names or flow/special templates provided by .

The designer can also specify email address(es), user(s), and role(s) to receive a CC: of the task notification message. For tasks assigned to an Email Address (No login required), the task will be locked by the first user who clicks the {task.perform.url} link. Designers can help ensure only the intended recipient picks up the task by configuring a warning into the email message such as "A copy of this notification has been sent to your manager. Managers should not click the link above."

Access the Assignment tab for that step to customize the subject and message of the email the user receives.

• You can enter any text you want for in the Subject and Message fields. Clicking on the DEFAULT button, shows "New Task" as the default subject and "You can access your task by clicking <a href="{task.perform.url}">this link</a>" for the default message.
• Clicking on the down arrow, show a list of templatized fields from your flow, flow/special templates provided by and Task Templates that you can use in the body of your email.
  
  • Type the opening curly brace - {- followed by the control name to enter a field from your flow as a template. Selecting an option enters the control name into the field with the closing curly brace
    
    

  • Built-in flow templates

    • {flow.id} - The unique flow instance id. This id is unique for each flow submission.
      
    • {flow.type.id} - The unique id associated with a given flow. See Sharing Forms
      
    • {flow.extid} - Client defined extId passed in the formtype Url parameter.
      
    • {flow.name} - The name of the flow.
      
    • {flow.description} - Description of the flow. 
    • {flow.activity.id} - The Id of the current workflow step.
      
    • {flow.activity.name} - The name of the current workflow step
      
    • {flow.activity.reject.reason} - The reason a workflow step is rejected
      

  • Built-in special templates

    • {subject.id} - logged in user's username. 
    • {subject.roles} - A list of all the roles for the logged in user 
      
    • subject.email - logged in users's email address
      
    • {subject.first.name} - logged in users's First Name

    • {subject.last.name} - logged in users's Last Name

    • {subject.reports.to} - the user id of the person the logged in user Reports To - configured in the user profile by the Tenant Admin. Typically used to designate a manager/supervisor.
      

    • {tn.id} - the Tenant ID where a form/flow is located

    • {tn.name} - the Tenant Name where a form/flow is located

    • {user.id} - Owner of form/flow and user folder name in the filesystem 

    • {app.id} - The unique id associated with a given application. See Sharing Forms
    • {app.name} - The unique name associated with a given application.

Task Notification Email Links

There are two built-in Live Forms templates that can be used to generate a link in the task notification email: {task.list.url} and {task.perform.url}.  To make any of these clickable links in your task notification emails, wrap them in an HTML <a> tag like this:

You can access your task by clicking <a href="{task.perform.url}">this link</a>

Space Specific URL

If you are using the  space feature it is more likely you might want to return to the user's task list in the space. To do this - modify the task notification email  to use a space specific URL. Change the default Task List special template to a space specific URL which will return you to the user's Task List embedded in your chosen space. Create a space specific URL by supplying a URL to the Task List with the space/spaceID/tasklist appended to it.

You have a new task for New Hire. To access your task list,
please click on:
http://10.0.0.14:8082/frevvo/web/tn/mycompany.com/user/designer/space/mycompany/tasklist   

In this example, the url is the space URL with /tasklist appended to it. Users must be logged in for this URL to take them directly to their Task List in your space. On mobile, you will see a Back button rendered to take you back to the space. In both cases, the top browser URL is redirected to the appropriate menu item for your task list so the user will not have to click on the Task List menu tab to display it. If you do not have a task list menu item in your space, you'll end up at the space home page.

See the Email Integration topic for information on setting up email notifications for form and flow submissions. This function uses a similar notification wizard.

The tenant admin can configure the from email address for task notification emails on the admin's Edit Tenant page.

Messages

Setup Task Information, Pending Messages and History Messages on the Messages tab.

• You can display the Messages tab in three ways:
  • Click on the step of the workflow, then click the Edit Step Properties icon then click on the Messages tab.
  • Click anywhere in the Messages section in the Properties Navigator. This takes you directly to the Messages tab.
  • Click the inside the Messages section in the Properties Navigator. This takes you directly to the Messages tab.
• Enter your customized text for each message in the appropriate field.
• Clicking on the down arrow shows a list of templatized fields from your flow, flow/special templates provided by  and Task Templates that you can use in the messages.
  • Type the opening curly brace - {- followed by the control name to enter a field from your flow as a template. Selecting an option enters the control name into the field with the closing curly brace
• Click the Submit button to save the changes or navigate to another tab.
  
  

Task Info

When you save a partially filled flow to continue it later or when  puts a task on your task list as part of a workflow, the task is accessed via your task list. This field controls the text that gets displayed in the user's task list. For more details, see the Using the Task List. This information gives the user(s) more details about the task that is waiting on their Task List. It also helps you to quickly find a particular task if you have a lot of tasks on your Task List.

This field can use templatized strings  for dynamic content, e.g. the Task Info can contain "Vacation Request for {FirstName} {LastName}" where FirstName and LastName are the names of fields in a form from a prior step in the flow. Before putting the task on a user's task list,  will resolve the Task Info string using the actual values of the FirstName and LastName fields e.g. "Vacation Request for Tom Smith".  will truncate the Task Info data to 250 characters.

You access your Task List from your applications home page or from a  Space. You use the Task list to perform tasks assigned to you, to view a task's history, or search for tasks you've participated in — a tenant admin can also search for other users' tasks.

If the Task Information is the same for all the steps of your workflow, you can set it up on the flow level. If you want the Task Info to show something different on a flow step, select the step, select the Messages tab and set up your customized Task Information there. The Task Information on individual flow steps overrides the default Task Info for the flow for this step only.

Pending Msg

Use this property to display different customized messages for each step of your workflow. Pending messages can be setup at the flow or flow step level. Setting this property at the flow step level, overrides any default Pending Msg that is set up on the flow level for all the flow steps.

Designers may want to display different messages to the users submitting each step of the flow. Templates can be used in the messages to provide dynamic content. The Pending Message is best explained with an example.

History Msg

You can use the History Msg property to type a message e.g. {EFullName} requested leave starting {StartDate} for {NumberOfDays} days.  At runtime, will resolve this message using the data from the form and save it in the audit trail. The names in the {} must exactly match the names of the respective controls.

Use the Save on Navigation feature and the history message to log a new submission entry in the Audit Trail every time the workflow navigates to a new step, even if the current user has permissions (the correct role) required to immediately execute that step.

Configure a History Message on the step before the task to be performed by the anonymous user, if you want to see relevant information in the audit trail. The History Message can be templatized so you can see the email address of the recipient.

Rejection

Use the Rejection tab to:

• Specify if a user can reject a step in a workflow or if the step can be rejected to by other users or both.
• Customize the Reject button label on workflow steps that are configured to show one.
• Customize the Subject and Message for the email users receive when a task is rejected.

• You can display the Rejection tab in three ways:
  • Click on the step of the workflow, then click the Edit Step Properties icon then click on the Rejection tab.
  • Click anywhere in the Rejection section in the Properties Navigator. This takes you directly to the Rejection tab.
  • Click the inside the Rejection section in the Properties Navigator. This takes you directly to the Rejection tab.
• Check Reject to Here if the flow may be rejected/reset TO this step.
• Check Reject from Here if the flow may be rejected/reset FROM this step.
• If Reject from here is checked, When selected, sections to customize the rejection email will appear.
• Clicking the Submit button to save your changes.

Rejecting a Workflow

There are three types of rejection scenarios for workflows:

• Reject to Revise - The form is sent back to a prior flow step for correction/more information. This is the Reject to Revise (Easy Reject) feature described below and is built into .
• Reject to Discard - Users pick the option to Reject to Discard the request from an Approval control, enter a status or comment and the flow skips all subsequent steps and completes. A submission is saved into the Submission Repository. It is likely that you may want to implement some custom business rules to fill requirements after the of Reject to Discard option is selected such as display a message to communicate the status to the user. Refer to Reject to Discard to see how the designer can implement this feature in workflows.
• Abort a Task - crumple the form up and toss it into the trash can. Only the Tenant Admin, users who have been granted the Flow Admin privilege for the workflow and the designer who created the workflow have the capability to abort a workflow task. When a task is aborted, all subsequent flow steps are skipped and the form is not saved in the Submission Repository. The Abort feature is built into .

Reject to Revise (Easy Reject)

Steps in a workflow that are routed to different non-admin users other than the person originally performing the step can be rejected (sent back) to a previous step by clicking on the Reject button. The designer can specify which steps display a Reject button and the steps the reject button can reset to. To take full advantage of this feature, make sure email is selected as the notification method for participating users. In-house customers should also make sure email is correctly configured. When a task is rejected, the user who it is being sent back to receives an email informing them of the reason for the rejection. The notification subject of this email is defaulted. The notification message and task history message are set to the specified reason provided by the person rejecting the task. The email shows task information specified by the designer.

Users designated as flow admins can reject a task using the Reject button if configured or the Modify Task icon.

Configure the Reject button

To configure the Reject button on an step of a workflow, follow these steps:

1. Click on the step in your flow where you want to configure the Rejection feature.
2. The Reject to Here checkbox is checked by default. Leave it checked if the flow can be rejected/reset to this step. Check Reject to Here if the flow may be rejected/reset TO this step. This
3. The Reject From Here checkbox is checked by default. Leave it checked if the flow can be rejected/reset from this step.
4. If Reject from Here is checked, you can customize the label of the Reject button and the Rejection email. This is the label used for the Reject button displayed in the form at this step. You can use a template to dynamically set the label.
5. Clicking on the down arrow shows a list of templatized fields from your flow, flow/special templates provided by  and Task Templates that you can use in the rejection email Subject and Message.
   
   • Type the opening curly brace - {- followed by the control name to enter a field from your flow as a template. Selecting an option enters the control name into the field with the closing curly brace
6. Click the Submit button to save the changes or navigate to another tab. Remember, if you navigate to another tab without clicking the Submit button, changes will NOT be saved.
7. Repeat these steps for each step of your workflow.
   

Configuring a Reject button on the first step of a workflow or for the steps in a multipage form/screen flow (steps fill out by the same user) serves no purpose. It is possible to reject to a step with a precondition, provided that step was executed and the precondition still holds.

When a user clicks the reject button, an embedded rejection page replaces the task form on the right side of the task list. This will happen on a desktop or mobile devices. To reject a task, the user selects the user/step that they want to send the flow back to from the To:dropdown. and provides a reason for the rejection. Note the list contains prior flow steps and the first and last names of the users who performed them. 

If a task is accessed from an email that uses the task.perform.url, the user will be taken directly to the task. If the task is then rejected on the desktop, the display rejection popup displays instead of the embedded rejection page.

Configuring Reject for Steps performed by Anonymous Users

Tasks assigned to an Email Address can be rejected from and rejected to, just like any step is the flow performed by a logged in user.

Let's say you have a Purchase Order workflow where the PO is sent to the customer for signature. The designer can configure a Reject button on this step (anonymous) so that the customer can send the PO back to the sender for corrections before signing.

Subsequent workflow steps can be configured to Reject the task back to the customer, if necessary.

Configuring Reject for Screenflows

Steps performed by the same user in a flow are referred to as a screenflow. The steps of the screenflow are considered one task. The reject functionality will allow users to reject only to the beginning of that screenflow. You cannot reject back to steps after step 1 in the screenflow.

Customize the Rejection Email

It is possible to customize the subject and email message body that is sent when a workflow task is rejected. The customized rejection email will be sent when the Reject button is clicked on a workflow step or Quick Approval screen.

You can choose controls from your form which will be added to the Message as templates or you can use built-in templates as described below. Click on thedown arrow shows the list.

•  {flow.name} - Name of the workflow

•  {subject.first.name} - First name of the user who rejected the task.

•  {subject.last.name} - First name of the user who rejected the task.

•  {flow.activity.name} - The step of the workflow that was being performed when the task was rejected.

•  {flow.activity.reject.reason} - The reason for the rejection.

•  {task.perform.url} - The URL to the rejected task.

Here is the default rejection subject and message. Notice the use of built-in templates to pull the following information into the email:

Subject: You have a new task for {flow.name}
Message: <p>This workflow was rejected back to you for further action.</p><p>The work flow was rejected by {subject.first.name} {subject.last.name} at step: {flow.activity.name}. The reason was: {flow.activity.reject.reason}.</p><p>You can access this task at <a href="{task.perform.url}">this link.</a></p>

In-house customers can modify the default subject and message values by changing the text in the web.xml file. Click here for the details.

Click here for an example showing how the Easy Reject feature works.

The "from" email for a rejection is the tenant "from" email. If no tenant "from" email is set, this will default to the admin user's email address.

Reject to Discard

Most often, steps in an Approval workflow can have three possible outcomes.They can be:

• Approved
• Sent back to a previous step for corrections/more information (Reject to Revise)
  
• Rejected and terminated (Reject to Discard)
  

Consider a workflow where Step 1 is filled out by a user, the second Step requires approval by a manager and when approved, Step 3 of the workflow is routed to the VP for review. After approval by the VP, the workflow completes.

The designer must consider what actions the Manager and the VP could take when the workflow appears on their Task List.

• The Manager:
  • Approve the request in which case the workflow moves forward to the next step, VP review. This is the default behavior.
  • Reject the workflow back to a previous step (Reject to Revise) by clicking the Reject button and selecting the step to send the flow back to from the Reject dropdown. The Manager may want to do this because some data needs correction or to obtain more information from the user who initiated the workflow. Reject to Revise is built-in to and can be configured for any step.
  • Reject the request completely (Reject to Discard) in which case the workflow moves forward, skipping all subsequent steps and completes. A submission is created in the submissions repository. This process is configured using the precondition property for workflow steps.
    
    
• The VP:
  
  • Approve the request in which case the workflow completes.
  • Reject the workflow back to a previous step (Reject to Revise) by clicking the Reject button and selecting the step to send the flow back to from the Reject dropdown. The VP may want to send the workflow back to the Manager or to the user who initiated the workflow. Reject to Revise back to a previous step is built-in to and can be configured for any step.
  • Reject the request completely (Reject to Discard) in which case the workflow completes.
    
    

Troubleshooting the Reject Button

Here are some reasons why you might not see the Reject option on a step where "Reject From Here" is selected:

1. If  the Reject To Here option is not selected in the previous steps, then user won't be able to see the Reject button on current step.
2. When consecutive steps are executed by the same user,  treats it as a screenflow. Think of those steps in the screenflow as one task. The reject functionality allows users to reject only to the beginning of that screenflow/task i.e. where the previous user started his work. It won’t allow a reject to the in-between steps.
3. If the immediate steps prior to the current step were performed by the same user, then he/she cannot reject to those steps (the user is rejecting the flow to himself). Users can reject only to those steps performed by other users, or to steps performed by himself that do not come immediately before the current step.
4. If a previous step was skipped because its precondition failed, then the user won't be able to reject to such a step.
5. If a precondition on previous step passed when that step was being performed, but the control values change causing the precondition to now fail, the user might not be able to reject to that step.
6. The Reject button will not be displayed at all if the conditions are such that users cannot reject to any prior steps.

Precondition

Use the Precondition Builder on the Precondition tab to:

• Write the JavaScript for a precondition on a workflow step.
• Provide a short business-level description of the precondition to help make the flow design easier to read.

• You can display the Precondition tab in three ways:
  • Click on the step of the workflow, then click the Edit Step Properties icon then click on the Precondition tab.
  • Click anywhere in the Precondition section in the Properties Navigator. This takes you directly to the Precondition tab.
  • Click the inside the Precondition section in the Properties Navigator. This takes you directly to the Precondition tab.
  • When you add a precondition to a flow step, a yellow Precondition decision diamond is displayed on the Flow Designer canvas. Clicking the icon in the Precondition decision diamond takes you directly to the Precondition tab. If the step has a precondition validation error, the error icon shows instead and the diamond displays with a red color.
    

Preconditions are used to add logic to your flow to skip or perform a step based on the data entered into prior flow steps. They are also used to generate/not generate mapped PDFs. Preconditions are entered into the Precondition property field for a workflow step and are performed if the precondition statement evaluates to true or the field is left empty. The precondition logic is the same used when writing business rules.

There are two entry modes: Precondition Builder mode and code entry mode. Precondition builder mode is turned on by default. The designer can switch back and forth between the two modes.

The Precondition Builder makes it very easy to eliminate incorrect or invalid JavaScript in your precondition statements during the design phase.

• Open the Precondition tab.
• Provide a Precondition Description. This field is optional. If this field is empty, the Precondition logic is described i.e. "LoanAmount is equal to or more than 50000"
• The Precondition Builder is turned on by default. Launch the Builder by clicking in the Precondition logic box or clicking the Edit button. Click the CLEAR PRECONDITION button to remove any existing Precondition logic.
• This editor uses a modified version of the Visual Rule Builder where you can build your precondition statement by selecting controls and conditions from the dropdown lists. Note the field drop downs (left and right sides) will not contain any repeating type fields (tables/repeats).
• Create the Precondition by selecting fields from your flow, an operation and a value. To enter a literal value, slide the toggle to the right. Yo can add more than one condition by clicking on the Add Condition button and modify the logic expression, if necessary.
  
  
  
  Click Accept then Submit to save the precondition or click Cancel to discard. You will be prompted to confirm the cancellation.
  
  
  
  Save the workflow.

When the user completes entry of a precondition via the rule builder, the precondition expression is displayed in the precondition property panel. Click in the precondition area in the properties panel again or click the icon on the diamond shaped decision box to re-run the Precondition Rule Builder.

To manually enter the Precondition JavaScript or edit a precondition created using the Precondition Rule Builder by editing the JavaScript code :

• Slide the Precondition Builder toggle to the left to turn off the Builder. Be aware that taking this action will remove your ability to edit using the Precondition Builder. A warning message will display:
  
  
  
  
• Click the CLEAR PRECONDITION button to remove any existing Precondition logic or edit existing code that is displayed.
• Type the JavaScript into the field.

• Click Submit to save the precondition. If you click Cancel, you will be asked to confirm.
  
  

Changes to the precondition trigger code validation. Appropriate messages are displayed if errors are encountered. Errors with information display if the JavaScript is invalid.

If you have an existing precondition that was manually entered into the Precondition Code field when the Builder was turned off (code mode), slide the  to the right to turn the Builder back on.The existing code will be removed but the Precondition Builder will be available again.

You will see this message:

It is important that designers test the preconditions in your workflow. The Precondition Builder displays an error if it encounters invalid JavaScript, however, runtime errors such as leaving off the .value are not flagged by the Precondition Builder because the JavaScript is valid. For example, the precondition in the image is missing the .value for the Loan Amount field. This precondition will pass the Precondition Rule Builder validation but it will not work. will catch this error when the flow navigates to Step 2. To correct the runtime behavior, change the precondition to LoanAmount.value >=500000

Precondition Examples

 Click here for some Precondition examples

Example 1:

For example imagine a mortgage application in which a Supervisor had to perform a step for all mortgages over 500,000.00. The flow has a 1st step where the applicant enters the loan amount into a field named LoanAmount. Step 2 is performed by a bank Employee and Step 3 is performed by the Supervisor only for mortgages over 500k.

To do this,  use the Precondition Builder or drop in the code to add the precondition  - LoanAmount.value >= 500000 - to Step 3.

Example 2:

You can also set preconditions based on values in dropdowns and radios. For example, imagine the 2nd Step contained a dropdown control named SendToSupervisor with the values Yes/No. The Employee could override the logic in the flow to send for Supervisor approval even for loan amounts under 500,000.00. Add the following precondition - (LoanAmount.value >= 500000) || (SendToSupervisor.value === 'Yes') - to the Supervisor step.

LoanAmount.value >= 500000 || SendToSupervisor.value == 'yes'

Either way the Supervisor step would be skipped for loans less then 500,000.00 or if the Employee set Send To Supervisor to 'no'.

Make sure the controls used in preconditions are required controls. Controls without values used in preconditions will cause an error in the flow. Test for this when you are creating flows with preconditions to ensure that when the flow designer shares the flow with others that it will not display an error.

Example 3:

In this example if the Supervisor was the one to fill the first step of the flow then they were required to enter their Supervisor Title, and that field is thus guaranteed to have a value. In this case, to skip the next step and go directly to the Supervision step, add this code - SupervisorTitle.value != '' " to the second step's precondition or use the builder to create a precondition where the second step only executes if the Supervisor Title filed is empty. Then add another OR statement to the precondition on the Supervisor step to execute that step if the Supervisor Title is filled.

!

Preconditions and Rejecting Tasks to Discard

Preconditions can be used to implement a Reject to Discard scenario as an option for rejecting workflow tasks. Let's say you want to note that a workflow task is rejected (not approved) but still have the form stored as a completed submission in the repository. Adding pre-conditions that evaluate to true to later flow steps will cause those subsequent steps to be skipped and the flow will complete. The flow will be saved in the submission repository with some customized indication that the flow step was rejected. See the Reject to Discard topic for the details and an example.

Escalations

Use the Escalations tab to set up the following on a workflow step:

• The workflow condition that needs to be met for escalations to take effect
• The time interval/due date for a task to be performed or completed
• Specify an action when the deadline is missed - Reassignment to a different user or role, Notification that the task has been escalated or the ability to skip the step and navigate the flow to the next step.
• The ability to skip a step in a workflow if the task deadline is not met.
• The number of email reminders and the interval to send them before the task deadline.

You can display the Precondition tab in three ways:

• Click on the step of the workflow, then click the Edit Step Properties icon then click on the Escalation tab.
• Click anywhere in the Escalation section in the Properties Navigator. This takes you directly to the Escalation tab.
• Click the inside the Precondition section in the Properties Navigator. This takes you directly to the Escalation tab.
• When you click on the Escalation tab, a short explanation of existing Escalations displays. Click the arrow to edit or review. Click the ADD ESCALATION button to add one.
• Click the Delete icon to remove an escalation.
• Remember to click Submit to save your changes.

Setup Escalations

Configuring Escalations

To start, click on the step in your workflow where you want to configure the Escalation feature and select the Escalations tab. Then click ADD ESCALATION to display the Escalation Condition tab. 

Escalation Conditions

Select a condition from the dropdown. There are 4 choices:

1. Perform By - This condition is met when the user clicks the  (if the task is assigned to a particular user) or ( if the task is assigned to a role) Perform icon on the task in the users Task List or Saves/Locks the task before the configured due date. If the Task Notification email includes the {task.perform.url} then the deadline is met when the user clicks the link in the email to display the task. 

2. Perform Within - This condition is met when the user clicks the (if the task is assigned to a particular user) or ( if the task is assigned to a role) Perform icon on the task in the users Task List or Saves/Locks the task before the configured the configured duration). If the Task Notification email includes the {task.perform.url} then the deadline Undo is met when the user clicks the link in the email to display the task.
   
3. Complete By - This condition is met when the user clicks the Continue/Finish button on a step in a workflow before the configured due date.

4. Complete Within - This condition is met when the user clicks the Continue/Finish button on a step in a workflow before the configured duration.

Selecting Perform By or Complete By displays two options.

• Using Date/Time Control: The Due Date control dropdown displays all date controls in your form. 

  An invalid due date template value will resolve to the current time to prevent any use-mode errors. The following message will appear in the frevvo logfile: "Escalation Due Date {DueDate} resolves to an invalid value".
  

• Use Fixed Date: Enter a date/time as the deadline.

Selecting Perform Within or Complete Within displays Days, Hours and Minutes and a Business Calendar checkbox.

1. Specify the amount of time the user has to perform or complete the task in Days, Hours or Minutes.
2. Check the Business Calendar checkbox if you want to use the business days, times and timezone specified for your tenant to calculate a task deadline. The business calendar is set up at the tenant level by the tenant admin.

Escalation Actions

Once the condition is selected, click the Action tab to continue. Select from the following choices:

1. None (Notify only) - Check this option if you want to send reminder emails to the user(s) who currently have the task on their Task List that the deadline is approaching and then send an email notification to them when the deadline is reached. The Notification tab becomes required. The task will not be reassigned or skipped. 
2. Reassign Task - Reassignment sends the task to the user/role selected if the deadline is passed. Select whether the task will be reassigned to a Role, User or Unlock to Role: 
   
   
   1. If you select Role or User, then you must select the user or role in Select Role or User Assignee(s) field. Type ahead to display the Roles/Users in your tenant that begin with the letter you are typing and select from the list or enter comma separated templates. Remember that  userids and roles are case sensitive. If reassigning to a specific user, only one user id can be selected but you can reassign to more than one role.
   2. Unlock to Role - This option unlocks the task. Use this option for a step in your workflow that has a role assigned to it and you want to handle the situation where one user with that role has the task locked and the deadline for the task has passed. Selecting Unlock to Role unlocks the task and keeps it on the Task list of all users with the role after the deadline expires. Now it can be performed by any user with the specified role again.
      For example, let's say you have a step in your workflow that is assigned the manager role. Users Jerry and Jim are managers so the task shows up on both their task lists. Jerry clicks the Perform icon but he does not complete the step. The task remains on his task list and it is locked by him. If Jim tries to access the task or checks the Audit Trail he will see that the task is locked by Jerry. The deadline to complete the task passes. If Unlock to Role is selected as the reassignment option, the task remains on the task list of users with the manager role, in this case, Jerry and Jim, but it is unlocked and the audit trail shows a status of pending. Now it can be performed by any user with the manager role again.
      
   3. Reassigned users receive the Task Information email specified by the designer. So be sure to 1063730798 for the step in your workflow where you assigned escalations and you want to reassign the task after the deadline.

3. Skip Task - check this option if you want the workflow to escalate automatically to the next step when the timer expires. When checked, no further configuration is required.

   Skipping a task is only supported if the next step in the workflow is a form/summary step. Configuring the Skip a task feature on the last step of your workflow will not work. 

Escalation Notifications

You can set up notifications for any of the three actions. 

1. Click on the Notifications tab.
2. Slide the toggle icon to the right to turn on Notifications
3. Select Role, User or the Current Owners from the Send To dropdown to specify who will receive email notification reminders when the deadline is reached.
   1. If you select Role or User, then you must list them in the Select User(s) or Role Recipient(s) field. Type ahead to display the Roles/Users in your tenant that begin with the letter you are typing and select from the list or enter comma separated templates. Remember that  userids and roles are case sensitive. You can specify more than one user or role.
      

      1. Current Owners refers to user(s) who currently have the task on their task list. Partial templates with prefixes and suffixes can be used to create a complex role such as floor-manager when setting up Escalations.

          Click here for an example

          When you are setting up step Assignments or Escalations for workflows, you can assign a user/role template where only part of the text is inside the curly brackets - {}. This is best explained with a simple example using roles for workflow routing.

         Let's say the roles in your organization are floor-manager, sales-manager and store-manager. Of course, these role names and users assigned these roles must exist in your tenant. Your form has a dropdown control named roles with these options: floor, sales, store. Users select the first part of the role from the dropdown. The suffix -manager is typed in after the role template in the Assignment tab to create the complex template - (floor-manager, sales-manager, store-manager). The workflow step with the complex template assigned will navigate to the appropriate role.

         A partial match template lookup is available on the Assignment and Escalations tabs to select the complex template from dropdown options.

         We will assign the {role}-manager on the Assignment tab of a workflow as an example:
         

         1. Type the control name of the template surrounded by curly brackets - in our example - {role}

             

         2. Type the dash - followed by manager. The {role}-manager appears in the dropdown

         3. Click on it to select. Click Finish to save the changes to the Assignment tab then click the save and exit to save the changes to the flow.

         4. Test the flow. Select floor in the role dropdown. The assigned workflow step will navigate to all the users in your tenant with the role of floor-manager.

         

         The partial lookup works with users/roles and prefixes/suffixes in the users/role names.

   2. Specify an email(s), user(s), or role(s) to receive a CC: of the notification (optional).
   3. The subject and body of the notification email are shown once the Recipient(s) are selected. You can customize the email message by adding controls from your form as templates, workflow templates, common templates, escalation or task templates. Simply click the to show the templates or type ahead to filter the list. For example, when a task is reassigned, you may want to specify the user/role that the task is being reassigned to (reassignee) in the email to avoid confusion. Simply add some text with this template in the Notification message section:  {flow.step.escalation.reassignee}.
      

Escalation Reminders

Configure email reminders on the Reminders tab. Reminder emails notify the roles/user(s) originally assigned to this step.

1. Specify the interval between reminders by entering the number of reminders in the Every field and select Days, Hours or Minutes from the Unit dropdown.
2. You can limit the number of reminders by sliding the toggle icon to the right and entering the number of reminders closer to the deadline in the Occurrence(s) field. If you enter a negative number in this field by mistake,  will change it to a 1 when you exit the field.
3. Specify an email(s), user(s), or role(s) to receive a CC: of the notification (optional.)
4. You can customize the email message by adding controls from your form as templates, workflow templates, common templates, escalation or task templates. Simply click the to show the templates or type ahead to filter the list. Select them from the Control dropdown.

Escalations and Screenflows

Escalation should always be defined on the first step of a task - this is relevant when setting up Escalations for a Screenflow.

Screenflows are steps in a workflow that are performed by the same user. Consider a New Employee On-boarding workflow where steps 1 - 5 are designed to collect the Personal Information, W - 4 Allowances, State Allowances, Health Insurances preferences and Banking Information. Step 6 in the flow is routed to the new employee's manager and step 7 is routed to HR for final processing. Steps 6 and 7 are not part of the screenflow as they are performed by users other than the new employee.

Think of the 5 steps of the screenflow as one task. Escalation for the screenflow task will work as long as you define the escalation on the first step of the screenflow task. The escalation configured on the first step of the screenflow applies to all steps of the screenflow. For example, if a Complete Within 2 days escalation is configured on Step 1 of screenflow, then the escalation is triggered if the whole screenflow is not completed within 2 days.

If the first steps of a workflow consist of a screen flow, you must configure the flow to use the Save on Navigate and/or Task for First Step properties for escalation triggers to get created

Escalation Examples

 Click here to see some Escalation Examples

Escalation Example 1

Let's consider a Time Sheet workflow consisting of 3 steps: 

• The employee accesses the Time Sheet workflow, fills in the form, signs it and clicks Continue. Live Forms sends that employee's manager a notification via email
• The manager clicks on the notification [on any device], views the Time Sheet approval request and approves it or sends it back for corrections.
• If approved by the manager, the workflow is routed to employees in the payroll department for final processing. 
  
  

In this example, the designer has configured a 10 minute interval for the Manager to approve/reject the task. The Escalation tabs are shown

Employee William submits his Time Sheet at 12:55 PM. The deadline to complete this task is 1:05 PM. William's Manager Jerry receives a Task Notification email notifying him there is a task that requires his attention. The email includes a link he can use to access it.

In this example, the deadline to complete the task is 1:05 PM. Based on the setup of the Reminder(s) section shown above, Jerry will receive 3 reminders every 3 minutes as the deadline approaches. The emails contain a link that Jerry can click to get to the task. The first one arrives as 12:56 PM, the second at 12:59 PM and the final reminder before the deadline arrives at 1:02 PM.

At 1: 05 PM, the task is removed from Jerry's task list since it was not completed in the allotted time and is routed to the task list of any users with the role of Supervisor. Jerry receives an email informing him that the deadline for the task has expired and the task is now assigned to any user with the role of Supervisor.

Reassigned users receive the Task Information email specified by the designer. So be sure to Setup the Task Notification Emails.

When Jack, a user with the role of Supervisor, access his task list he will see a task sent to him by the system and the Audit Trail shown in the image:

Escalation Example 2

Let's consider a situation where you might want to skip the task after the deadline has been reached. Imagine a workflow with a requirement that it must be approved by specific users in sequence. To prevent the chain of approvals from being delayed if one user does not perform their approval before the deadline, the designer can check the Skip the Task checkbox on the flow steps and  will automatically complete the current step and create a pending task on the Task List of the next user.

The Project Approval workflow shown in the image must be approved by Approver 1 and Approver 2 in that order. The escalation set up on the Approver 2 step automatically skips this step and advances the flow to the next next step . Notice that notification and reminder emails are also configured.

In this example,

• The Approver 1 and Supervisor steps do not have Escalation configured.
• The Approver 2 step has an escalation that specifies the step must be completed within 3 minutes. 
  
• If Approver 2 does not complete the task within 3 minutes, the Approver 2 step is skipped and the flow advances to the Supervisor step.
• Approver 2 receives an Notification email stating that the flow is now assigned to a Supervisor.
  
• Approver 2  receives 1 Reminder email during the 3 minutes interval. 
  

Here's what happens:   

1. Project Details are submitted for approval. 
2. Approver 1 receives a Task Notification email, clicks the link in it and performs step 1 of the workflow. The task is placed on Approver 2's task list.
3. Approver 2 receives a Task Notification email which includes a link to the task. Approver 2 does not click the link in the email to perform the task.
   
4. Approver 2 receives 1 reminder email. Approver 2 does not perform their approval within the 3 minutes.
5. When the 3 minutes expires, the task is removed from Approver 2's Task List.  Approver 2 receives a customized email stating that the flow has moved to a Supervisor for approval.
6. All users with the role of Supervisor receives a Task Notification email which includes a link to the task. 
7. Someone in the Supervisor group approves/rejects the task.

Activity Document Actions

What do you do with the data you collect from your workflow? offers the ability to configure a Document Actions to send a final email, post data to a web service/back end system, update a Google Spreadsheet  or save submissions to ImageSilo/Papervision, Google Drive, your Filesystem, Box or SharePoint using one of the frevvo Connectors . The Document Actions execute when the workflow is completed.

What if you want to perform some action after a workflow step is completed, instead of having to wait for the flow to finish? You can configure an email to a specified address or to post to a web application or both for any step in the flow. For example. Each step of your flow could post to a web application that will audit flow steps or you might want to send a customized email to a specified address after one of the steps instead of waiting for the entire flow to be completed. The designer can configure an Email or a post to a web application for the steps in your flow, as well as, Document Actions that will execute when the flow is completed.

Actions configured on the Email and Web Hook tabs execute when the user clicks the Continue button for each step. It does not matter if the next step is performed by the same user or if the step is put on the task list of a new role/user.

If you are saving back to your own task list, by clicking Save on the flow step instead of Continue, saving to role or saving to a different user, in a flow, these actions do not execute.

Email

Use the Email tab to send a custom email with attachments (if required) to a specified address. The email will be sent when the workflow step completes.

You can display the Email tab in three ways:

• Click on the step of the workflow, then click the Edit Step Properties icon then click on the Email tab.
• Click anywhere in the Email section in the Properties Navigator. This takes you directly to the Email tab.
• Click the inside the Email section in the Properties Navigator. This takes you directly to the Email tab.
• Slide the toggle to the right to turn on the Email feature.
• Enter email addresses or click the down arrow to select control and built-in form/flow templates to dynamically determine it at runtime.
• Customize the Subject and Message of the email.
• Select the type of attachments to include in the email.
• Remember to click Submit to save your changes.

Configuring Email

You can configure the Email tab on as many steps of your workflow. Remember the Document Actions that are set up will execute when the flow is completed, so you may not need to configure an action for the last step.

Specify the To: email address and the optional Cc: and Bcc addresses. You can enter multiple addresses separated by commas or semicolons in the To, Cc, Bcc fields and a single Reply To address.Templates can be used to provide the email addresses if desired. The "To:" email address is required. All other properties are optional. The tenant admin can configure the from email address on the tenant admin's Edit Tenant page. If you want an email to show a different From:address than what is configured on the Edit Tenant page, enter that address in the From: field. You can enter a static address or use templates to make the the address dynamic. The From address replaces the default no-reply@…, an address configured on the Edit Tenant screen .

Select which documents are included in the email.

• You have the option of sending a filled form image using the Send Snapshot dropdown. Select the image type from the dropdown. Leave the option blank if you do not want to send a snapshot.
• The Data checkbox adds an XML document of your flow.
• Check Attachments to include files uploaded to your form/flow. Uncheck it to exclude attachments in the submission.

• If you have Pixel Perfect mapped PDFs (ex: W-4, I-9 etc…) associated with your forms/flows, choose  the action you want to take by checking an option in the Send Generated PDF Forms field:

  • Check All to send all the Pixel Perfect PDFs in the submission. This is the default value.
  • Check None to send none of the PDFs.
  • Check Select to display a list of all the PDFs associated with your form/flow. Click the ones you want to be part of the submission from the popup.
    
    

Customize the subject and message of the email in the Subject and Message fields on the tab.

Email Example

Web Hook

Use the Web Hook tab to post the data from your flow to a web application. Your data will post to the web application specified by the URL when the user clicks the Continue button on the workflow step.

For example. Each step of your flow could post to a web application that you created to audit flow steps. At this time, Web Hook cannot be used to kick off another workflow (please see this documentation for another option.)

You can display the Web Hook tab by:

• Clicking on the step of the workflow, then click the Edit Step Properties icon then click on the Web Hook tab.
• You will not see a section for this tab in the Properties Navigator.
• Slide the toggle to the right to turn on the Post to Web Hook feature.
• Click the down arrow to select control and built-in form/flow templates in the URL.
• Select the type of attachments, if any.
• Remember to click Submit to save your changes.

Configuring the Web Hook

• Type the URL to your web application in the URL field. Templates can be used. Click the down arrow in the URL field to select control and built-in form/flow templates in the URL to your Web Application. When the form is submitted,  POSTs the document set to the specified URL. This option may be used for additional processing of data.
• You have the option of also sending a filled form image using the Send Snapshot dropdown. Select the image type from the dropdown. Leave the option blank if you do not want to send a snapshot of the flow
• The Data checkbox sends the flow XML document.
• Attachments uploaded to your form/flow are sent if the Attachments checkbox is checked.

• If you have Pixel Perfect mapped PDFs (ex: W-4, I-9 etc…) associated with your forms/flows, choose  the action you want to take from the Send Generated PDF Forms control:

  • Check All to send all the Pixel Perfect PDFs in the submission. This is the default value.
  • Check None to send none of the PDFs.
  • Check Select to display a list of all the PDFs associated with your form/flow. Click the ones you want to be part of the submission from the popup.

Activity Document Action Failure Notification

https://<your server>/services/testhttp?status={t}&content=errortext

Quick Approval

Use the Quick Approval tab to configure the Quick Approval feature on workflow steps. Quick Approval provides the ability for a user to see a simple view of a task in order to Approve or Reject it. A comment and/or signature can be added to the task without viewing the entire form. Quick View makes the process of task review/approval/rejection easy especially on mobile devices.

You can display the Quick Approval tab by:

• Clicking on the step of the workflow, then click the Edit Step Properties icon then click on the Quick Approval tab.
• You will not see a section for this tab in the Properties Navigator.

Approval Control

Your workflow step MUST have an Approval Control to successfully configure the Quick Approval feature.

Approval controls are sections in your form that contain a textarea control. The Approval control section can NOT contain any other controls in addition to the text area. The section can be named anything.  It cannot be nested in a repeat or a signed section.  

Follow these steps to create an Approval control:

1. Drag/drop a Section control into the step of the workflow where you want to configure the Quick Approval feature. Name the section whatever you want.
2. Drop a Textarea control inside the section. Do NOT add any other controls to the section.

The Approval control can be optionally set up to be digitally signed. Regular text digital signatures and Wet Signatures are supported. See Electronic Signatures for more information. The image below shows a section named Manager Review with a textarea control for comments. Text/Signature image is selected on the Signature dropdown on the section security tab. This section meets the requirements for an Approval control that can also be digitally signed.

 

Quick Approval will be disabled if the approval control is removed from the workflow step or additional controls are added to the Approval Control section.

If the flow step does not contain an Approval Control, you will see this warning message when you display the Quick Approval tab.

Setup Quick Approval

Once you have added Approval Controls to the workflow steps where you want to configure Quick Approval, select the Quick Approval tab.

• Slide the toggle to the right to turn on the Quick Approval feature.
• Set up Task Information for the Quick Approval view in the Summary field. Click the down arrow to include control and built-in form/flow templates in the Task List Summary. The Quick View icon  will appear on the Quick Approval view on the Task List if the step in your flow has been setup for it. This feature is helpful if your users will be approving/rejecting steps of a workflow from a mobile device.
• Select the Quick Approval control from the dropdown.
• Remember to click Submit to save your changes.
• Repeat for all steps where you want to configure Quick Approval.

There is a visual cue, a lightning icon, , that displays on a workflow step if quick approval is enabled.

Quick Approval Example

An example of an Employee On Boarding workflow with Quick Approval configured on the Manager Approval step is provided.

Geo Location

Use the Geo Location tab to:

• Capture location information for a step in your workflow.
• Embed a Google map in your flow step.

You can display the Geo Location tab by:

• Clicking on the step of the workflow, then click the Edit Step Properties icon then click on the Geo Location tab.
• You will not see a section for this tab in the Properties Navigator.
• Enable the Geo Location feature for the step.
• Enable the ability to capture additional location information or embed a Google map in the flow step
• Do this for each step in your flow where you want to use the Geo Location feature.
• Remember to click Submit to save your changes.
  

You can capture the location where your form/flow was filled in by turning on ' Geo location feature. A form/flow knows it's current location and will submit that information when the form is completed.   uses the HTML5 GeoLocation api.  The geo api is well supported on tablet, phone and recent laptop/desktop browser versions. This feature works on a desktop or any GPS capable mobile device.

When the form/flow loads in the browser, it will ask for the location. All browsers will show a pop up asking the user's permission to use their location, unless permission was Always granted or refused in a previous session. The user must give permission for Geo Location to proceed. Here is an example of the request in the Firefox browser:

The Geo Location feature works in conjunction with rules that use the form.positionUpdated identifier. You can set up the rule to execute every time the position is updated. See Business Rules for examples of rules that will do this. Also see Rules Position Data for the complete list of available build-in data.

You can also collect additional information associated with your location. For example, a section of a Police Incident Report, shown in the image, captures the location where the form/flow was filled in plus the address information associated with it. The last position update will be in the submission metadata of your form or flow but it is NOT automatically added to the XML document .  You must create controls (perhaps hidden) and rules to add the location information to the form XML document. The Position Address section of the Police Incident Report has controls and rules to show longitude, latitude, accuracy and/or errors plus the address information.

Latitude and Longitude display the coordinates of the user location. The accuracy of the location in meters is represented by the value in the Accuracy field - a low Accuracy value means the position is more precise. You can display a position error code and the text description of an error message in your form/flow if desired. Error message codes can be 1, 2 or 3:

1 - Permission Denied - You will get this error code if the user says no to the access question.

2 - Position Unavailable - This error code means the device running the browser cannot get the GPS satellite signal (tunnel, underground).

3 - Timeout - The device running the browser times out trying to get the location information.

You will never see coordinates and error codes in the same form. You get one or the other.

Configuring Geo Location

• Select one of three options from the Geo Location dropdown to turn this feature on:
  • None - (no location) - this is the default
  • On Load - turn the feature on when the flow step loads (at start time)
  • Custom - allows the designer to specify a periodic refresh. The default value is 30 seconds. Choosing this method will fire a rule in the specified time. For example, if the field to the right of the Geo Location dropdown was set to 10, rules to capture additional location information would fire every 10 seconds. 
    
• Enter the Location Refresh Timeout - this is the amount of time in seconds the location finder in the browser will search to find the location before it times out. The default value is 5 seconds.

• Check the Detailed Location checkbox to capture additional information based on the location via a Business Rule or to embed a Google map in your form. You will need a connection to google.com for this to work.

  • A connection to google.com is required for this to work. This connection is automatically available in the frevvo Cloud.
  • New in-house installations must obtain an API key in order to use this feature. Follow the steps listed here to obtain the key.

Displaying a Google Map in your Workflow Step

•  Add a Message Control where you want the map to display in your flow step. Type f-map-div in the css class field on the Message Control Properties panel. This is a built in java script that cannot be edited to display the map.

The map will only display at runtime. You will not see it in the Flow Designer.