-
The system now limits auto-restarts of unary protocol threads to 5 attempts, in order to avoid filling up the filesystem with files used to execute the thread. After 5 attempts, the system will deactivate the unary protocol thread and trigger a fatal error which in turn alerts the system admin.
-
The curl command added to HTTP Transaction module output in the previous system release now includes any payload that was sent via POST or PATCH.
-
Form designs can now specify that an account is required before the form will appear and can be submitted. The form will first check to see if the user is already signed in, by looking for a browser cookie. If the user is not signed in, they will be prompted to either sign in or to create a new account. The form will not appear until the user either signs in successfully or until a new account is created. Forms that require an account will emit “tenant uuid” and “person uuid” fields, so that the user’s account can be fetched via a System action to retrieve account information.
-
Fixed an issue so that rich text notes in the automation builder now appear within array iterators and conditions.
-
ActiveMQ has been removed from the system, as Hazelcast has reliably been used for message queues for many years and has proven to be more robust than ActiveMQ. ActiveMQ in particular exhibited memory leaks.
-
When an app assembly is renamed, any references to the app in subscription plan lists of “allowed apps” are now updated with the new name.
-
Fixed an issue with the DateTime - Translation module (used in the Transform Data “modify and reformat date time” action) where certain conversions would fail to produce correct results.
-
When moving items above or below conditionals in the automation editor via up/down icon arrows, the “select destination” dialog that prompts where to move the item(s) relative to the conditional (above/below the conditional, true or false branch) now has an “X” close icon at its top right that can be used to cancel the move.
-
When deploying automations having a webhook instant trigger, if the trigger needs no manual sending of a webhook and if the trigger has no configuration settings, the system will now automatically run the trigger assembly to generate the webhook URL such that manual configuration is no longer required in order to turn on the deployed automation.
-
Fixed an issue with system imports of assembly modules where referenced content such as JSP scripts where not being loaded unless the module’s last modified datetime was newer.
-
Fixed an issue with the automation editor where mapped action fields would not appear in destination automations after deployments.
-
When clicking the “eye” icon in automation editor mapped action fields, the list of fields that opens will now correctly display the mapped field if the field’s name has underscores, rather than an empty popover being displayed.
-
A new catalog tree icon now appears in automation editor mapped action fields. Clicking it will make the automation’s diagram appear with the mapped item scrolled into view and highlighted. Previously this functionality was accessed by double-clicking the eye icon.
-
The system can now be configured with an OpenAI API key. When provided, an AI Agent becomes available to assist with action field mappings in the automation editor. See AI field mapping assistant - APIANT
-
The list of folders in the automation editor’s dashboard now displays correct counts of automations in each folder by not including deleted automations in the counts.
-
Fixed a Java runtime error that could occur in the “Save multiple mapped values for mapped key” Lookup Tables action.