-
When executing an assembly in the assembly editor that performs OAuth via the OAuth v2.0 Workflow module, if the signed-in account has “Assembly Developer” and “Switch Account” permissions the system will now log debug information into the developer trace log, accessible via the Developer menu at the top right of the assembly editor. The required permissions for this are imposed so that the account must be considered to be at a higher level of trust, b/c the logged information will include sensitive information such as the OAuth client ID and secret.
-
Fixed an issue with the system’s comparison logic of numbers such that values containing letters like “0054x000005F5peAAC” are no longer parsed as a number value of “54” but rather evaluated as a string value.
-
The system no longer writes automation alert mapping replacement logic trace information into automation logs. Instead, the information is now written into Lucene, where it can be accessed via the “eye” icon in execution entry tiles within the top level automation history screen. This is done b/c the information is only needed when troubleshooting alert message replacements. Also, it is confusing to see information about messages that pertain to other apps beyond the ones that are executed by the automation.
-
The recently introduced Alert Mapping functionality can now be used to suppress email alerts by not entering any replacement text. The alert will still be logged and other related error handling processing is still performed, but if the alert replacement text is empty the system will not send any alert email.
-
When creating new accounts in the Admin Console, if the email already exists an error message is now displayed.
-
When editing automations, if a search is performed and highlighted actions are disabled/enabled, the action text is now updated to reflect the change.
-
If the Human Interaction app’s “Get moderation queue request link” action’s description field starts with “http://” or “https://” the URL will be displayed when the item is moderated.
-
When publishing content from a development server to a production server, Unicode characters within the content are now preserved. This mainly seemed to affect automation and assembly names.
-
In the assembly editor, when searching for text within module fields subassemblies and nested modules now highlight matching fields.
-
The automation editor dashboard gear icon menus have a new Properties option for viewing the date and time the automation was created and last edited.
-
Within automation history, looped subroutines can now drill into specified loop iterations when clicked. Only works for newly processed data going forward.
-
Fixed an issue that would cause data fields to not be listed in the automation editor. The issue was caused by database data being stored into the anonymous account having person id = 0 when automations were imported or published into a production system from a development system.
-
Fixed an issue that would cause duplicate database records for dynamic trigger and action fields when automations were imported or published into a production system from a development system.
-
In the automation editor, when using the “find items mapped to this” functionality for triggers, if a highlighted action’s field mappings are edited to remove all mapped fields to the trigger the action is now unhighlighted after the change is saved.
-
In the automation editor’s graphical history view, clicking on an “execute subroutine” action that was not executed will now show the action’s settings, rather than an error message.
-
The baseline MySQL integration now supports table names containing dashes.
-
Fixed the Math Sum Subnode Values module so that when its “passthru input data streams” setting is unchecked the summation value is saved.
-
The search query at the top of the automation dashboard screen has a new option to search for a value within the task history of all automations. If automations are found with task history containing a matching value, a dialog opens listing all matching automations. Clicking on an automation in the list opens the automation’s task history with that value searched upon. Returning to the dashboard automatically re-opens the list of matching automations, so that multiple automations can be inspected. Use the “cancel” button to cancel the search, so the dialog will no longer appear when the dashboard is opened.
-
The automation gear icon menu has a new “Show folder” option that will display the name of the folder the automation is in.
-
Fixed an issue that could cause duplicate info to be saved in the database for dynamic trigger and action input/output fields. The duplicate info in the database was harmless, but consumed storage space.
-
Automation editor settings related to “halt automation on any alert” have been renamed to “turn off automation on any alert” which better describes what the setting does.
-
In the Admin Console’s manage account dialog, a new option has been added to forcibly sign out an account.