Planning for v8.0

Live Forms v8.0 is no longer supported. Please visit Live Forms Latest for our current Cloud Release. Earlier documentation is available too.

Planning for v8.0

The initial release of

Version 8.0 was deployed to the frevvo Cloud on 12/15/2018. A future release will be available for in-house customers.

We recommend that you read the information below before you begin.

Automatic Upgrade for Live Forms Online (Cloud Hosted) Customers

Live Forms Online cloud hosted customers will be automatically upgraded on TBD. The automatic cloud upgrade will be seamless. Cloud customers should review these topics to prepare for the new version of 

.

If you have any questions, please email support@frevvo.com.

Migration Considerations for Cloud Customers 

 frevvo is committed to making

more intuitive and easier to use. Version 8.0 is the first phase of this effort. More features/improvements are coming in future releases.

Redesigned Flow Designer Canvas

When you launch the Flow Designer, you will see a more intuitive canvas to create/edit workflows. Designer can quickly see how the flow is routed and have easy access to the properties for each workflow step. 

The new canvas:

Existing workflows will automatically be converted to the new format when the Cloud is upgraded. No worries - at runtime your existing flows will work as before but they will look different when you edit them in the Flow Designer.

Easily Add an Anonymous Step to your Workflow

Anonymous steps in a workflow are steps that are performed by an non-authenticated user. This means the user does not have to login to

to perform their step in the workflow.  

This a common workflow scenario. Some examples are:

  • a Membership workflow that requires reference letters from an external person.

  • a Purchase Order Approval requiring the customers review and signature.

  • a workflow that is sent to an External Vendor for a Quote.

Anonymous steps are simply form steps that route to an email address in version 8.0. That's it.

Create an anonymous step in your workflow by following these simple steps:

  • Create the step you want the recipient to see or link to an existing one.

  • Click on the step then click the

    Edit Step Properties icon

  • Navigate to the Assignment tab.

  • Enter a valid email address in the Assign to Email field. Leave the Assign to User and Assign to Role fields blank. Only one email is allowed.

    checks that the entered address is in the correct format for email. An error displays if it is not. 

  • You can use Control Templates in the email field so that it’s dynamic. Enter the left curly brace - { - then start typing the control name and a pick list will appear with matching controls. Selecting the control form the list enters it into the field with the closing curly brace - }  

  • Customize the email that the anonymous user receives. Control Templates can be used in the email Subject and Message for dynamic behavior as well.

  • Click Submit.

At runtime, the value in the Assign to Email field is evaluated and an email that contains a link to the anonymous step is sent. The recipient clicks the link to perform the anonymous step. Logging into

is not require

  •  It is no longer a requirement to set the Who can start the form/flow permission to Anyone (No login required) - called Public in previous releases. The anonymous step will work with any of the Form/flow Visibility choices.

  • Designers can now design a workflow that rejects to an Anonymous step.

  • The Modify a Task feature now allows Tenant/flow administrators to reassign an anonymous step to a different email address.

Existing workflows, created with Email/Anonymous steps, will continue to work after the upgrade to v8.0. However, the ability to reassign an anonymous step to a different email address or rejection to an anonymous step are not available for workflows created with these types of steps. Please review Migrating Flows with EMAIL/Anonymous Task Steps for information to manually migrate these flows to take advantage of the new features.

Migrating Flows with Email or Anonymous Task Steps

Designing a workflow step performed by a non-authenticated (anonymous) user in previous versions required dragging/dropping an Anonymous Task Step from the Flow Designer Palette and configuring it with an email address. The step that followed the Anonymous Task Step was the actual step that the recipient would perform. This design approach was confusing and error prone. 

Workflows with an Anonymous Task Step (those built in previous versions) will be supported only for a limited number of releases. Designers must manually convert these workflows to the v8.0 format. New to v8.0 is the ability to reassign or reject an anonymous step. After converting your workflow, designers can take advantage of this feature.


To convert your flow from pre v8.0 to v8.0, we suggest you follow the same procedure that you use to update any other form/flow in Production. Review Administrator Best Practices if you need a refresher.

To convert your Anonymous Task Step to the v8.0 Simple Anonymous step(s) follow these instructions:

  1. Login to your Production tenant or the user account where your Production forms/flows are located.

  2. Ensure there are no flows in flight for the workflow you want to update.

  3. Download the workflow from your Production tenant or Production designer account.

  4. Upload it into a different application in your test tenant or designer test account

  5. Edit the existing Email/Anonymous Task step.

  6. Click the

    Edit Step Properties icon. Click on the Assignment tab.

  7. Copy the information in the Assign to Email, Task Notification Subject and Message fields. Paste this information to a text pad and save to your desktop. Click Cancel.

  8. Click on the step following the Email/Anonymous Step. (the step performed by the anonymous user)

  9. Click the

    Edit Step Properties icon. Click on the Assignment tab.

  10. Paste the information you copied in step 7 into the Assign to Email, Task Notification Subject and Message fields.

  11. If the Message field contains the {task.notify.url} template, change it to {task.perform.url} or {task.list.url}.

  12. Click Submit.

  13. Delete the Email/Anonymous Task step from the workflow.

  14. Save and Test the workflow.

  15. To replace the production workflow with the updated flow, download the updated flow from your test tenant or designer test account.

  16. Upload the updated workflow to your Production tenant. Be sure to check the checkbox to REPLACE an existing flow with the same ID. The checkbox to use existing schemas is checked automatically.