-
Fixed an issue in the Admin Console’s System Settings screen where the lists of production servers, worker servers, retryable errors, and 401 error codes to ignore would duplicate all their content each time the System Settings screen was opened.
-
The “connect an app” hyperlink at the top of the automation editor’s Connections screen is now a button.
-
The Asana API is added to the list of API’s for which to ignore 401 errors, so that automations using Asana won’t be turned off. Asana has been seen returning a 401 even though the credentials remained valid.
-
When Java implementations for modules are being compiled either from the admin console or when the system boots after being upgraded, only automations, batch jobs, and web services for the tenants pending compilation are now blocked from being executed until the tenant’s Java module implementations have finished compilation, rather than all of the system’s automations, batch jobs, and web services being blocked.
-
Added a “remove contact from list” action and “get contact by property” action for CallFire.
-
Added a “remove subscriber from list” action for MailChimp.
-
The Mailchimp “updated subscriber in group”, “updated subscriber”, “new cleaned subscriber”, and “new unsubscriber” triggers have been fixed so they function as expected.
-
The Pipedrive app connection assembly has been fixed so that invalid API Tokens are no longer accepted.
-
The Pipedrive “add new deal”, “add or update a deal”, “add or update a person”, and “add organization” actions can now save custom field values.
-
The Geckoboard app connection assembly has been enhanced so that an invalid API Key is no longer accepted.
-
The Admin Console’s “Automations”, “Batch Jobs”, “Web Services”, “Tenants”, and “User Accounts” screens now show usage information in relation to the system’s licensed limits, if any limits are defined. Usage information can be applicable for the system as a whole or per-tenant, depending on the license configuration.
-
Fixed the automation execution engine so that actions nested within other actions (e.g. actions dragged from the catalog and placed into another action like a subassembly) will now work as expected such that input data is correctly processed.
-
Fixed an issue with server-side assembly execution where sometimes a nested subassembly within a module like a Conditional would receive the literal “xpath: XPATH” value instead of the data value referenced by the xpath.
-
Fixed an issue with the Trigger module that could cause the automation editor to hang when dynamic fields were being parsed if any field name was empty.
-
Added an “evaluate javascript expression” action for the Transform Data system app.
-
The server no longer chunks data sent/received to/from the browser into 64KB chunks, which was previously being done due to a Java limitation on the server.
-
The “max simple db result chunks” setting has been removed from the admin console’s settings screen.
-
The APIANT_MAX_SIMPLE_DB_RESULT_CHUNKS environment variable has been removed the from the baseline docker-compose.yml file.
-
The Wufoo “new form entry (instant)” trigger has been deprecated. A new version of the trigger is now available that uniquely names subfields.
-
All Recurly instant triggers have been fixed so that they can now be configured in the automation editor.
-
The MINDBODY integration has been updated so accounts can be connected to a sandbox.
-
Zoom.us has been integrated with a “create meeting” action.
-
The Alert (via Email) module has been deprecated. Instead, use a Conditional module with a nested Email module.
-
Warning messages related to “flushing two-way sync identifiers” have been removed when disconnecting accounts and saving changes to triggers/actions in the automation editor. The only action that will flush two-way sync identifiers from the system is when the “reset” option is used from an automation’s gear icon in the dashboard.
-
When the automation “reset” option is used from the dashboard, entries are now added to the automation’s history informing that a reset has been performed.
-
The internal API mechanism that some modules use to communicate with the server has been revised.
-
Fixed an issue with the Admin Console’s “System Keyvault” where if someone was signed in with a tenant account they could not add or update keyvault values.
-
The Jotform “new form submission” trigger has been deprecated and replaced with a new version that parses out all available form fields and subfields.
-
The automation execution engine now sends email alerts when triggers report errors.
-
If a webhook automation experiences an error with its trigger, the failed transaction is now retryable from the automation history screen. Previously no “retry” button would appear.
-
When a failed webhook transaction is retried from the automation history screen, all data rows are no longer flagged with the “Success” checkmark if the transaction retry succeeds, instead just the retried action(s) are flagged with the “Success” checkmark.
-
The MINDBODY “add or update client” action has been deprecated and replaced with a new version that offers selectable matching logic for matching existing clients for updates.