Section

Column

Approval workflows are everyday actions that businesses perform on a routine basis. This tutorial will show how easy it is to create an Approval Workflow using . We will start with a simple workflow and add to it for each example discussed to demonstrate some design patterns and different features. The final workflow will be an example of a services Purchase Order workflow. We will create:

A screenflow - allows you to collect a lot of information in a series of small steps
A workflow where one of the steps is performed by someone outside the company (anonymous)
An Approval workflow where one of the steps is only routed for additional approvals if certain conditions are met.

If you need basic help using the Flow designer, please refer to the Getting Started with Flows guide, and then return here.

What are we going to build?

Many companies offer software services to their new and existing clients. The final workflow in this tutorial will be a Purchase Order workflow for services that follows this business scenario:

A sales person accesses the company's Purchase Order form, fills in the customer's email address and other required information, signs it and clicks Continue.
sends a customized email to the customer that contains a link to the PO.
The customer clicks on the link, reviews the Purchase Order, approves and signs it or sends it back to the company for corrections
The workflow is routed back to the sales person.
The sales person reviews the PO, and sends it to his manager for approval. The manager receives an email.
The manager clicks on the link in the notification email, logs onto to review the PO via the Task List. He approves or sends it back to the sales person for corrections.
If approved by the manager and the total amount of the PO is greater than $10,000.00, the workflow is routed to the VP for final approval.

Column

width	375px

On This Page:

Table of Contents

maxLevel	1

...

Click the Edit icon for the Purchase Order application.
Click the Flows tab to open the Flows home page.
Click the New icon to create a new flow. Click on the toolbar to display the flow properties panel. Type "Example 1 - PO Screenflow" in the Flow Name field.
If the Palette is contracted, click in the header to expand it. Drag the Client form from the Palette and drop it on the flow designer canvas into the Guide box. This form will be the first step in the flow.
Drag the Services form from the palette and drop it below the Client form when you see the "green flashing bulls eye". The Services form will be the second step in the screenflow.
Click on the what does the user see icon in the tool bar to customize the message the sales person will see when the flow is completed:
1. Click on the Display Message wizard. Copy the message below into the Message box then click Finish. {ClientName} and {ClientCompany} are examples of templates. Templates are specified by surrounding the name of a control in your form with curly braces. will use the values entered into the Client Name and Client Company fields at runtime.
  Code Block
  The Purchase Order for {ClientName} at {ClientCompany} is complete.
2. Click Finish.
At this point, your workflow should look like this:

Click the save/exit icon to save your work.

Info
If you want to see the details of the forms, click on a step in the flow designer then click the Image Removed Image AddedEdit icon on that step. The form will display in the forms designer. You can view the business rules by clicking on the Rules icon.

...

Click the Edit icon for the Purchase Order application.
Click the Flows tab to open the Flows Home Page.
Click the New icon to create a new workflow. Click on the toolbar to display the workflow Properties panel. Type Example 2 - Send the PO for Signature in the Flow Name property on the left.
Drag the PO form from the Palette and drop it into the Guide box on the flow designer canvas. The PO form will be the first step in the workflow.
1. Click on the PO step. Click theEdit Step Properties icon. Click on the General Settings tab. Make sure the printable property is checked on this step. We are creating our flow using the linked steps design pattern. Checking the printable property on the original form guarantees that the original form and any linked steps in the flow are included in the pdf.
2. Type "Send to client" in the Continue Label property. Click Submit.
Click the Link icon to create a copy of this step. A linked copy of the PO form (double box), is added to the flow.
Click on the linked PO step:
1. Change the name to "Client Approval" in the Name field by clicking the General Settings in the the Properties panel.
2. Type "Send to frevvo, Inc" into the Continue label property to change the text to something more meaningful.
3. Click the Rejection tab, uncheck the Reject to here and Reject from here checkboxes. The Reject button feature will be discussed in a later example.
We will now set up the anonymous user step:
1. Click on the Assignment section of the Properties panel. Enter the template {ClientEmail} into the Assign to Email property. ClientEmail is the field in Step 1 where the sales person enters the email address of the customer. sends the PO to the email address entered in that field. This is an example of a template. Note the control name is encased in curly braces.
2. Below the Task Notification Email instruction on the same tab, type the subject for the email - "Purchase Order from frevvo". Copy the text below into the message field to replace the existing message. This is the email the customer receives.
 Code Block
 {ClientName}, Please review and sign this Purchase Order from frevvo Inc. by clicking on <a href="{task.perform.url}">this link</a>. Thank You.
3. Click on the Messages tab, enter "Purchase Order Sent to {ClientEmail} for Signature" in the Pending Message property. This will be the message that the sales person sees after they click the Send to client button.
Click Submit

We will use the Visual Rule Builder to add a business rule to the PO. This rule hides the Instruction section on the Client Approval step. The Instructions should only show on the steps performed by company employees logged into . It will also show the Agreement (Client Approval) section on the Client Approval and subsequent workflow steps and hide it on the first step. We want the Agreement section to display on the Client Approval step of the workflow where the Client Approves or Rejects the PO. If the Client approves the PO, then the business rule will make the Client Signature field required.

Expand

title	Click here to see how to create this rule

The Visual Rule Builder consists of 3 wizards:

Condition wizard - describe the conditions under which a set of actions should be executed
Action wizard - declare the actions that should be taken when the condition is true
Else Action wizard - declare the actions that should be taken when the condition is false

