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

Flow Setting Properties

Properties Navigator

Clicking the Edit icon on the Flows Home page opens the workflow in the Flow Designer. The Properties Navigator panel displays in the lower-left portion of the Form Designer. This panel shows information about important properties setup for this flow step. Not all of the configured properties are shown in this view.

Open the Flow Properties wizard by:

  • Clicking inside a section or clicking on the  Edit Flow Properties icon in a section of the Properties Navigator. This immediately displays the property tab for editing.
  • Clicking the Edit Flow Properties icon in the Flow Designer toolbar

The Properties Tabs work the same way whether you open them from the Navigator or from the Flow Designer toolbar. 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 flow property setting is described below.

On This Page:

 

Flow Name

This is the name you see on the Flows home page where your flows are listed. We recommend changing the name to make it more meaningful than the arbitrary name assigned when you create it, but keep in mind it is a working name only, so users will not see it. It is recommended that you name your form/flows using characters that are suitable for filenames. Following the POSIX filename standard (A–Z a–z 0–9 . _ - ) will ensure it works.  Click the pencil icon above the Properties Navigator to edit the name then click the checkmark to save or the cancel icon to discard your changes. You can also change the name on the Settings tab.


Settings

Use the Settings tab to select general settings for your workflow.

You can access the Settings tab in three ways:

  • Click the  Edit Flow Properties icon on the Flow Designer toolbar. This will launch the Flow Properties wizard. It defaults to the Settings tab.
  • Click anywhere in the General Settings section in the Properties Navigator. This takes you directly to the Settings tab.
  • Click the  inside the  General Settings section in the Properties Navigator. This takes you directly to the Settings tab.
  • Select/enter the properties for your flow
  • Click the Submit button to save the changes or navigate to another tab.

Description

By default all flow descriptions say, “Edit the flow to change this description,” but you can change this if you wish. The description appears as a tool tip when you mouse over the area just to the right of the flow's share  icon on the Flows Home Page. You also see this description when you view individual submission documents.

Navigation

 can automatically generate and display a navigation toolbar for your flow which users can use to navigate back and forth between workflow steps. There are four available options:

  • None: This option displays no navigation toolbar. This is useful for situations where the same form is being passed between users for signatures e.g. Vacation Request workflow filled in by an Employee and signed by a Manager.
  • Navigation Toolbar: this displays a standard navigation toolbar with links for each step.
  • Percent: This displays progress through the flow as a percentage.
  • Step 1 of 4: This option displays progress through the flow as a counter.

The default value for Navigation is Navigation toolbar. When you configure the Navigation toolbar for your workflow, users will see the following:

  • The name of the current step displays with a bright blue color. Note that the active step number is also circled in bright blue. Steps that have yet to be performed display with a light blue color.



  • HTTP Wait-Notify and Anonymous Task steps, once performed, display with a faded blue color indicating that the flow cannot be reset to this step.
  • Skipped steps display with a light blue color and steps that have already been performed display with a black color. For example the Expense Report workflow shown in the image, has four steps: Expenses, Reviewer, Supervisor and Accounting. The employee fills out the Expense report for an amount less than $5000.00. The flow is routed to a company reviewer and if approved, to Accounting for final processing. If the amount of the expense had been greater than $5000.00 then the flow is routed to a Supervisor for an additional review before navigating to the Accounting department. The Supervisor step is skipped for Expense reports less than $5000.00. When the Accounting employee performs the task, here is what they will see:




  • The Expenses and Reviewer steps display in black since they have already been performed.
  • The Supervisor step is displayed in faded blue because it was skipped as the total amount of the expenses was less than $5000.00.
  • The name and number of the Accounting step, which is the step that is currently being performed by the Accounting employee, display in a bright blue color.

 Refer to the precondition topic to see how to use them to skip a step in a workflow.

Mobile vs Desktop Behavior

You may notice a difference in behavior when using a flow on the desktop vs on a phone/tablet. For Example: Imagine a two step flow where 1st step has 2 Pagebreak controls and neither step has an assigned role/user. On the phone/tablet this translates into a screenflow with 3 steps for 1st step and 1 step for 2nd step. You can use the Previous button to get back to the 1st step from the 2nd step.


