Fall '23 Designer Updates
Combined Form and Workflow Definition
The form and workflow definitions have been combined into one single definition file instead of two separate files.
The save button on either the form or the workflow tab within the designer will save changes made to both your form and workflow. The download button on either the form or the workflow tab within the designer will download both your form and workflow in a single file. If you view the form/workflow in the advanced editor, you will see both form and workflow code.
Existing forms with a separate workflow definition will automatically be combined during the upgrade process.
After the upgrade, if you create a new form the workflow will automatically be created as a part of the form definition.
Embedded Integration Actions
Simplify creating Mirata forms embedded in other systems (i.e. SSAM)
“Backend actions” have been renamed to “Integration Actions”.
Previously there were 3 types of backend action requests:
- Email Notification
- HTTP
- Data Table
Now a new request type, “Embedded Integration Events”, has been added and can now be created in the Admin tool. In the workflow designer you can now select these embedded integration even actions and add them to a transition in the same way that all other actions are added. After it has been added, you will see that action in the “integration action” list for that particular workflow transition. For example, to add a “create form” action for a form embedded in SSAM, simply select the “MDK Form Create” action that was created in the Admin tool and add it to the create transition.
Workflows with existing actions that were hard-coded in the advanced editor do not need to be modified.
Integration Data Mappings
Import mapping files for forms embedded in other systems have been replaced with “Integration Data Mappings”. Form designers will reference data mappings created in the Admin Tool using calculations in the designer.
A new calculation “integration-data” has been added. To set the value of a field with information from another system, select “integration-data” for the initial value of the field. Then select the corresponding data mapping parameter name and add a default if required. For example, to set the Operation Equipment field equal to the Operation Equipment Number from a Work Order in SSAM when the form is created set the initial value equal to the data mapping parameter “Operation Equipment ID” for integration type MDK.
Existing Import Mapping files must be recreated as Integrated Data Mapping records and the associated forms must be updated to utilize the “integration-data” calculation.
Show Outlines Toggle
A new toggle “Show Outline” has been added to the bottom of the form designer next to the “Show Hidden” toggle. Switching this toggle on will outline all fields on the form in a dotted line. Simply switch the toggle off to go back to viewing your form without outlines.
Version Information Displayed in the Designer
The form version is now always visible in the top right corner of the form designer, in line with the grayed-out form name.
When you save the form/workflow, you will be notified of which version you will be publishing. For example, if you are modifying version 2 of the form and click the save you will see the following in the Save Form dialog box: “Are you sure you want to save “Form Name” (version 3)?
Elastic Search in the Designer
When creating a new form, you can now search by form name or form type and any forms whose names or types match your search will appear. You do not have to know the exact form name you’re looking to copy to get the search result.
When adding an integration action to a workflow transition, you can search by action name or type and any action that matches your search will appear. Previously, you could only search by connection type.
Use position in calculation for form updates
When adding a form update to your workflow transition, you can now use the position calculation functionality to update a specific array row on your form.