Click the PO step then click the Image Removed Image Addedblue pencil icon to edit it
Click the Rule icon on the Flow Designer toolbar
Click the to add the rule.
Name it Show/Hide Client Approval/Instruction Sections, make Client Signature Required if Approved
Click the Rule Builder button then click Add Condition - this is the Condition wizard
Select current step from the first dropdown.
Select is on or after from the second dropdown
Select Client Approval from the third dropdown
Click Next then click Add Action - this is the Action wizard where you set up actions that will happen if the condition is true
Set the Agreement section to visible
Add another action to set the Instructions section to hidden
Add another action to set the Client Signature field to required
Click Next then click Add Action - this is the else action wizard where you set up actions that will happen if the condition is false
Set the Agreement section to hidden
Add another action to set the Instructions section to visible
Add another action to set the Client Signature field to optional
Click Finish

The Rule should look like this on the Rule Editor page:

Click the Image Removed Image Addedsave and exit icon to save your work. Click the Cancel icon to return the the Flow Designer canvas.
In this example, the workflow will end after the client approves. The sales person receives an email with a copy of the flow pdf attached. Follow these steps to configure this email:
1. Click the what happens to my data icon on the toolbar.
2. Click on the Email data to a specified address wizard.
 1. Enter {SalesEmail} and {ClientEmail} in the To: field. Separate them with a comma. Ex: {SalesEmail},{ClientEmail}
 2. Select PDF from the Send Snapshot dropdown. This adds a pdf to the email after the customer approves it or requests corrections.
 3. Uncheck the Send Data checkbox. Check the Files checkbox. These selections ensure the flow xml will not be attached to the email but any attachments that are uploaded will.
 4. Click Next
 5. Enter "Purchase Order for {ClientName} at {ClientCompany}" in the subject field.
 6. Copy the text below into the message field to replace the existing message.
 Code Block
 The Purchase Order from {ClientName} at {ClientCompany} is attached. Please review. Thank You.
 7. Click the Finish button.
Customize the message the client will see when they click the Send to frevvo, Inc button.
1. Click on the what happens to my data icon in the tool bar.
2. Click on the Display Message wizard. Enter "The Purchase Order for {ClientName} at {ClientCompany} was sent to frevvo, Inc.".
3. Click Finish.
Change the visibility of the workflow to public so the customer (anonymous user) can access it. To do this:
1. Click thelock icon on the toolbar. This will pop up a window where the designer can specify permissions.
2. Change the Visibility to “Anyone (login not required)” for the Permission “Who can start the flow”.
3. Click Finish.
At this point, your workflow should look like this:
Click the save and exit icon to save your work.

...

Click the save/exit icon then the Test icon. Click the the blue blue right arrow to expand the Instructions section. This section is only visible to internal employees of the company.
Fill in the first step of the PO and sign.
Click the Send to client button. You will see your customized pending message.
Log out of
sends a notification email with your customized subject/message to the email address specified in the Primary Contact Email Address field on the first step.
Open the customer's email with a "Purchase Order from frevvo" subject. Click on the link provided.
The customer will see the completed PO and a section where they can sign to approve the PO or send it back if corrections are needed. In this example, the Reject button does not show as it is not configured for this workflow step
Approve the PO for now. We will cover rejecting the PO in a later section. Sign as the customer. Verify the Date Signed field is populated with the current date after signing.
Click the Send to frevvo, Inc button. You will see your customized message.
The sales person and the client receive an email "Purchase Order for {ClientName} at {ClientCompany}" as the subject.
Open one of the emails and click on the pdf. Verify the Sales Information, Client Information, Client Services details and the Agreement section with the customer's signature are included.

...

Login to your tenant as the designer user.
Edit the Purchase Order application.
Click the Edit icon for the workflow you want to modify. Change the name to Purchase Order Workflow.
Set up the fields from the flow to use as task and submission search criteria. For example, if we define the control named ClientCompany as a searchable field then we can search for Purchase Orders that were submitted by a particular company.
1. Click the Setup Searchable/Summary fields link on the Flow Properties panel.
2. Minimally, move the Client Company, Client Name and Total Amount fields from the Available Fields column to the Searchable Fields column. Add/remove any other fields that you want to define as Searchable Fields.
3. Click Finish.
  
  Image Modified .
Add the Sales Review step:

Click on the PO form, and then click the Link icon.
A linked copy of the PO form, a double box, will be added to the flow. Drag this step below the Client Approval step. Drop it when you see the "green flashing bulls eye".
Click on the linked PO step, then click theEdit Step Properties icon. Change the name to "Sales Review" in the Name field by clicking in General Settings on the Properties panel.
Click on the Assignment Tab. Type {SalesID} in the Assign to User property on the panel.
To customize the task notification email the sales person receives:
1. Below the Task Notification Email instruction message type "Review PO from {ClientName}" in the subject field. You can select the control name from the dropdown to the left of the subject field.
2. Leave the default message.
Click on the Message tab. Type "Thank you! Your PO has been sent back to frevvo Inc." in the Pending Message property. This is the message the client will see when they click the Send to frevvo, Inc button on the previous step.
Type Client: {ClientCompany} in the Task Information property. The Task Information helps the sales person identify the task on the Task List.
Click Submit

