-
The subscription settings screen in the automation editor is now searchable by group name, setting name, and value.
-
Automation diagrams can now include rich text notes for documentation. See Documentation notes - APIANT
-
Fixed an issue that prevented subroutines in linked child accounts from being edited and saved, where the system would report the error “Subroutine names must be unique”.
-
The Transform Text “Parse array elements from text” action has been renamed to “Split text into array”.
-
When saving automations in the automation editor, the editor no longer requires that all apps in the automation have a connected account.
-
Code related to browser UI transactions to the server for long-running processing has been refactored so that the polling logic is now unified in a single abstraction layer.
-
Many misc. fixes have been made to the widget editor, which is a currently unused editor in the system.
-
The automation editor’s diagram search functionality now has an option to search for matching action field names. See Search by field names - APIANT
-
Fixed an issue that caused subscription-related information to not be displayed in browser screens when multiple tenants having subscriptions were added to the system.
-
Fixed multiple issues related to running unary protocol threads in tenants.
-
The UI library has been patched so that modal dialogs only display right-click context menus that are defined within the modal dialog. Previously it was possible for right-click context menus to appear for content underneath the modal.
-
Fixed an issue in the automation editor, where after an action with a data-mapped setting that had annotation text entered was saved, when the action was later edited the data-mapped setting would display “null” instead of the data mapping.
-
Form templates are now deleted by right-clicking on them in the catalog and choosing the Delete option, rather than via a trash can icon that would appear upon mouseover.
-
Form templates on a development server can now be published to production servers by right-clicking them in the form templates catalog and choosing the publish option. See Form Templates - APIANT
-
When mapping fields via the diagram in the automation editor, if a search was previously performed the editor now keeps the display of search results visible.
-
When saving changes in the keyvault, the list now remains in its position rather than resetting to the top.
-
Developer-level keyvaults have been removed. The system now has a single keyvault, accessible either from the admin console or from the assembly editor account menu. The Utility - Keyvault Value module no longer has the option to select an “account outside assembly editor”. See API Key Management - APIANT
-
Web service automations now display the execute icon in the dashboard. Clicking it generates a curl command that will invoke the automation for testing, based upon the configuration of query parameters and any POST payload defined in the web service trigger.
-
Fixed the loading of automations shared via the dashboard gear icon’s “Share” menu option, so that an infinite loop no longer happens and the diagram will now load as expected.
-
The form designer now has a JavaScript element that can be used to execute JavaScript when the form loads or when the form is submitted.
-
Forms now have an option (found as a checkbox option on the root-level canvas) to auto-submit themselves when loaded. The main reason for adding this option is to support building form automations where the trigger form can be configure to auto-submit, such that the first form to appear will be an action form such that data processing and dynamic data can be loaded into the first form, since trigger forms cannot show dynamic data other than values passed as query parameters on the form’s URL.
-
The form designer now has a cancel button element, which is only intended for two scenarios. One is when the form is displayed in an iframe, where clicking the button needs to execute JavaScript to communicate to the window parent to close the iframe. The second is when the form is displayed in the automation editor within a dialog window (e.g. during subscription onboarding), where clicking the button closes the dialog window.
-
Image elements in form designs are now always stretched proportionally when their stretch option is checked.
-
The form designer can now load and save form designs that include emoji characters.
-
Numeric values displayed in the stepper UI control are now right-aligned.
-
In the admin console, subscription plans are now copied and pasted via the clipboard, to facilitate copying plans from one server to another (e.g. from a dev server to production).
-
The automation execution work queue now processes automations having a form trigger immediately, bypassing any limit checks for the work queue. This avoids potentially long delays for forms to load if the work queue is busy.
-
Settings for the assembly editor’s code editor are now stored in the system’s database instead of in a browser cookie. The code editor’s settings are now loaded with the account session upon login, allowing the editor’s settings to be the same across multiple browsers. Note that when first using this new release, the code editor will initially use its default values b/c it no longer loads saved values from the browser cookie.
-
The form designer now has a “Check all” checkbox element that toggles all checkboxes in the form.
-
If a unary protocol thread crashes, the system will now auto-restart it.
-
The admin console’s Protocol Threads screen now has a button to view the logs for inactive unary protocol threads, so that if an error occurs when activating the thread any logged errors can be viewed.
-
The form designer now has a back button element, which can be placed in action forms to allow the end user to return to the previously entered form. The previous form will reload and display the previously entered data. Note that the back button cannot be placed in the first form action, b/c the system cannot return back to a form trigger.
-
The HTTP Transaction module and its variants now log the equivalent curl command under the <http_info> section, to aid troubleshooting especially when API providers request an example of an issue with their API.
-
The Fetch Paginated Results - Breadcrumbs module now has a field to optionally enter a base URL to support cases where the API returns relative URLs that don’t include the domain instead of complete URLs.
-
Automation gear menus now have an option to manage suppressed alerts, under Processing → Alert Handling. Alerts become suppressed when suppression links in automation alert emails are clicked. The menu option only appears for automations having at least one suppressed alert. See Alert email options - APIANT
-
The Human Interaction app now has a “Perform app connection workflow” action that can be used in form app automations to have the user connect an app account, same as is done in the automation editor’s Connections screen. See Connecting app accounts - APIANT
-
The System app now has a “Does account have app connection” action that returns true or false depending on if the specified account has a connection to the specified app.