-
Added a new “test data” trigger to the System app. The trigger lets you define multiple output fields and values, for the purpose of building test automations. The trigger always fires, emitting a single data row with the defined fields and values.
-
The system has a new “Public content” permission that is now needed for accounts to be able to choose to save content in public scope.
-
The system has a new “Share content” permission that is now needed for accounts to be able to share private content with other accounts.
-
Fixed the dashboard for the special “templates” account so templates can now be switched to be private or public.
-
The dashboard for the special “templates” account no longer displays the Schedule or Stats columns, since this account cannot operate automations.
-
Fixed the dashboard for the special “templates” account so templates are ordered with public templates listed first.
-
When signing into the automation editor, after sign-in the dashboard now refreshes itself.
-
Fixed automation notes so that any existing notes will appear when notes are edited.
-
Fixed the automation execution engine so that if the “execute automation” or “execute subroutine” System actions result in the child automation/subroutine encountering a retryable error, only the parent automation performs the retry logic instead of the child automation/subroutine also being retried which would lead to duplicate processing.
-
When searching in the top-level automation history, the count of total matching executions at the bottom of the screen is now updated correctly.
-
When displaying API errors in the 2nd-level automation history drilldown, the system now replaces tags in the API error text to avoid circumstances where certain API error responses with HTML and CSS would cause side effects in the UI, especially where the ACE code editor would not be sized correctly when viewing data in the graphical automation history.
-
Made a change to the OAuth refresh token logic so that if a mutex lock cannot be obtained the logic will now throw an error instead of continuing ahead with the token refresh. This is to avoid the potential for multiple threads performing oauth token refreshes at the same time, which could lead to the wrong refresh token being stored in the database which would then cause future token refreshes to fail.
-
Fixed an issue that could cause the 3rd-party ACE editor to not appear. This editor is used throughout the UI, mostly when viewing automation and assembly data.
-
In the automation editor’s Connection screen, after clicking the “Connect App” button the catalog that opens now loads much faster.
-
In the assembly editor, the “Open Assembly Editor Guide” menu option under the Developer menu has been removed. The “Tips” menu at the main screen’s top right has been replaced with a “Learn” option that opens assembly editor help information from https://info.apiant.com/assembly-editor.
-
In the assembly editor’s Developer menu, the “open webhooks log” and “purge webhooks log” options are now only visible if the system is a development server or if the signed-in account has the “Admin Console” permission.
-
In the assembly editor’s Developer menu, the “open admin console” option is now only visible if the signed-in account has the “Admin Console” permission.
-
Put in a possible workaround for a rare and unreproducible issue with the 3rd-party VTD-XML parser that may only occur when free memory is low, or is perhaps a concurrency issue with the library.
-
In the assembly editor’s File menu, the “Keep for Later” option has been moved up and a separator line has been added between it and the Save menu option, to make the Save menu option easier to access.
-
In the assembly editor’s File menu, the “Keep for Later” option is now only available for previously saved assemblies that have unsaved edits.
-
After switching accounts in the assembly editor, a message is now displayed explaining that credentials for the switched account are only used for newly opened assembly tabs.
-
In the assembly editor’s Developer menu, the “open system webhooks log” option now opens the log in a dialog window rather than opening a new browser tab. The webhook log contents are now displayed with the most recently received webhooks at the top, making it easier to refresh the log and watch for webhooks of interest.
-
In the admin console’s “Webhooks” screen, added a button to open the system’s webhooks log.
-
On development systems, the automation editor’s dashboard gear icon “get linked template info” menu option now searches all configured production systems for linked templates, not just the first production system listed in the dev system’s configuration settings.
-
Added a “Data Nodes - Rename Name-Value Pairs” module that reformats name-value pair child nodes in the data stream and transforms them to facilitate processing. This is especially useful when using an Action in the catalog as a nested module within an assembly and the action’s output needs further processing.