Click on the what does the user see icon in the tool bar. Click on the Display Message wizard. Change the email message back to
Code Block
The Purchase Order for {ClientName} at {ClientCompany} is complete.
At this point, your workflow should look like this:
Click the save/exit icon to save your changes.

...

Login to your tenant as the designer user.
Edit the Purchase Order application.
Click the Flows tab.
Find the Purchase Order Workflow in the list.
Click the Deploy icon to remove the development watermark and deploy your workflow to production.
Click the Spaces link at left. Click the Image ModifiedNew icon.
Enter a Space Id i.e.workflowtutorial and a Space Name i.e. Workflow Tutorial Space and click Create.
Click the Image ModifiedShare icon. Copy the share URL for your space. Bookmark it in a different tab of your browser. Save the URL. You will need it for the Task Notification email messages in Example 4.
Logout

Example 4 - PO for Manager Approval

...

Roles can only be created by the tenant administrator. The steps are:

Login to as the tenant admin.
Click the Manage Roles link.
Click the the plus iconplus icon.
Type "VP" into the role name and click Submit

...

Test Example 6:

Follow these steps to test Example 6:

Click the link to your space that you bookmarked earlier. Login as the designer.
Select the Purchase Order from the Purchase Order tab.
Fill in the PO with a Total Amount value that is equal to or greater than $10,000.00. Sign as the sales person. Click the Send to client button.
Log out of your space.
Check the email account for the customer. Access the email with the subject "Purchase Order from frevvo", click the link provided.
Approve and sign the PO as the customer.
Click the Send to frevvo, Inc button.
Log into your space as the designer@<your tenant>. Select Task List from the Important Items tab.
Click the Perform icon. Review the PO then click Send to Manager. Logout of your space.
Login to your space as jerry@<your tenant>. Select Task List from the Important Items tab.
Click the Perform icon. Add a comment and sign as the manager. Click Finish or Send to VP. Logout of your space.
Login to your space as ed@<your tenant. Select Task List from the Important Items tab
Click the Perform icon. Add a comment and sign as the VP. Click Finish. Logout of your space.
The sales person (designer) and the customer will receive an email with the signed PO. Check the pdf to make sure the VP approval is included.
Run the workflow again with a Total Amount that is less than $10000.00. The workflow is finished after the Manager Approval step.The sales person and client receive an email with the signed pdf.

Example 7 - PO Reject

What happens if the manager or VP need more information or corrections made to the PO before approving? They can send the PO back to an earlier step by clicking the reject button. 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 designer configures which steps display a Reject button via the Setup Approval/Rejection wizard. Simply check/uncheck the Reject to here or Reject from here checkboxes for each step in the workflow. The reject button label can also be modified on any step.

You can one to a step performed by an anonymous user (our Client Approval step). For example, clicking the Reject button on this step allows the customer to send the PO back to the sales person (designer) for corrections. Once the corrections are made, the flow is sent back to the customer for another review and the flow continues to completion if the customer approves.

Modify the workflow:

Log into your tenant as the designer user. Edit the Purchase Order Application, click the Flows tab then edit the Purchase Order Workflow. You can change the button label on any step where Reject from here is checked.

Click the PO step then click on the Rejection section in the left Properties panel.
1. Check "Reject to here" and uncheck "Reject form here". Since this is the first step in the flow, there are no steps before it to reject to. If you leave it checked, it will be ignored.
2. Click Submit.
Click the Client Approval step. Click on the Rejection section in the left Properties panel.
1. Check Reject to here and Reject from here.
2. Change the Reject Button Label to "Send PO back for revision".
3. Click Submit.
Click the Sales Review step then click on the Rejection section in the left Properties panel.
1. Check Reject from here and Reject to here.
2. Click Submit.

Click the Manager Approval step then click on the Rejection section in the left Properties Panel.

Verify that Reject from here and Reject to here are checked. The manager can reject the flow back to the sales person and the VP can reject the flow back to the manager step.
Change the Reject Button Label to "Reject PO".

Replace the {task.perform.url} template in the Rejection email body to the URL of your space with /tasklist appended to it. Here is an example.

Code Block

language	xml
title	Reject Email 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 your task by clicking <a href="https://app.frevvo.com:443/frevvo/web/tn/mycompany/u/85a7dee1-e4cc-4c31-bcc6-d6929fb4d2b2/space/workflowtutorial/tasklist">this link</a></p>

Click Submit

Click the VP Approval step then click on the Rejection section in the left Properties Panel.

Check Reject from here and uncheck Reject to here. Since this is the last step in the flow, there are no steps after it that can reject back to it. If you leave it checked, it will be ignored.
Change the Reject Button Label to "Reject PO".

Replace the {task.perform.url} template in the Rejection email body to the URL of your space with /tasklist appended to it. Here is an example.

Code Block

language	xml
title	Reject Email 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 your task by clicking <a href="https://app.frevvo.com:443/frevvo/web/tn/mycompany/u/85a7dee1-e4cc-4c31-bcc6-d6929fb4d2b2/space/workflowtutorial/tasklist">this link</a></p>

Click Submit.

Click the save/exit icon to save your changes to the workflow.
Logout of your tenant.

Test Example 7:

Click the link to your space that you bookmarked earlier. Login as the designer user.
Select the Purchase Order from the Purchase Order tab.
Fill in the PO with a Total Amount value that is equal to or greater than $10,000.00. There is no Reject button on this step. Sign as the sales person. Click the Send to client button.
Log out of your space.
Check the email account for the customer. Access the email with the subject "Purchase Order from frevvo", click the link provided.
Notice the reject button with the label Send PO back for revision. Click on this button.
Click the down arrow for the To dropdown on the Rejection screen. Select the step in the flow to send the flow back to - in our case - PO - (designer) who is the sales person.
Provide an explanation for rejecting the PO in the Reason box. Click Submit.
The message "Task successfully rejected" displays.
Check the email for the sales person (designer user). Notice the email with the title "You have a new task for Purchase Order Workflow". This is the Rejection email.
Open this email. The step of the flow where the rejection was performed and the reason for the rejection is shown in the body of the email. Click the link to the flow embedded in the rejection email. The rejection email subject and body can be customized to reflect whatever you want to say.
Log into your space as the sales person (designer user). The Sales Person's (designer user) Task List displays. Click the Perform icon, review the PO, make a change, sign then click Send to client. Logout.
Check the email account for the customer. Access the email with the subject "Purchase Order from frevvo", click the link provided.
Approve the corrected PO, sign and click the Send to frevvo, Inc button.
Login to your space as the sales person (designer user). Select Task List from the Important Items tab. Click the Perform icon. Review the PO. Click Send to Manager. Logout.
Login to your space as jerry@<your tenant>. Select Task List from the Important Items tab. Click the the Perform icon. Notice the Reject PO button on this step.
Approve the PO as the manager, sign then click Finish or Send to VP. Logout.
Login to your space as ed@<your tenant>. Select Task List from the Important Items tab. Click the Perform icon. Notice the Reject PO button on this step.
Click Reject PO. A list of steps that you can send the task back to displays when you click the down arrow in the To dropdown. In this example, the VP can reject the task back to the manager Jerry or the sales person (desiger user).
Select Manager Approval (jerry) from the dropdown then fill in a reason for the rejection - "Does this project conflict with the Sales Conference in LA". Click Submit. The message "Task successfully rejected" displays.
Click theInbox icon. The task is removed from the VP's Task List. Logout.
The manager receives an email with the subject "You have a new task for {your flow name}". Note the reason for the rejection is included in the email body. Click the link in the Rejection email.
Login to your space as jerry@<your tenant>. The Sales Person's (designer user) Task List displays. Click the Perform icon. Change the comment to inform the VP that the project does not conflict with the conference. sign and click Finish or Send to VP. Logout.
Login to your space as ed@<your tenant>. Select Task List from the Important Items tab. Click the Perform icon.
Approve, sign then click Finish. Logout. The sales person (designer) and the customer will receive an email with the signed PO.

Example 8 - Save/load

The Save/Load property adds a Save button to a workflow step. If the sales person cannot complete the PO in one session, they can partially fill the purchase order form, save it, then return to complete it at a later date. We will add the Save button to the PO step in this example. Also, we will take this opportunity to view the audit trail - a feature that is available for any task in the Task List. The audit trail is very useful when you want to view the task's history.

Modify the workflow:

Login to your tenant as the designer user.
Edit the Purchase Order Application, click the Flows tab, then edit the Purchase Order Workflow.
Click on the flow designer toolbar to display the flow Properties panel. Check the Save/Load property.

Click the PO step to display the property panel for this step. Click on General Settings Section. Check the Save/Load property.
Change the label of the Save button by typing "Save for Later" in the Save Label field.
Click Submit
Repeat steps 4, 5 and 6 for the Sales Review, Manager and VP Approval steps.
Click on the Client Approval step. Verify that the Save/Load property is unchecked.
Click the save/exit icon to save your changes.
Logout of the flow designer.

Test Example 8:

Click the link to your space that you bookmarked earlier. Login as the designer user.
Select the Purchase Order Workflow from the Purchase Order tab. Fill in a few fields on the PO. Note the Save button is added.
Click Save for Later. The "Save successful" message displays.
Click Task List on the Important Items tab.
Since the sales person only has one task in the Task List, the saved task will display. However, if you have many tasks in the list and you only want to see the partially completed ones, click the Saved Task icon at the top.
Click the Perform icon. Fill in some more fields. Click Save for Later.
You can click the Save button as many times as you want. Clicking the view task history icon will show the audit trail for the task. You will see an entry for each time the task was saved. The task shown in the image was saved 3 times and is currently locked by the sales person (max).
When all the fields in the PO are filled in, click Send.
Run the rest of the workflow as described in the previous examples. You will see the Save button on any of the steps that require the user to log into .

Example 9 - PO Save to User

Manager Jerry is going to the Sales Conference in LA. As he is preparing to leave the office, a PO requiring his approval comes in. Example 9 will show you how Jerry can quickly reassign the PO to another manager, Sue, so he can leave for the conference.

We will need to create another user, Sue Blue. A dropdown control with a list of managers will be added to the PO step so Jerry can select the manager he wants to reassign the PO approval to - in this case Sue.

Create another user:

Log on to as the tenant admin.
Click Manage Users on the Manage tenant page
Click the add new user icon which will bring up the Add New User form
Enter "sue" as the User Name then enter all the required information.
Leave the Reports To and Role fields empty. Click Submit.
You should be back on the user list. Logoff.

Modify the PO step:

Login to your tenant as the designer user.
Edit the Purchase Order Application, click the Flows tab, then edit the Purchase Order Workflow.
Click the PO step and the to edit it.
Add a field named "ManagerID" with a label "Manager ID" to the Sales Information Section. Uncheck the Visible property.
Drop a Dropdown control under the Manager Approval Section. Change the Decorator property to the blank option in the Decorator dropdown on the Properties panel.
Set the label and name of the control to "Managers".
1. Uncheck the visible property
2. Add two managers to the dropdown control's Option's property. The option syntax is value=label. Value must be the manager's username and the label can be a more user friendly label such as the manager's first and last name.
  jerry=Jerry Mouse
  sue=Sue Blue
Click the Properties Style tab and set the control width to half the width of the form.
Drop a Message control to the right of the Managers dropdown.

Add this text to the message control's Message property.

Code Block
To reassign your approval task to another manager, select that manager from the Managers dropdown and click the Save button.

Set the Name property to ReassignMsg. Uncheck the visible property

Modify/Add Rules:

We will create a rule that show the Manager Dropdown and the reassign Message controls only when the flow is on the Manager Approval step.

Click the rules icon on the toolbar.

Expand

title	Click here to see how to create this rule

The Visual Rule Builder consists of 3 wizards:

Condition wizard - describe the conditions under which a set of actions should be executed
Action wizard - declare the actions that should be taken when the condition is true
Else Action wizard - declare the actions that should be taken when the condition is false

Click the to add the rule.
Name it Show/Hide the Manager DD and Reassign Message controls on the Managers Step
Click the Rule Builder button then click Add Condition - this is the Condition wizard
Select current step from the first dropdown.
Select is from the second dropdown
Select Manager Approval from the third dropdown
Click Next then click Add Action - this is the Action wizard where you set up actions that will happen if the condition is true
Set the Managers control to visible
Add another action to set the Reassign Message control to visible
Click Next then click Add Action - this is the else action wizard where you set up actions that will happen if the condition is false
Set the Managers control to hidden
Add another action to set the Reassign Message control to hidden
Click Finish

Edit the rule "Populate Sales Person" and add this action line under the SalesID to userID() line:

Expand

title	Click here to see how to Modify the Populate Sales Person Rule

Click the on the Set SalesID to userID().
Click Add Action
Select ManagerID from the first dropdown
Select to from the second dropdown
Type user in the Expression box - a list of Rule Builder functions for User details will display
Scroll down and select the userManagerID function.
Add the closing parenthesis and tab out of the Expressions box.
Click Finish

Add a new rule to copy the selection from the Managers dropdown into the ManagerID control. Remember we have set up the ManagerID template to route this step of the workflow to the user name specified in the ManagerID control.

Expand

title	Click here to see how to create the rule in the Visual Rule Builder

The Visual Rule Builder consists of 3 wizards:

Condition wizard - describe the conditions under which a set of actions should be executed.
Action wizard - declare the actions that should be taken when the condition is true.
Else Action wizard - declare the actions that should be taken when the condition is false.

Click the to add the rule.
Name it Reassign to User
Click the Rule Builder button then click Add Condition - this is the Condition wizard
Select Managers from the first dropdown.
Select is filled from the second dropdown
Click Next then click Add Action - this is the Action wizard where you set up actions that will happen if the condition is true
To set the value of the ManagerID control to the value of the Managers control:
1. Select ManagerID from the first dropdown.
2. Select to from the second dropdown
3. Begin typing "man" in the Expression field. A list of the fields in the flow that begin with the letters "man" display. Select the Managers field from this list.
This rule does not require an else action. Click Finish

Click the save/exit icon to save the changes to the PO form.

Modify the workflow:

Click the Manager Approval step.
1. Click the Image Removed Image Added Edit Step Properties icon. Click on the General Setting tab. Check the Save to User property and verify that the Save/Load property is checked.
2. Change the User property from {subject.reports.to} to {ManagerID} - this must now be set to a dynamically populated control in the PO form.
3. Change the label of the Save button to Save.
Click the save/exit icon to save the changes to the flow.

Test Example 9:

Test the flow to the step for Manger Approval
When performing the task from Jerry's Task List, select the other manager (sue) from the Manager's dropdown. You do not have to sign it.
Click the Save button. The task will be removed from Jerry's Task List.
Login as the other manager (Sue). The PO Manager Approval task is now on her task list.
Perform that task. The flow will be routed to the VP if the amount of the PO is greater than or equal to > $10,000.00. If the amount is under $10,000.00, the flow will complete.

Example 10 - PO Save to Role

In some cases, you may want multiple actions taken during a step in the workflow. Let's say you want to collect comments about the PO from more than one VP in the company. The PO can be routed to the first VP (Ed) who will comment, click Save and the approval task will be assigned to the Task List of all users with the VP role. A second VP can then perform the task from their Task List add their comment, click Save. The last VP to comment signs to complete the flow.

In this example, we will drop the comment control in the VP section of the PO into a repeat control so more than one manager can comment and add some message controls to clarify the instructions. Our workflow must use the Save to Role feature so the saved task is assigned to all users with the VP role that we specified for the VP step.

We will need to create another user with the role of VP.

Create another user with the VP role:

Log on to as the tenant admin.
Click Manage Users on the Manage tenant page
Click the ! add new user icon which will bring up the Add New User form
Enter "jim" as the User Name then enter all the required information.
Leave the Reports To field empty.
Select "VP" from the Role dropdown. Click Submit.
You should be back on the user list. Logout.

