V7.12 Release 1-7-23

  1. In the admin console’s “Automations” screen, the “active webhook automations” list has been renamed to “active instant trigger automations” and now includes automations having a form submission trigger. The list is also now sorted by the number of invocations rather than by automation number.

  2. In the admin console’s “Automations” screen, the “active automation stats” list now defaults to show the size of automation log files with the list sorted in descending order. A new “sort” option above the list allows the list to be sorted either by log file size or by automation processing time in descending order. Automation log size totals are computed by the system once a day at midnight. Due to how Java functions, log sizes represent the byte size of the logfile content, not the actual file sizes on the server’s filesystem.

  3. In automation execution history, searches for a step number combined with a date range now return expected results rather than zero results. This fix only applied to newly processed data going forward.

  4. Made some notable performance improvements for the Transform Date Time “modify and reformat date time” action, including the caching of computed results for inputs that are fixed datetimes (natural language translations are not cached). When the cache is hit the pre-calculated result can be fetched immediately. Other tweaks have resulted in typical performance of calculations being reduced from 20ms to less than 5ms.

  5. Made some performance optimizations in the way the server builds SQL strings for hot areas such as the keyvalue table and for webhook routing, to eek out more runtime performance.

  6. Fixed the automation editor field mapping UI so that mapped values consisting of a single letter are now rendered.

  7. Centered form lines having a single File Upload button are now centered correctly instead of being left-justified.

  8. When searching in automation history, if the automation was executed by another automation those informational entries will now be included in search results.

  9. Automation history searches now allow simple AND/OR logic, e.g. ‘phrase1 AND phrase2 AND phrase3’, ‘phrase1 OR phrase2 OR phrase3’

  10. The automation editor’s dashboard now supports searching all automation and subroutine implementations for the specified text. Each automation’s XML is searched for the matching text, meaning that assembly UUIDs can be used to find all automations where a certain trigger or action is used. Text with action field mappings is also searchable.

  11. The automation editor’s dashboard has a new sort option “by runtime references” in which child automations invoked by any “execute automation” action and child subroutines invoked by any “execute subroutine” actions are displayed indented under their parents that invoke them. This view is driven by runtime references stored in the database, so if no parent-child executions have taken place then the relationships cannot be shown.

  12. The runtime performance of daily pruning of automation history and logs has been dramatically improved. On the production apiant.com system, the execution of daily pruning has decreased from 4-5 hours to around 15 minutes.

  13. The admin console’s system settings screen now has settings to control the max number of threads used for writing to automation logs and for general-purpose system executor functionality.

  14. The automation editor’s subroutine catalog now displays id numbers next to subroutines.

  15. The automation editor’s subroutine catalog’s top-level categories now display their open/close caret correctly when opened and closed.

  16. In the automation editor under account settings, the setting for alert email delivery has a new option “Never” to suppress all alert emails from all automations.

  17. In the automation editor under account settings, when the setting for alert email delivery is set to “Immediately” the system will now send a single email for all alerts that occurred in the past minute, rather than sending each alert as a separate email.

  18. The System app has two new private triggers, “Alert digest emailed to any account” and “Automation alert in any account”. System integrators with dedicated APIANT systems can use the “Automation alert in any account” trigger in particular to override the system’s handling of automation alerts by configuring all accounts to never receive the default system alert emails and by building an automation to perform desired alert handling.

  19. In any of the automation history drilldown screens, clicking the automation name in the top header now opens the automation editor in a new browser tab/window and edits the automation.

  20. The system HTTP app’s “send an http(s) request” action has been fixed so empty query param and header keys won’t cause an invalid request error. Typically this would happen when configuring the action in the automation editor.

  21. From the “templates” account’s automation editor dashboard, the “Manage” gear menu has a new option “View accounts deployed to” that lists all accounts where the template is installed, as determined by matching the automation name. Name matching is done in order to find templates that were deployed without linking. Clicking an account in the list opens the account’s automation editor dashboard in a new browser tab/window.

  22. The Data Rows - Loop and Data Rows - Conditional Loop modules both have a new checkbox setting in their “Settings” menu to control their behavior when the nested item throws an error. The default matches the current behavior, which is to halt all execution. If the option is disabled, the loop will instead not halt and will continue to iterate through all data rows.

  23. From the topmost automation history screen, when the automation is executing a new “notify when done” button appears that can be used to enter an email that will receive an alert when the current execution finishes processing. The email alert contains a link to view the processing results of the execution.

  24. The Multi-Select List form element now has a “Select All” option. When enabled, a checkbox appears above the list that allows all items in the list to be selected and unselected.

  25. When a form automation has a runtime error, the form viewer now displays the error message.

  26. In the automation editor, when adding a new trigger or action app, if the app has 10 or more triggers or actions to choose from a search entry field now appears at the top of the list to help find items.

  27. In the automation editor, clicking on “execute automation” and “execute subroutine” actions now shows a new menu option to edit the child automation or subroutine. The automation editor will open in a new browser tab/window and load the selected item.

  28. Fixed the server-side implementation of the Data Rows - Sort module so that numeric values having more than 3 decimal places are now correctly sorted.