However, on the desktop there is no "Previous" button so once the flow gets to 2nd step there is no way to get back to 1st step. If the designer does not configure the Navigation Tool Bar in this situation once the user gets to the second step in the flow, there is no way to return to the first step.



Anonymous Screenflow Navigation

A screenflow is a type of workflow consisting of a collection of sequential steps performed by the same user. What if you wanted that user to be anonymous? Configuring the Navigation Toolbar in an anonymous screenflow allows anonymous users to navigate back to a previous step in a screenflow. The set of available links is restricted to the steps that are executed in sequence by the anonymous user. Links to steps outside of the screenflow are not visible. The steps in the screenflow cannot have a role, dynamic role or user property assigned to them.

Configuring the Save on Navigate feature enables the screenflow to be completed in multiple sessions.Let's consider a Job Application workflow with the following requirements:

  • The workflow is going to be performed by anonymous users. Anonymous users do not sign in to .
  • The anonymous user receives an email that includes a link to the workflow.
  • The workflow must collect a lot of information from the applicant: Contact Information, Education and Employment history, References and more. You can create one long form or design a screenflow with an Anonymous Task step and subsequent steps as separate screens to collect the information.
  • The user must have the option to compete the screenflow in multiple sessions. Clicking on the email link takes the user back to the last step in the screenflow where the Continue button was clicked. 
  • The user must be able to navigate back to previous steps to review or update information that was previously entered.
Flow Designer
  • The Save on Navigate checkbox is checked and the Navigation Toolbar is configured on the Flow Property Panel
  • Step 1 of the screenflow has a field named EmailAddress that collects the applicant's email address.
  • Step 2 is assigned to an email address. This is the first step that is performed by the anonymous user.
  • All remaining steps in the screenflow are designed to collect the applicant's information: Contact Info, Education and Employment history, references etc. Remember, the anonymous user does not login to perform these steps so they cannot have a role, dynamic role or user property assigned to them.

The image shows an example of a possible screenflow design:

Use Mode

Anonymous users return to a previous step by clicking on the Navigation Toolbar if the workflow contains a screenflow performed by an anonymous user.

Deployment

This field is a toggle that sets the state of your flow to production or development. Functionality is the same as Deployment for forms.

Tracking Id

When your flow loads, it will send a page view event to your Google Analytics account if you enter your Google account tracking ID into this flow property. Please refer to Google's documentation for information about finding your Google Analytics tracking ID.

Element Name

By default, this is set to form for newly created forms as well as flows. The root element name of the from-scratch document is determined by what you put in here. It needs to be a valid XML element name. The designer can now change the name of the flow without impacting the element name.

Flow schema and the Submission xml document show the element name. When the flow name is updated, and 'Element Name' is kept the same, the previous submissions can be initialized successfully. When 'Element Name' is updated, previous submissions cannot be initialized.

If you change the element name, all existing submissions will become invalid and you will get the error message: " Error. Submission is not valid. An incompatible change was made to the form/flow."

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  will also generate an entry in the user's task list from where the user can continue working on the flow at a later time.

If you are not authenticated, clicking the Save button will display an authentication dialog that requires you to login. See documentation on using forms for more details.

Users can repeat the save/load steps 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 . And the flow cannot be continued/finished until corrections are made to those fields.

Customizing the Save Button Label for Workflows

The Save button label can be customized for each step in your workflow on the Settings tab of the Edit Step Properties wizard. For example, you can change the button text to Save for Later. This will help clarify the function of the Save/Load feature to your users.

Designers should refer to the Save and Load topic for the details.

Save on Navigate

Imagine you are entering data into a large screenflow and something happens that causes you to navigate away from the workflow... you just lost all your work! Checking the Save on Navigate property saves the task to your Task List.  automatically "bookmarks" your place in the workflow. You can go to your Task List to retrieve the task and be returned to the screen where you were when the browser was closed.