Modify the PO step:

Login to your tenant as the designer user.
Edit the Purchase Order Application, click on the Flows tab, then edit the Purchase Order Workflow.
Click the PO step and the to edit it.
Drop a Message control inside the VP Approval section above the VP Comments text area.

Put the following text into the message control's Message property

Code Block

If you want another VP to comment:
        <ol>
        <li>Add your comment below</li>
        <li>Click the save button to return this PO onto the task list of all employees with the VP role</li>
       </ol>
       Other VPs can add comments by clicking the + icon.

Drop a Message control inside the VP Approval section, below the VP Comments text area
1. Select "Warning" from the Message Type dropdown.
2. Put the following text into the message control's Message property.
  Code Block
  The last VP to comment must sign the approval.
Click the Comments control inside the VP Approval section
1. Type "Enter both your name and comments" into the Placeholder property
Drop a Repeat control inside the VP Approval section immediately above the VP Comments text area.
Drag the VP Comments text area into the repeat control
1. Click to select the VP Comments text area control
2. Set the Min property to 0
3. Set the Max property to 4
Click on the VP Approval section
Type f-page-break in the CSS Class property for the VP Approval section. This css class will put the VP Approval on a new page in the workflow pdf.
Click the save/exit icon to save the changes to the PO form.

Modify the workflow:

Click the VP Approval step
1. Click the Edit Step Properties icon. Click on the General Settings tab. Check the Save to Role property.
2. Verify that the Save/Load property is checked.
3. Change the label of the Save button to Save.
Click the save/exit icon to save the changes to the flow.
Logout as the designer.

Test Example 10:

Test the flow to the step for VP Approval. Be sure to make the amount of the PO greater than or equal to $10,000.00 so the workflow navigates to the VP step.
You should be logged in as the user, ed for the VP step.
Add a VP Comment. Do not sign it.
Click the Save button. Logout. Notice the task remains on Ed's Task List. All users with the VP role will receive a task notification letting them know the PO is available on their tasks lists again. For this example, users ed and jim receive a Task Notification email.
Login as the other VP user (jim) and view Jim's Task List
Perform the task.
Click the icon to add another comment and sign the section.
Click Finish.
Logout of your space.
Check the workflow PDF attached to the final email. Verify that the VP Approval section is on a new page in the PDF.

Example 11 - PO Workflow Escalation

If workflow tasks are not completed within a certain specified time, you can remind the user via an email (s) that there is a deadline for task completion and you can reassign the task to another user when the deadline expires. In Example 11, we will use the escalation feature to set a five minute deadline for manager Jerry to approve the PO. He will receive two emails in that time frame reminding him that he has a task that requires his attention. When the five minute deadline expires, Jerry will receive an email informing him that the task has been reassigned to manager Sue.

In Example 9, manager Jerry manually selected the manager to reassign the task to from a dropdown control in the PO step. In this example, we will configure the Escalation feature so that automatically assigns the task to the user/role specified after the time period expires.

We will use the Setup Escalation link on the manager step. Escalations can be set up for any of the steps in our flow except the step performed by the anonymous user (Client Approval).

Modify the workflow:

Login to your Live Forms tenant as the designer user.
Edit the Purchase Order Application, click the Flows tab, then edit the Purchase Order Workflow.
Click the Manager Approval step. Click on the Escalations Section in the Properties Panel.
Set up the Deadline:
1. Click on the Add Escalation button
2. Select Complete Within from the dropdown in the Condition field. Enter "5" on the minutes box that displays.
Setup the Reassignment:
1. Click on the Action tab. Select the Reassign Task option.
2. Select "User" from the Reassign To dropdown. Type "sue" in the Select User Assignee's text box. Note the list of users that begin with the letter s displays as you type.
Setup the email that will inform Jerry that the deadline has expired for the PO task.
1. Click on the Notifications Tab. Change the No Notification slider to on.
2. Select "Current Owners" from the Send To dropdown. Current Owners will notify users who currently have the task on their Task List via email.
3. Replace the template {flow.activity.assignee} with {flow.activity.escalation.reassignee} in the Email message. This change will put the name of the manager the task was reassigned to (Sue) in the message to Jerry.
Setup the Reminder emails to be sent. For Example, we want a total of two reminder emails to be sent - one every two minutes during the 5 minute time period.
1. Click on the Reminders Tab. Change the Reminders are Off slider to on.
2. Slide the "Limit Reminder" to on. Enter "2" in the Every text box. Select "Minutes" from the Time Unit dropdown.
3. Enter "2" in the Occurrences(s) text box.
4. Leave the text of the Reminder message at the default.
Click Submit.
Click the save/exit icon to save the changes to the flow.
Logout as the designer.

...

Test Example 12:

Test the flow to the Client Approval step. Approve the PO.
Logon as the sales person (designer).
Click the Important Items tab then click the Task List.
Click the quick view icon. The Quick Approval screen will display.
If the client did not approve the PO and sent it back to frevvo with comments, the Sales Person can click the Details button to view those remarks.
Notice the text we added as the Quick Approval summary appears at the top.
Add a comment and click Approve. You will see the message "Task Successfully Approved".
Notice the Sales Approval section displays on the Sales Review, Manager and VP Approval steps.
Complete the flow.

