Although they work exactly the same, we now call them “Integration Actions” instead of “Backend Actions”. You’ll see this nomenclature change across the Admin Tool and Designer.
You no longer have to upload/download forms and workflows separately or worry about making sure your form is tied to the right workflow version because form and workflow are now combined into one definition.
We added two new integration action types:
We created a new type of Integration Action called Embedded Integration Events to drastically simplify creating Mirata forms that can be embedded in other systems (such as SAP Asset Manager, Fiori, ESRI, etc.)
Use this type of action to delete form submissions in the Inbox. This can be useful when you want to batch delete a set of submissions.
See the Scheduled Jobs section for how you can now automatically run integration actions, such as submission delete requests, on set cadence(s).
We replaced the JSON Mappings files with a new concept: Integration Data Mappings
In the Admin Tool, you can now set up integration actions to automatically run on a scheduled cadence
Go to the new Scheduled Jobs knowledge article for more details on how to set up your first Scheduled Job
You can now view change history for Data Tables, Data Table Records, and Integration Actions in the Admin Tool. Go to the new HISTORY tab to view a log of when updates were made and by who.For each change, you can view the Change Type, Updated At, Updated By, and other relevant metadata.
This history tab will be coming to more places in the Admin Tool soon!
Both data table and submission queries now include not equals, not exists, not contains, and not begins expressions.
Quickly filter and search Integration Actions and Images