Let's say you have a screenflow with steps A > B> C and the user closes the browser at screen B. When the user performs the task from the Task List, the workflow will open up at step B.

Here is a short synopsis of when the current location is saved. Consider a workflow with the following steps/roles: Role1(A → B → C) → Role2(D) → Role3(E):

  • A user in Role1 starts the workflow on Step A:  does not save because it is the FIRST step (if the user abandons the workflow in the browser it is as if it never existed).
  • The user clicks next:  saves BEFORE step B renders.
  • The user performs Step B and C, then clicks next:  does not save because the workflow will already be saved in the PENDING state due to the new role assignment on Step D.
  • Role2 performs Step D and clicks continue: no need to save here since the workflow is already saved in the PENDING state due to the new role assignment on Step E.
  •  will not save if the step is READONLY - this might be the case if the user navigates back to a previous step that was performed by a different user.
  •  will not save when the workflow navigates from an HTTP/Anonymous Task step to the next one.
  •  will not save when the workflow is completed, because it will already be saved in the SUBMITTED state.

When Save on Navigate is used on a screenflow with sequential steps performed by an anonymous user, it brings the user back to the workflow at the current/latest anonymous step.

Configuring Save on Navigation

Printable

If you check a flow's printable checkbox a Print button will be displayed in Summary steps of the flow. If you don’t want users to print your flow, uncheck the checkbox so users will not see the Print button. You can control which fields are printed by setting up which fields are displayed in the Summary View as described below.

Flows do not currently support a print icon as is available on forms. This will be added in an up coming release. One solution is to add your own print link as discussed in the chapter Printing Forms.

Each step also has a printable property which controls whether or not that step appears in the  PDF document view . See the printable property for workflow steps for full details.

Save PDF

When checked a PDF image of the flow is saved in ' submission repository. See the documentation for the submissions repository for details on viewing the PDFs saved there.

Since flows are a combination of multiple forms or a single form visible in multiple steps or a combination of the two, it is important to understand what controls will be printed when the PDF is generated. See the topic discussing the step printable property. Notice all controls, including those disabled or in a signed section, are no longer grayed out in the PDF.

PDF Name

When you check Save PDF on the flow Property panel, an optional PDF name field displays. It is only visible when the "Save PDF" property is checked and is disabled when the "Save" property is unchecked. If this property is set, then it is used to name the generated PDF. You can use templates to name the PDFs.For example, let's say you have a New Employee On boarding flow and you want the PDF in the submissions to be named using the new employee's  last name. Simply add the name of the control in your flow that collects the last name as a template ex: {LastName} in the PDF Name property. The pdf for each Employee On boarding submission will then be named {LastName}.pdf.

If the PDF Name property is empty, then the form name is used as the pdf name. It is recommended that PDF Names use characters that are suitable for filenames. Following the POSIX filename standard (A–Z a–z 0–9 . _ - ) will ensure it works. 

PDF names can contain special characters with the exception of curly braces {}.

In the submission, the pdf for the Onboarding for new hire Eric Armani is named as shown as shown:

Fast Finish

The Fast Finish feature is very useful when you're filling a lengthy screen flow.  workflows consist of steps (steps) performed by the same person or more than one person. Steps in a workflow performed by the same person are called multipage forms or screen flows. The designer can select the Navigation Toolbar  or add a Summary step as one of the steps to provide an easy way to move forward and backwards through the steps of a  workflow. 

Let's say a user needed to return to a previous workflow step to change entered data. The user clicks the step on the Navigation toolbar or the edit link in a Summary step and the flow returns to the previous step so the user can make the change. In previous versions, once the change is made, the user would have to click through all of the remaining screen flow steps in order to resubmit the flow with the updated data.

The Fast Finish feature provides a finish button, visible in use mode, in addition to the Submit and Save button (if Save/Load  is selected) for the forms in your flow. The Finish button works the same way as the Continue button. The flow will not advance to the next step or be submitted If any of the fields are invalid. 


