A pre-release of the upcoming v6.39 release has been installed in dev.apiant and apiant.com for live testing:
-
The performance of the appRPC handleReceivedUnaryProtocolPayload() method, used by Unary Protocol Threads to invoke automations, has been greatly improved by optimizing a SQL query to utilize an existing index.
-
When dragging items in the assembly editor, if a modal opens the drag is now halted. Previously the dragging would not stop, making it impossible to click in the modal.
-
The automation name entry field at the top of the automation builder screen is now limited to 100 characters.
-
The Transform Date Time “modify and reformat date time” action now supports a timezone offset value of “ACCOUNT_UTC”, which converts inputs in the account’s timezone to GMT.
-
When an action in an automation is configured to “continue if error”, an error is no longer written into the automation’s task history log.
-
Automation names in the automation editor’s dashboard are now fixed width, to avoid the screen jumping around as polling countdown timers are updated.
-
Fixed a null pointer exception that would occur in the server runtime for the Trigger Two-Way Sync module.
-
When sharing items in the assembly editor, the share settings dialog now has a checkbox to show only accounts the item is currently shared with.
-
Accounts having the “Automation Templates” permission now see template annotation entry fields underneath all trigger and action settings when editing automations in the automation editor. These annotations will appear when template automations are initially configured by end users who install the templates and turn them on for the first time. The annotation text can contain HTML markup, for embedding links/images/videos/etc.
-
The search entry field in the automation editor’s dashboard now requires pressing ENTER to search. An onscreen prompt indicates this. A “Waiting…” spinner now appears when searching, b/c searching in dashboards with lots of automations can take a few seconds to complete.
-
When saving automations in the automation editor, a “Validating…” spinner now appears briefly as the system validates the automation’s field mappings. This can take a few seconds for automations with lots of actions and fields.
-
Added a “Conditional Execution” module that is a hybrid of the existing [Single Value] and [Data Stream] variations. This module allows two scalar values to be tested, while allowing the nested item to emit either a scalar value or a data stream. It fills a gap where the existing [Single Value] module cannot emit a data stream and the existing [Data Stream] module cannot easily test two scalar values without having to place the left side value into a data stream first. An expected common usage scenario is to conditionally execute the nested item based on the output from the When In module.
-
The “Get dynamic action output fields” subassembly has been deprecated and replaced with module “Action - Extract Output Data Fields” that provides equivalent functionality but with maximum runtime performance by using native Java on the server.
-
The “Show only required fields” and “Show only mapped fields” checkbox functionality in the automation editor’s action settings has been optimized so it completes faster by minimizing rendering of the fields as they are hidden or shown.
-
Internal changes have been made to help reduce the system’s database storage for automation history going forward. Existing data already stored in the database is not modified.
-
In the automation editor, when clicking on action data fields the popover of mappable data fields now renders the popover immediately and then renders the list of fields separately, so that the popover can appear as soon as a field is clicked rather than being delayed to wait for all fields to render first.
-
Text entry field borders no longer initialize to black and then quickly transition to gray. Instead, they initialize to gray.
-
Action parameters can now be optionally data-mapped. When editing an action in the automation editor, data-mappable parameters will have a “Data map?” checkbox next to them. When checked, the parameter value can be mapped to a field or hardcoded by hand. The data-mapped value can either be the item’s name or the item’s id. In the case of populated dropdowns, the action will fetch all the values of the dropdown when the automation runs and compare the contents to the data-mapped value. The first item with a name or id matching the data-mapped value will be used. Data-mapped parameters are not currently available for actions that have dynamic input fields or dynamic output fields. When a template is installed and configured, any data-mapped parameters are not shown in the initial configuration dialog when the installed template is first turned on.