Keeping your Forms and Flows in Sync

Forms that are used as steps in a workflow can be created in the Form or Flow designers. There are two approaches a designer can choose from when creating a flow:

1. Create forms in the Forms designer and then drag the form(s) into the flow as the steps (Existing Forms).
2. Create the flow by dragging a New Form from the palette and drop it onto the flow canvas. Then click the edit icon and create the form in the forms designer that opens up in the flow designer.

There are pros and cons to each approach when you need to make small updates to one of the steps of your flow:.

• The designer can go back and edit the forms in the forms designer then drag the updated forms into the flow.  If you choose to do this, then you have to redo any properties for that step. (assign users/roles, task information, Pending messages, customized Save and Continue buttons etc).
• Or you can update the form directly in the flow by clicking the edit icon. This approach is quicker but the changes that you make to the form from within the flow designer DO NOT update the form in the Forms designer.

Let's say you create the perfect form step in a workflow and now you want to use it in another flow. How do you extract the form step from the flow so that it is available in the Forms designer?

 If you click on a form step in a workflow, you can download that step from the flow as a standalone form and upload it into the Forms designer. Simply click on the step in the flow then click the form icon. If you have designed your workflow using Linked Steps in a Flow the icon to download the form step will only appear on the parent step.

The downloaded file is a _form.zip file and is named according to the convention shown below:

• the flow name
• the version number of the form step plus 1
• _flow step name
• _form.zip

Here is an example of the downloaded file for step 1 named Employee in a workflow named Vendor Quote.

This is an easy way to keep your forms and flows in sync and reuse forms created/updated in the flow designer in other workflows or as standalone forms.

Form actions and Doc actions, excluding Doc URIs, are copied to the extracted form if that step in the flow was an existing form that was dragged into the flow and that form had configured actions.

Activity doc actions are retained. Email Activity doc actions are copied to the Additional Email tab in the extracted form.

Doc Uris are cleared when applied to a form that is created in the forms designer then dragged into the flow designer as a step. Designers will have to manually add them to the extracted form.

New Form

The New Form palette control allows you to create a new form step in your workflow directly inside the flow designer. If you do not have an existing form for the step you require, drag & drop the New Form into your flow and create the step in place. This will launch the  form designer where you can add controls to the form just as you would if you designed the form from the Forms Home page.

Drop the New Form from the palette into the flow. Click to select it. Then click the edit icon to launch the form designer. A unique and arbitrary name will be generated automatically for the step--Step 29 for example. You'll change this name inside the form designer.

Existing Forms 

The palette contains all of the forms that you have already created and which are listed in your current application's forms home page. You can use any form as a step in the flow. Adding an existing form to the flow creates a copy of that form. If you later edit the form from the forms home page,  those changes will not affect the step in the flow. It remains as it was at the time you copied it into the flow. If you want to update the flow to have a new copy of the form, delete the form from the flow and drag it in again. You can also edit the form directly in the flow. Conversely these changes to the form inside the flow do not affect the original form in the form home page.

When you add an existing form as a step in your flow:

• PDF mappings associated with the form will be copied to the flow
• If the form has a configured Email data to a specified location doc action it will be copied to the Activity Document Action for that step.
• If the Email data to a specified address wizard is empty but an Additional Email doc action is configured, it will be copied to the Activity Document Action for that step.

Summary

Drag a Summary step anywhere in your 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. Clicking on the Details button navigates to the selected step for viewing/editing.

Previously completed steps in a workflow can be viewed by all users but editing data is only allowed for the user that initiated the flow. For example, if the Summary step is part of a screenflow performed by the same user, editing is allowed when this user clicks on the Details button. Once the flow navigates to a different user, previous steps are rendered read-only and cannot be edited. Refer to Flow Processing Modes for more information.

The Print button is available on Summary steps by default. Refer to Printing Flows for the details.

The designer can specify a CSS class, a Button label and a Decorator for the Summary step on the Settings property tab.

The fields that display on the Summary Step are selected by the designer in the  Summary wizard.

http Wait Notify

http Wait-Notify is a step, configured with a post url, that can be added to a flow. The flow data is posted to this url when the task is executed. A call back url is included in the post. The flow and task are suspended until the receiver posts back.