Example 13 - PageBreak for Mobile

What do you have to do to run the PO flow on an iPad or iPhone? Nothing!!!! automatically breaks up the form into steps and adds Back and Next buttons. uses the device’s features to make the mobile experience easier for the user e.g. specialized keyboards.

If you want to specify where the logical breaks are, you can use the PageBreak control to break the PO step into small logical pieces. For example, our PO has Instructions, Sales Information, Client Information and Client Services Order sections. In this example, we will use the PageBreak control to display the Instructions, Sales and Client Information sections on the same screen on an iPad and and on two separate screens on a smartphone. We will add another PageBreak control to display the Client Services Order section on a separate screen on both devices.

Modify the PO step:

Login to your Live Forms tenant as the designer user.
Edit the Purchase Order Application then edit the Purchase Order Workflow.
Click the PO step then click the Edit icon.
PageBreak controls in your workflow display by default. If you want to hide them while you are developing your workflow, click the show/hide page breaks icon in the toolbar once.
Drag a PageBreak control from the palette and drop it below the Sales Information section. Click on it and uncheck Tablet. This PageBreak control will only be recognized on an iPhone.
Drop a PageBreak control from the palette and drop it between the Client Information and Client Services Order sections.
Leave the Phone and Tablet checkboxes checked.
Click the save and test icon. The Save and Test feature saves the changes to your flow and allows designers to test forms/flows without leaving the Flow designer.

Test Example 13:

When you click the save and test icon, you will see the desktop view. The Instructions, Sales Information, Client Information and the Client Services Order sections display on the same screen.
Click the Tablet icon at the top. The Instruction, Sales Information and Client Information display on the same screen, as expected, since the first PageBreak was setup to be recognized on the phone and not the tablet, The second PageBreak was setup to be recognized by the phone and the tablet so you will have to click Next, to see the Client Services section.
Click the Phone icon at the top. You will see the Instructions and Sales Information sections only. The first PageBreak was setup to be recognized on the phone so you will have to click Next, to see the Client Information section. The second PageBreak was setup to be recognized by the phone and the tablet so you will have to click Next, to see the Client Services Order section.
Close the Test window. Click the Cancel changes icon twice to exit the Flow Designer.

Example 14 - Fast Finish

In this example, we will switch to an Employee On-boarding workflow to demonstrate the Fast Finish feature. This feature adds a Finish button that allows the user to fast forward through a screenflow. It is very useful if your screenflow contains a lot of steps. Let's consider this scenario:

A new employee starts their first day at your company and needs to provide their information. The employee is handed an iPad with a link to an Employee Onboarding workflow that is used to collect basic information, W - 4 allowances and Education information. When completed, the new employee clicks the Continue button and the flow is routed to their manager for approval. If approved by the manager, the flow is routed to HR for final processing.

Imagine the employee completes the flow through the Confirmation step and then decides to navigate back to make a change to the Employee Information step. Without a fast finish button the screen flow will make the user review each step - Employee Info, W-4, Education Info and Confirmation in order to submit the forms to the manager for approval. But by adding Fast Finish the new employee can now click on the Finish button and (as long as all required fields are complete and valid in all other flow steps) immediately submit the forms to the manager for approval.

We will use the Navigation toolbar at the top to navigate back and forth between the steps of the flow. We will configure Fast Finish on the first three steps. We will also need to add another role, HR and another user, Pam who has the HR role, to test it.

Add a Role and User:

Login as your tenant admin.
Create a new role - HR.
Add a new user pam and give her the role HR. Logout.

Review the workflow:

Browse one of these URLs:
1. https://app.frevvo.com - if your tenant is in the frevvo Cloud
2. http://<server>:<port>/frevvo/web/login - if your tenant is in-house. Replace the <server>:<port> with the information for your in-house server.
Login as the designer. Edit the Purchase Order Completed or Purchase Order application.
Click the Flows tab. Edit the Example 14 - Fast Finish workflow.
Click on the Employee step.
1. Notice the Fast Finish property is checked in General settings on the Property panel.
Click on the Allowances step.
1. Notice the Fast Finish property is checked in General settings on the Property panel.
Click on the Education step.
1. Notice the Fast Finish property is checked in General settings on the Property panel.
Click cancel changes icon to exit back to the Flows Home Page in the flow designer.

Test Example 14:

Click the Test icon for Example 14 - Fast Finish
The Employee Information step prefills the user name and uses the Geo-location feature to capture the user's location. All browsers will show a pop up asking the user's permission to use their location. Click to give permission.
Fill in the other required fields. Click Continue.
Fill in the W - 4 Allowances. Notice the Total Allowances field is updating as you enter values for the other allowances. this calculation is done using a business rule. Sign then click Continue.
Fill in the Education Information step. Notice if you check "yes" for the "Permission to access college transcript" question a table requesting additional information displays. This is controlled by a show/hide business rule. Click Continue.
On the Confirmation step, click Review Your W-4 form. The W - 4 will open in a separate browser tab merged with the data you entered. This is an example of the Pixel-perfect PDF generation feature.
While reviewing the pdf, you realize you made a mistake when entering your social security number. Close the pdf.
Click the Employee Information step in the Navigation toolbar at the top.
Make a change to the SSN. Click the Finish button.
The flow will skip the Allowances and Education information steps and return you immediately to the Confirmation step.
Review the pdf to verify the updated SSN is now displaying. Close the pdf.
Sign then click Send to Manager.
Logout as the designer.
Login as Jerry. Perform the task. Add a comment and sign. Click Send to HR.
Logout as jerry.
Login as Pam and complete the flow.
Logout of .

