-
In the automation history screens, after the “Retry All” button is clicked a waiting dialog is now displayed while records are being fetched, to avoid the user from repeatedly clicking the button and possibly swamping the server.
-
The automation dashboard and the list of automations in the admin console’s “Automations” screen can now be sorted by the most recently edited first. When this sort option is selected, each automation will display its last edit date time.
-
The “automation notes” option in the dashboard’s automation gear menus has been removed. Automation note data has been migrated into automation descriptions instead, which appear underneath automation names in the dashboard.
-
Fixed the Transform Text “truncate” action so it emits output.
-
When importing an assembly or module in the assembly editor, choosing the option to import the item into all tenants no longer results in an error.
-
Fixed an issue with the system’s conversion of JSON to XML where unicode-encoded ampersands were not being properly escaped, resulting in malformed XML.
-
Fixed an issue in the graphical automation history, where drilling into a subroutine within a loop would sometimes not display the data for the selected loop iteration.
-
The admin console’s “automations” screen can now search for automations by ID number.
-
The Transform Data system app now has a “split array” action that splits a large array into smaller subarrays of text strings delimited by specified text. Use the “parse array elements from text” action to parse each subarray text into actual arrays that can be looped.
-
The system now has a mechanism for general-purpose datafile generation from automation data. The initial functionality supports generating daily CSV files. The initial goal is to be able to export automation data and load it into ChatGPT’s Code Interpreter for analysis. For information about creating datafiles, see Datafiles - APIANT
-
Additional caching is done for processing performed by unary protocol thread webhooks, to improve routing performance to the destination automations to be invoked.
-
When searching in automation history where the automation invokes subroutines, the search results are now limited to including subroutine history that was invoked by the topmost parent automation, rather than including subroutine search results where the subroutines may have been invoked by other parent automations.
-
After selecting items in an automation diagram, a new editor right-click menu option “copy items to clipboard” now appears. This can be used to copy the selected items to another automation editor session in another browser tab. In the destination automation, click the “+” destination icon and choose the new “paste from clipboard” menu option to paste the copied contents into the automation. Copy-paste via clipboard - APIANT
-
In the automation editor after clicking the “Create a subroutine” button, if the subroutine’s input or output actions are edited and the “cancel” button is clicked to close the dialogs, the trigger or action is no longer removed from the subroutine’s diagram.
-
The server’s XML parser can now store node text consisting of only spaces.
-
Fixed an issue with forms where if the browser window was resized quickly the form design would not be updated correctly.
-
Dropdown form elements can now be configured to be searchable.
-
When an automation is turned on/off from the dashboard, if a system support person is switched into the account the logged automation history information entry now includes the name of the person who performed the action.
-
When an automation is turned on/off from the Admin Console’s automations screen, the logged automation history information entry now specifies that the action was performed from the admin console. If someone other than the root system admin account is using the admin console, their name is included in the logged message.
-
In the automation editor, the action tile right-click menu option “find items mapped to this” will now correctly find items that contain the item mapped into a key-value action setting control.
-
When saving an automation, the editor will now report invalid field mappings contained in action settings controls that are data-mapped.
-
Fixed an issue where if the last action in an automation was disabled, the automation history data rows screen should show “null” for the date time values.
-
Radio buttons in form designs can now be specified as being the default selection.
-
Fixed a null pointer error in the assembly editor that would occur when saving an assembly that is protected and owned by another account.
-
The admin console’s User Accounts screen now stretches horizontally to make use of available screen width.
-
Form designs now have an option to center the form vertically.
-
Fixed an issue where deploying automations that contain field mappings within action settings (any settings an action has are located above its input fields) resulted in the field mappings within action settings not being correctly mapped.
-
If a connection to a service is aborted and the database contains incomplete information, the Service Credentials - Get module, if configured to report errors, will now report an error that the connection is not found rather than emitting a value of “ACTIVATION_INCOMPLETE”.
-
In the assembly editor, module titles no longer overlap the icons that appear upon mouseover, which would happen for narrow modules especially after they had been loaded with data.
-
Fixed an issue importing or publishing automations where “assembly not found” errors would sometimes be reported if all assemblies in the import did not already exist.
-
Subscription plans can now be configured to display custom menu options under the Account menu at the top right of the automation editor. Custom menu options can either open a URL or execute an automation. If the automation to execute has a form trigger, the form will be opened.