The timezone must be added programmatically by the service you are using. http steps can be performed by an anonymous user.

Let’s consider this scenario. Your company has a purchase process workflow. One of the steps in the workflow requires approval from several other approvers before the flow can continue to the next step. These approvals should happen in parallel and not one after the other. A web component that would manage those approvals is in place. An http Wait-Notify can be added to the Live forms flow with a URL to the web component to collect the signatures. The callback URL will be included in that post. The flow will be suspended until all the signatures are collected. The remote web component will notify the Live Form flow using the callback URL when the signature task is completed. If the http step in the flow has doc actions configured, they will be performed and the flow will proceed to the next step.

Now let’s take a look at a simple flow that will accomplish the scenario described above. This flow contains the Purchase Request form submitted by the company purchasing manager as the first step, followed by an http step which provides the url to the web component that handles collecting the signatures from all the required approvers, followed by a Summary step. Remember the flow will be suspended until all the approval signatures have been collected by the web component. The web program will then use the callback url to proceed to the Summary step of the flow.

To set up the http URL, click on the http step and enter the URL for your post. In the image below, we are entering the URL to a remote test server running a service that can be used to test this feature: http://localhost:8082/services/testwaitnotify

10:14:13.071 |-INFO 
[http-nio-8080-exec-2] [     
c.f.f.s.FlowService] - httpWaitNotify: POSTing to
http://localhost:8080/services/testwaitnotify Jun 21, 2013 10:14:13 AM org.apache.catalina.core.StandardWrapperValve invoke 
INFO: TesthttpWaitNotifyServlet: notify URL is: http://localhost:8080/frevvo/web/tn/willstenant/user/designer/app/_fZMUEK5vEeKl1rJ0IEAosw/flowtype/_pJUvcMFJEeKKR-e9RKn4zg/notify?embed=true&_method=POST&nextstepTypeId=next&locale=eng&_method=post&embed=true&_submission=4a3850a2-4c62-4a1b-b2e1-f50bba6547c8

When the first step in the flow is submitted, you will see an outbound message in the frevvo log similar to the one shown below:

Notice the latter portion of the entry contains the call back URL

This URL is generated by the frevvo server and will point to whatever host/port the frevvo server is accessed on. If the frevvo.forms.server.external.url parameter in config.properties or web.xml is set, it will always use the value of that property.

This URL is used by the remote service to “wake” up the Live Forms flow.  Any document actions configured will be performed and the Live Forms flow will resume. Flow visibility must be set to public. 

You cannot reset a flow to an http step.  There is a new flow status, WAITING, that you can use to find steps in a flow that is in a suspended state. 

Configure a History Message on the step before the http step if you want to see relevant information in the audit trail.  

Anonymous Email

Many business scenarios require a step in the workflow to be performed by a person who is not an authenticated user - someone who is not logged into .  

The email step allows the design of a flow where some steps are performed by authenticated users/roles and other steps are performed by an anonymous user. The anonymous user receives an email, clicks on a link in the email and accesses the task without being authenticated, performs the anonymous step, clicks continue, and the flow is routed back to an internal, authenticated user. The Email step suspends the flow (saves the flow to the database), sends an email to the specified email address with a back link. The email recipient clicks the link and the flow renders even though he/she is not logged in. 

A typical situation is an employee who submits a request to an outside vendor for a quote, which then needs to be approved by the employee's manager. The second step of the flow sends an email to the vendor, the flow is suspended until the vendor submits his quote, then the flow continues for the manager's approval. The Vendor Quote Workflow Tutorial consists of step by step instructions to completely build/test a workflow that uses the email step.

The Vendor Quote workflow, shown in the image, has 4 steps:

• Step 1 is the Vendor Quote request filled in by someone in the company with the employee role. The Employee role was selected from the role list for this step.
• Step 2 of the flow sends an email to the vendor. The Email step was dragged from the palette and dropped into the flow. This step must have an email address. It can be filled in by the user or populated via a business rule. In this case, the value of the control named VendorEmail will be used to determine the email address to send to. VendorEmail is an example of a template. An email is sent to the email address in the VendorEmail control with the link back to the flow.
• Step 3 is what the vendor sees when the link inside the email is clicked. The step that goes to the anonymous user cannot have a role, dynamic role or user assigned to it. This step is really a section in the main form that is shown only when step 3 is being performed. The Vendor and Manager sections are shown/hidden using a business rule. The flow is suspended until the vendor completes his section. In a future version of , the amount of time the flow remains suspended can be configured. 
• Step 4 is the Manager Approval step. After the vendor submits the quote information, the flow proceeds to the manager step and puts the Vendor Quote Task on the Task List of the employee's manager .  The manager can approve/reject the quote. If approved, the flow is completed.

Here is what it looks like when the flow is performed:

When the Vendor clicks on the link, the relevant parts of the flow are shown. The notify URL automatically adds the timezone from the browser.

The manager approve/rejects the flow from his Task List. Any configured Form/Doc actions , such as a display message, will execute. If the manager approves the task, the workflow is complete. Note the email step in the flow is greyed out.

Some Tips about Email steps

• Email steps can be performed by an anonymous user. 

• The behavior of workflows consisting of multiple consecutive anonymous steps has changed. Refer to this topic for the details.

• The anonymous email step will show up in the navigation bar for other users as usual; you can assign it a decorator but you cannot click on it.

• The task will show up in the Audit Trail in the Waiting state when it is waiting for an anonymous recipient. You can search for it, do all the usual things.

• Users can reject anonymous steps in a flow by clicking the Reject button but a subsequent user cannot reset a flow back to these steps. See the topic below for more information.

• If navigation is used to go to previous step, the Email step will be skipped. It would get recalled if you reset to a prior step and the flow continues thru it's normal flow. 

• Configure a History Message on the step before the Email step if you want to see relevant information in the audit trail. The History Message can be templatized so you can see who the email address of the recipient.

Email Properties

When you drag/drop an Email step into your flow and click on it, a Properties panel displays. The Name,  Pending Message, Precondition and Decorator properties work exactly like they do on other types of steps. Task Info does not apply to an EMail step. If you want to set up a History Message you must do so on the step in your flow that the anonymous user is going to see.  Note the envelope decorator to identify the Email step in the flow. 

 Step Doc Actions work exactly like they do on other types of steps. 

When you click on the step in your flow that is seen by the anonymous user, a Properties pane displays. Several of these properties, do not apply to a task performed by a non-authenticated person and will have no effect. These properties are: Role List, Role, User, Task Info, CSS class, Preconditon, Save Load, Save to Role, and Save to User and . You can customize the button label, history message and select a decorator for this task that will display on the Navigation toolbar.  

The Task Notification Email  wizard also works exactly like it does on other types of steps except that the default message content is slightly different. It references {task.notify.url} which is the back link URL that the non-authenticated person clicks in the email to perform their step in the workflow. The designer can customize this message however, if you don't include the {task.notify.url} in your email content, the email recipient will never be able to access the task.

Resetting a Flow with an Email step

 Consider a flow with the following navigation: Step 1 is performed by an Employee > Step 2 is an Email step > Step 3 is performed by an Anonymous user > Step 4 is performed by a manager. 

• Employee starts flow, email gets sent, the anonymous step is performed and a task is generated for manager.
• A flow cannot be reset to the Email or Anonymous user step. In this example, only a reset to the employee step is allowed. 
• The Employee performs the step again and clicks Continue. The Email step is performed again and another email will go to the anonymous user.

 The same behavior applies to a flow with an http step. 

Searching Tasks with an Email step

Consider a flow with the following navigation: Step 1 is performed by an Employee > Step 2 is an Email step > Step 3 is performed by an Anonymous user > Step 4 is performed by a manager.

• The flow has been started and the notification email has been sent.
• The flow is now in the WAITING state.
• The Employee can search for a status of WAITING and reset the flow to a previous step or view the audit trail.

• The tenant admin can search for a status of WAITING, reset the flow to a previous step, abort it or view the Audit trail. 

The same behavior applies to a flow with an http step. 

Form Viewer Control

The Form Viewer control is used to allow a generated PDF to be viewed as part of a form step in a flow. This control only appears on the Forms palette in the flow designer when you click the icon to edit an step in a flow.