Workflow Settings

Use this field to change your Workflow's title. It's important to note that the Workflow Path doesn't adjust automatically when you change the Workflow Title. When changing the Workflow Title, ensure it's unique to avoid issues with your other environment Workflows.

A value in the Workflow Title field is required to save changes.

Use this field to change your Workflow's path. Adjust the Workflow Path as you see fit, but ensure it's unique to avoid issues with your other environment Workflows.

To the right of the field, there's an option to copy your Workflow Path. Click Copy to copy the workflow path value to your clipboard.

A value in the Workflow Path is required to save changes.

State Control is how your end-user interacts with your workflow. It gives you the option to restrict or give freedom to end-user navigation. Regardless of your option, Next and Previous buttons display in Express View Express View is how your end-user views your application. Express View also lets you preview your applications to test your configuration and view the styling. This is also the view your end-users will see when interacting with your application. After configuring a module, click Preview in the Module Builder to interact with the module in Express View.. End-users can use these buttons to move to the next task, or a previous one.

The State Control setting contains the following options:

• Auto State Control: This setting restricts your end-user from skipping tasks. They must complete their tasks in sequential order. This setting is selected by default.

• Manual State Control: This setting gives your end-user more navigational freedom. If end-users have access to a task, they are free to jump to it at any time. They can also navigate to non-sequential tasks.

This setting controls how the end-user navigates the tasks of your workflow. An end-user can navigate freely without using the Next and Previous buttons, or any other navigation buttons.

This setting is available only when Auto State Control is selected.

Sequential Navigation Control contains the following setting:

• Make Sequential Navigation Clickable: When selected, this setting lets end-users navigate to the previous task in your workflow. They can also navigate to a previous task by clicking on the page's Navigation Display. They aren't required to use the Previous button to move around tasks.

By default, this checkbox is clear.

This setting determines the completion path your end-user must follow in Express View. You can choose to display progress as steps or use a progress bar.

• Steps: This setting displays end-user progress using a progress bar consisting of steps. This setting is selected by default.

• Percentage: This setting displays end-user progress using a percentage-based progress bar.

When your end-user saves an invalid entry, an error message displays. Use this field to create a title for that error message.

By default, the Error Title displays as: Oops - {{ errors }} error(s) have been found! In this case, {{ errors }} represents the count of errors returned.

When your end-user saves an invalid entry, they'll see an error message. Use this field to create a specific error message.

By default, the message reads as: Please fix the fields outlined in red.

This field lets you set the button label text for the cancel button. This button displays in a pop-up when your end-user receives error validation. Or, it displays in a pop-up after clicking the Save and Exit button. On button-click, your end-user's updates clear.

By default, this button label text displays as Cancel.

This field lets you set the button label for the confirmation button. This button displays in a pop-up when your end-user receives error validation. Or, it displays in a pop-up after clicking the Save and Exit button.

By default, this button label text displays as OK.

Use this field to create a message that displays in a pop-up modal when an end-user navigates to a task where they don't have access. Your end-user sees this pop-up when they click the Next  button.

Use this field to create a message that displays after your end-user submits their final task.

This setting lets you add a Save and Exit button to your workflow. When this toggle is set to  (ON), the button displays at the bottom of each page in Express View. This button lets your end-user save and exit individual tasks. You can also configure the button to trigger a hand-off and send your end-user to another page.

By default, this toggle is set to (OFF).

Use this field to create a label for your Save and Exit button. This button displays at the bottom of your page in Express View.

By default, the button label text displays as Save and Exit.

Use this field to create a message that displays in a pop-up modal when your end-user clicks the Save and Exit button. Interactive Cancel and Confirmation buttons also display in the modal.

If left empty, no pop-up modal displays on button-click.

This setting lets you display navigation in vertical order. When set to  (ON), your Navigation Display is a table of contents on the left side of your page.

Which tasks end-users can select depends on selections made to State Control settings.

By default, this toggle is set to (OFF).

Non-persistent data refers to data that doesn't save to the Unqork database. Most components have Data Storage option that lets your automated tasks access and use unsaved data. When set to  (ON), your application won't be bloated with large amounts of saved information.

To store a field's data to the Unqork database, set the Store Data in Database toggle to  (ON). You can find this toggle in many of the components' configuration windows. Keep in mind, the Store Data in Database setting affects how data persists through your application.

By default, this toggle is set to (OFF).

This setting controls what data stores on the end-user's side when navigating between workflow pages. By default, data from all fields store on the end-user's side when navigating between pages. But, you might want the end-user's submission to keep persistent data on navigation. Or, in other words, to only hold on to data that ultimately stores in the database on submission. In this case, set the Only Keep Persisted Data Upon Navigation toggle to  (ON).

By default, this toggle is set to (OFF).

This setting lets you use language translations in your workflow. When set to  (ON), translatable elements in your workflow auto-populate in the Workflow Builder's Translate table.

To learn more about Workflow Translations, view our Workflow Builder Translate Sidebar Option article.

By default, this toggle is set to (OFF).