Selecting Finish automatically advances through the flow steps until one of the terminating conditions listed below is true:  

  1. An step is encountered that is not valid - this could be as simple as a required field that was not filled in.
  2. The next task is assigned to any user/role that is different or the same from the user that selected finish - an example would be the step in the workflow that gets routed to a manager for approval.
  3. The next task is an Anonymous Task or HTTP step type.
  4. The last step is valid and submitted.

You can select the Fast Finish property at the flow level or for the individual steps in the flow. Selecting Fast Finish at the flow level enables it for all steps.

To select Fast Finish for all the steps in your flow:

  1. Edit the flow in the flow designer.
  2. Click the  Edit Flow Properties icon to display the Flow Properties wizard.
  3. Check Fast Finish on the Settings tab.
  4. Click Submit to save.

Selecting it on the individual steps makes the Finish button available on the designated steps only. 

  1. Edit the flow in the flow designer.
  2. Click on the Employee Information step. Click on the  Edit Step Properties icon. Click the General Settings tab.
  3. Check Fast Finish.
  4. Repeat for all the steps in the flow where you want the Finish button to display.  
  5. Save our changes.

If the steps in your flow consist of forms and/or a summary step, Fast Finish forwards through the steps of your flow until it hits one of the terminating conditions listed above.

Let's consider the Employee On Boarding workflow as an example. This workflow consists of a screenflow that is filled in by the new employee:

  • Step 1 is the Employee Information form
  • Step 2 is the Personal Allowances form
  • Step 3 is the Health Insurance Information form
  • Step 4 is the Direct Deposit form
  • Step 5 is a Summary step where the employee can review the data. Clicking on the automatically generated Edit links in the Summary View takes the flow back to that step so the data can be edited.
  • Step 6 is a Confirmation form for the employee to review the W - 4 pdf information,
  • Step 7 is not part of the screen flow - the workflow is routed to the HR department for final processing.

The new employee has filled in steps 1 -  6 but upon viewing the W - 4 pdf realizes that the Additional amount withheld is incorrect. The user clicks on the Personal Allowances step in the Navigation bar to make the correction. If Fast Finish is not selected for the flow, the user must click the Continue button on each remaining step of the flow to submit it with the corrected information.

If Fast Finish, is selected on the flow or step level, the user can click the Finish button after making the correction and the flow will fast forward through Step 6. Fast Finish will stop here since step 7 is assigned to the user Sue who is a member of the Human Resources department. The user will see the pending message after Step 6 and the workflow will be routed to Sue for final processing.

If the Fast Finish and Save/Load features are enabled for a workflow, the user can save a partially completed form to their task list. If the saved form still has required fields that have to be filled in, when the user retrieves the saved task from their task list to complete and submit it, clicking the Fast Finish button takes the user to the point in the screen flow where they left off. 

Fast Finish on Mobile Devices

The Fast Finish button on an iPhone or iPad is accessed via a dynamic action menu that is activated by the right-most button in the top button bar. The action menu drops down below the button and floats above the form. If Fast Finish is not selected for the workflow or on the current step, then the action button and menu are not present at all. 

 

Refer to this feature announcement for more information.

Decorated

Decorated is checked by default when you create a new flow. If  you uncheck Decorated at the flow level, newly added controls in the forms of your flow will not have a decorator. Controls in the forms that already have decorators will retain them. The designer can select a decorator for each of the steps in a flow that will display on the navigation bar.

Force Auth

If this is checked and the  tenant supports SSO (single sign on) such as the LDAP Security Manager enabled tenants, then the  authentication mechanism will be in effect even when a user is already authenticated via SSO.

For example, if you leave force auth unchecked and your form is public in tenant, and you are already authenticated via SSO you will not have to login directly to  to use the form.  If instead you check force auth  will force you to login directly even though you are already authenticated via SSO.

See Working with LDAP and Single Sign On for more details.

This property is currently ineffective for tenants with the default delegating security manager. However the delegating security manager may support SSO in the future.

Show in History

If this checkbox is unchecked, tasks for the form or flow will not appear in Task History searches. If you want them to appear, make sure this box is checked. Checking or Un-checking it affects all tasks including ones that were created prior to the action. 

Accessible

frevvo can be used to build accessible forms/flows that meet Section 508 and WCAG 2.0 accessibility standards. Check the Accessible property to turn on this feature. Refer to the  Accessibility documentation for the details.

This property is checked by default and causes the “powered by frevvo” logo to appear on your flow. Uncheck the checkbox to remove the logo from your flow.

Access Control

Use the Access Control tab to assign workflow permissions to users/roles in your tenant.

You can access the Access Control tab in three ways:

  • Click the  Edit Flow Properties icon on the Flow Designer toolbar. This will launch the Flows Properties wizard. Click the Access Control tab.
  • Click anywhere in the Access Control section in the Properties Navigator. This takes you directly to the Access Control tab.
  • Click the  inside the Messages section in the Properties Navigator. This takes you directly to the Access Control tab.
  • Enter the users and roles for the permissions provided.
  • Clicking on the down arrow(s) show a list of users, roles and templatized fields from your form. Select the users/roles from the dropdown.
    • Type the opening curly brace - {- followed by the control name to enter a field from your form 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.



 Click here to learn more...

Access Control List User Interface

  • users assigned the frevvo.publisher role have the ability to assign/change visibility/ACL permissions. Refer to Access Control List for Publisher Users for a discussion of the UI the Publisher user will see when the Lock icon is clicked.
  • Although designer users also can click theLock icon on the Forms/Flows Home page, we encourage you to use the Form/Flow Properties wizards, explained below, to assign permissions.

Open the Access Control wizard by

  • Editing the form/flow.
  • Clicking the Access Controls section or the cog icon on the Form/Flow designer Properties Navigator when editing a form/flow.
  • Click the Access Control tab.


Form designers as well as users with the publisher role are authorized to configure access control. The Access Control wizard makes the following permissions available for forms/flows:

  • Who can use the form/flow?
  • Who can edit the form/flow?
  • Who can view form/flow submissions?
  • Who can edit form/flow submissions?
  • Who can access the audit trail - available only for flows
  • Who can administer the flow - available only for flows

ACL Permissions for Forms

ACL Permissions for Flows

ACL settings,set by the designer, are retained when you download/upload a form/flow/app to another designer user in the same or different tenant and when you copy a form/flow.

Dynamic ACLs

Templates provide the ability to dynamically determine and restrict access to submissions/ task audit trails when assigning Access Control permissions. Templates are like variables in your form that can be filled in by the user, populated by a business rule or from a back end system.  Any item on the Access Control screens contained in curly braces is a form template and will be replaced with the value of the associated control. For example, the list below contains a fixed role (reviewer) and one dynamic template based role - {AcctMgrRole} :

In the example discussed below, templates are used to navigate the flow to the correct employee in the Accounting department and to define user lists to dynamically control access. 

Important Note on Dynamic Access Controls:

  • Whenever a template is used to determine access control the derived set of users and roles are tied to the submission. They will only change if the submission is edited. Once a user/role is granted permission to a submission dynamically, that cannot be changed by editing the access control configuration in the designer.
  • Dynamic ACLs work per submission when that form/flow is being submitted. If you change ACL permissions they will not take effect for the old submissions automatically as the related ACL record was not created when that particular submission was made. Old submissions must be edited and re-submitted for the changes to take effect.
  • Templates are not allowed for the Who can edit the form/flow permission.

Who can start the form/flow

Setting this permission determines who is allowed to create form/flow submissions. The choices for Form/Flow visibility are: 

  • Anyone(login not required) - anyone can use it even if they are not logged in.
  • Authenticated Users(login required) - the form is usable to anyone who has an account (username/password) and is logged in to your tenant.
  • Designers/Owner Only - the designer user who created the form/flow (owner) can edit, test or use the form. They must be logged into .
  • Custom - The owning designer always has access to the form/flow. Additionally, the designer may configure selected users and/or roles (i.e. users with these roles) to have runtime access to the form/flow.

 Click here for a detailed discussion of the Visibility permission

The  designer can specify the Visibility of a form//flow in two ways:

  1. Clicking the  Lock icon on the Forms Home Page or the Flows Home Page.
  2. Clicking the Access Controls section or the cog icon on the Form/Flow designer Properties Navigator when editing a form/flow.
  3. Click the Access Control tab.

Clicking on the icons or in the Access Control section of the Properties Navigator display the same wizard which can be used to set the Visibility of your form/flow.

When Who can start the form or Who can start the flow is displayed in the Permission field, the designer can select one of the dropdown choices to specify form/flow visibility. The default value for forms is Anyone (login not required) while flows default to Authenticated Users (login required). The choices for form/flow visibility are:

  • Anyone (login not required) - anyone can use it even if they are not logged in.
  • Authenticated Users (login required) - the form is usable to anyone who has an account (username/password) and is logged in to your tenant.
  • Designers/Owner Only - the designer user who created the form/flow (owner) can edit, test or use the form. They must be logged into .
  • Custom - The owning designer always has access to the form/flow. Additionally, the designer may configure selected users and/or roles (i.e. users with these roles) to have runtime access to the form. Use this option to auto-start workflows programmatically.

The Visibility property has been removed from the form/flow properties pane in the designer. You can no longer change form/flow permissions in this manner. When  is embedded in another product such as  Atlassian's Confluence wiki, you do not have access to the icons described above.

The designer can grant form/flow access to explicit users/roles by selecting the Custom choice from the Visibility dropdown. Roles and users can be selected via an editable combo-box control. As the user types,  will try to find any roles and users in the tenant that contain the typed string. Up to 5 matches are displayed below the combo box. Selecting a role/user from the dropdown inserts the selection into the list.

Click Submit or continue with the next option in the Access Control wizard. 

The Expense Report in the above images can be used by anyone in the tenant with the role of Employee, Manager or Accounting, the user id of the Reviewer and the user Sue. Notice the Reviewer role is encased between curly braces. This is an example of a control template. Templates are like variables in your form that will be evaluated at runtime and replaced with the actual values entered. For templates to work, there must be a control in your form with the name given inside the curly braces.

The user, Jack, who has the role of frevvo.Publisher, is not a Reviewer for anyone in the company and of course, is not Sue, will be denied access to the form. He will see this error:

 

You can publish any form/flow regardless of whether it can be started by Anyone (No login required) or just the Designer/Owner. If Designer/Owner Only is selected, the person who created it or any user given the Who can edit the form/flow permission can edit it or test it. It is possible for more than one designer to collaborate on Forms/Flows in development if the form/flow owner (the designer that created the form/flow) gives this permission to other designers. However, if one designer is working on the form, other designers will be denied access. Form/flow owners can also designate the Who can view submissions or Who can edit submissions permissions to other users so two or more people may test the form/flow and view/edit submissions at the same time.

Similarly, if a form visibility is set to Authenticated Users(login required), only users with accounts in the tenant will be able to access the form.

Until you set your form/flow visibility to Anyone (login not required) all other users will see this error message when they try to access the form: " Error Access Denied. Authentication required. Are you trying to access a private form or flow?

A form/flow made public this way is accessible to anyone with the form/flow's URL. There are other methods of sharing forms that have increasingly higher levels of security. See form security for details.

If you set the form/flow visibility to Anyone (login not required) and users have begun submitting it, you'll need to use caution when modifying your form. If users access it while you are editing it, they will see error messages indicating that the page is being refreshed or that the form is invalid.  

You can mark your form/flow Designers/Owner Only until you are done developing it, which will prevent new users from accessing the form, but if users happen to be completing the form when you switch it from Anyone (login not required) to Designers/Owner Only, they will see error messages. A better approach if feasible is to edit the form in a copy of your application running on a staging server. You can then replace the current form with the new form by removing the original application/form/flow from the staging server and uploading the new application/form/flow.

ACL settings,set by the designer, are retained when you download/upload a form/flow/app to another designer user in the same or different tenant and when you copy a form/flow.

The designer can set other permissions, such as who can view/edit submissions for forms and flows via the Access Control wizard. Roles and users that can view the audit trail or be designated as flow administrators are specified through the same wizard.

Public forms that include the save/load feature or digital signatures will prompt the user with the login screen when they click to save or sign. These features require a login.

Who can edit the form/flow

  • Edit permissions should not be given to forms or flows currently in production use. Please see the Admin Best Practices Guide
  • Users with this permission have the ability to run the Refresh Searchable Fields process for the forms/flows they are editing. This process updates existing submissions if changes are made to Searchable Fields.

Form and flow owners (designer users that created the form/flow) can give other users (designers/non-designers) the capability to edit form/flows. This is particularly helpful if a designer user takes a leave of absence or leaves the company. The "backup designer" has the ability to make changes to the form/flow without having to download the form/flow(s) from the owner's account to the backup designer's account. The "backup designer" also can view related submissions by clicking on the Submission or Legacy Submission icons. The ability to edit submissions is granted by a different permission.

Users with or without the role of frevvo.Designer can be assigned the permission to edit forms/flows.

Users given this permission access the shared form/flow from the Shared Items tab even if they have the frevvo.designer role assigned to them. They can only edit the form/flow that was shared with them. They will not have the ability to create new forms/flows from the Shared Items tab. The ability to make changes to a form/flow is not available from Shared Items on the Important Items menu in a  space.

To assign users the ability to edit forms/flows, follow these steps:

  1.  Open the Access Control wizard.
  2. Click the right arrow to expand the Who can edit the form/flow section.
  3. Enter the roles that you want to grant editing capability to in the Roles section. Begin typing the role name then select the role from the dropdown. 
  4. Enter the users that you want to grant editing capability to in the Users section. Begin typing the user id then select the user from the dropdown.

     

    It is not good practice to use Templates for this permission and is not recommended.

  5. Click Submit or go to the next permission section in the Access Control List.

Users that have been granted the editing permission, access forms and flows that have been shared with them via the Shared Items tab on their Home Page. It will not work from the Shared Items selection in a Space or any other embedded scenario.

The Who can edit the form/flow permission does not apply if you are running  with Confluence. Confluence users share form/flow editing by specifying the Forms Editor group on the add-on configuration screen. Users who will be sharing the editing function must be assigned to the specified group.

A browser notification message displays if the user who has been granted permission to edit forms/flows tries to modify their own ACL.  will not allow the "backup designer" to remove themselves from the ACL list.

Who can view submissions

The designer can assign permission to view form/flow submissions to specific roles/users.  Any user with view access can view submissions in read-only mode. Submission deletion is not allowed. Templates can be used to dynamically determine at runtime which users and roles are allowed to view submissions.

To assign permission to view submissions, follow these steps:

  1. Open the Access Control wizard.
  2. Click the right arrow to expand the Who can view submissions section.
  3. Enter the roles you want to grant view access to in the Roles section. Begin typing the role name then select the role from the dropdown. You can enter control names from your form/flow encased in curly braces to act as templates for dynamic access.
  4. Enter the users you want to grant view access to in the Users section. Begin typing the user id then select the user id role from the dropdown. You can enter control names from your form/flow encased in curly braces to act as templates for dynamic access.
  5. Click Submit or go to the next permission section in the Access Control List.

Who can edit submissions

The designer can assign permission to edit form/flow submissions to specific roles/users. Any user with edit access can view, edit and delete submissions in the SUBMITTED, ABORTED or ERROR states. Submissions in the PENDING, SAVED or WAITING states can only be deleted by the tenant admin, flow admin or designer user that created the flow. Refer to the Deleting Submissions for more information.

Templates can be used to dynamically determine at runtime which users and roles are allowed to edit submissions.

To assign permission to edit submissions, follow these steps:

  1. Open the Access Control wizard.
  2. Click the right arrow to expand the Who can edit submissions section.
  3. Enter the roles you want to grant edit access to in the Roles section. Begin typing the role name then select the role from the dropdown. You can enter control names from your form/flow encased in curly braces to act as templates for dynamic access.
  4. Enter the users you want to grant edit access to in the Users section. Begin typing the user id then select the user id role from the dropdown. You can enter control names from your form/flow encased in curly braces to act as templates for dynamic access.
  5. Click Submit or go to the next permission section in the Access Control List. 

Who can access the audit trail - Flows Only

 The audit trail is accessed on a  user's Task List by clicking the View Task History icon. Roles/Users granted this permission will see theView Task History icon on tasks in their task list.

To assign permission to view the audit trail, follow these steps:

  1. Open the Access Control wizard.
  2. Click the right arrow to expand the Who can access the audit trail section.
  3. Enter the roles you want to grant edit access to in the Roles section. Begin typing the role name then select the role from the dropdown. You can enter control names from your form/flow encased in curly braces to act as templates for dynamic access.
  4. Enter the users you want to grant edit access to in the Users section. Begin typing the user id then select the user id role from the dropdown. You can enter control names from your form/flow encased in curly braces to act as templates for dynamic access.
  5. Click Submit or go to the next permission section in the Access Control List.


     
  6. Custom indicates that only users granted explicit access or with one of the specified roles can view the audit trail for the task (provided they have access to the task).  Roles and users can be selected via an editable combo-box control



  7.  Enter the roles you want to grant audit trail access to in the Roles section. Begin typing the role name then select the role from the dropdown. You can enter control names from your flow encased in curly braces to act as templates for dynamic access.
  8. Enter the users you want to grant audit trail access to in the Users section. Begin typing the user id then select the user id from the dropdown. You can enter control names from your flow encased in curly braces to act as templates for dynamic access.
  9. Click Submit or select the next option in the Access Control List.

 

Who can administer the flow - Flows Only

This permission lets a user abort, reassign and reset tasks that are not assigned to them. These administrative tasks are no longer restricted to tenant admins.

The designer can delegate these tasks to additional users/roles by assigning them in the Who can administer the flow section of the Access Control dropdown. Any user/roles listed here will be considered a Flow Administrator.  As such, the Modify Task icon on a task in the task list will be displayed. Tenant admins and designer users get the Modify Task icon by default. 

To assign user/roles as Flow Administrators, follow these steps:

  1. Open the Access Control wizard.
  2. Click the right arrow to expand the Who can administer the flow section.
  3. Enter the roles you want to grant flow admin access to in the Roles section. Begin typing the role name then select the role from the dropdown. You can enter control names from your form/flow encased in curly braces to act as templates for dynamic access.
  4. Enter the users you want to grant flow admin access in the Users section. Begin typing the user id then select the user id role from the dropdown. You can enter control names from your form/flow encased in curly braces to act as templates for dynamic access.
  5. Click Submit to complete the ACL setup
  6. Be sure to save the flow if you were accessing the ACL from inside the Flow Designer.

User jerry has been designated as a flow administrator for the Expense Report but not for the Time Sheet workflow. When Jerry logs into , his task list will appear as shown:

The Modify Task dialog allows a 'flow admin' to execute any one of abort/reassign/reset functions.

When searching for tasks, if a flow is chosen, and the user is a flow admin for it, then all tasks for that flow display. If no flow is selected, then all tasks, even those that the flow admin has not participated in, plus tasks for which the user is a flow admin will display.

Messages

Use the Messages tab to set up the Task Information and the Pending Message for your workflow.

You can access the Messages tab in three ways:

  • Click the  Edit Flow Properties icon on the Flow Designer toolbar. This will launch the Flows Properties wizard. Click 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 the text for the Task Information and Pending Message.
  • Clicking on the down arrow(s) show a list of users, roles and templatized fields from your form. Select the users/roles from the dropdown.
    • Type the opening curly brace - {- followed by the control name to enter a field from your form 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 name that gets displayed in the user's task list. For more details, see the Tasks documentation. 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. You use the Task list to 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.

Set the Task Information on the Flow level if you want it to be the same for all the steps in your flow. If you want differen