Example 15 - Summary

In this example, we will add a Summary step to the Employee Onboarding flow. This will simply display a Summary view of all the data that has been entered into the various steps of the flow prior to the Summary step. Previously completed steps in a workflow can be viewed by all users but editing data is only allowed for the currently logged in user. Clicking on the Details button navigates to the selected step for viewing/editing.

We will change the Navigation property to a different format and use the Summary step to navigate back to a previous step.

Review the workflow:

Login as the designer. Edit the Purchase Order Completed or Purchase Order application.
Click on the Flows tab. Edit the Example 15 - Summary workflow.
Click on the toolbar to display the workflow properties.
Notice the Navigation toolbar is set to Percent. The progress of the workflow displays as a percentage when this option is selected.
Click the Setup Searchable and Summary Fields link. Designers select the workflow fields to display in the Summary step using this wizard. Note most of the fields in the workflow have been selected to display in the Summary Step. Clicking on the Searchable fields tab shows the First and Last Name fields in Step 1 have been setup as Searchable Fields. They can now be used as search criteria when searching submissions.
Notice the Summary step between the Education and Confirmation Step. The Summary step displays the fields selected with the Setup Searchable and Summary Fields wizard and all the data that has been entered into these fields prior to the Summary step. Clicking on the Details button navigates the user to the selected step for viewing/editing.
Click cancel changes icon to exit back to the Flows Home Page in the flow designer.

Test Example 15:

Click the Image ModifiedTest icon for the Example 15 - Summary workflow.
Run the flow. Notice the percent completed is displayed at the top
On the Summary step, click the Details button on a previous step to view the entered data.
Change a value in one of the fields.
Click the Continue or Finish button on the rest of the steps.
Complete the flow.

Example 16 - Save on Navigate

Imagine a large workflow with many steps - let's say 30. You are filling in the screens and when you get to screen 25 you accidentally close your browser! None of the entered information is saved and you will have to begin all over again. Unless you check the Save on Navigate checkbox for the flow. This feature will automatically save the flow to your Task List. When you click the Perform icon to open up the task returns you to the last step where data was being entered. If you navigate to previous steps, all entered data displays.

Review the workflow:

Login as the designer. Edit the Purchase Order Completed or Purchase Order application.
Click on the Flows tab. Edit the Example 16 - Save on Navigate workflow.
Click on the toolbar to display the flow property panel. Notice the Navigation property is set to Navigation Toolbar and the Save on Navigate checkbox is checked to turn the feature on.
Click cancel changes icon to exit back to the Flows Home Page in the flow designer.

Test Example 16:

Click the Image ModifiedTest icon for the Example 16 - Save on Navigate workflow..
Fill in the Employee Information and Personal Allowances steps in the New Employee On boarding workflow.
Fill in the first column of the first row of table on the Education step.
Close the browser.
Open the browser again.
Login as the designer.
Click My Tasks. The unfinished task will be on your Task List.
Click the Image Modified Perform icon. returns you to the step where you left off. If you navigate to the Employee and Allowances steps, you will see that the information was saved but the data that you entered into the first column of the table on the Education step is not.
Continue entering data from this point to complete the flow.

Task Notification Email.

Versions Compared

Old Version 8

New Version Current

Key

What are we going to build?

Example 4 - PO for Manager Approval

Test Example 6:

Example 7 - PO Reject

Modify the workflow:

Test Example 7:

Example 8 - Save/load

Modify the workflow:

Test Example 8:

Example 9 - PO Save to User

Create another user:

Modify the PO step:

Modify/Add Rules:

Modify the workflow:

Test Example 9:

Example 10 - PO Save to Role

Create another user with the VP role:

Modify the PO step:

Modify the workflow:

Test Example 10:

Example 11 - PO Workflow Escalation

Modify the workflow:

Test Example 12:

Example 13 - PageBreak for Mobile

Modify the PO step:

Test Example 13:

Example 14 - Fast Finish

Add a Role and User:

Review the workflow:

Test Example 14:

Example 15 - Summary

Review the workflow:

Test Example 15:

Example 16 - Save on Navigate

Review the workflow:

Test Example 16:

Page Comparison

Versions Compared

Old Version 8

New Version Current

Key

What are we going to build?

Example 4 - PO for Manager Approval

Test Example 6:

Example 7 - PO Reject

Modify the workflow:

Test Example 7:

Example 8 - Save/load

Modify the workflow:

Test Example 8:

Example 9 - PO Save to User

Create another user:

Modify the PO step:

Modify/Add Rules:

Modify the workflow:

Test Example 9:

Example 10 - PO Save to Role

Create another user with the VP role:

Modify the PO step:

Modify the workflow:

Test Example 10:

Example 11 - PO Workflow Escalation

Modify the workflow:

Test Example 12:

Example 13 - PageBreak for Mobile

Modify the PO step:

Test Example 13:

Example 14 - Fast Finish

Add a Role and User:

Review the workflow:

Test Example 14:

Example 15 - Summary

Review the workflow:

Test Example 15:

Example 16 - Save on Navigate

Review the workflow:

Test Example 16: