V7.08 Upgrade 8-27-22

  1. It is now possible to build “form apps”, where an automation can use multiple forms and the form viewer will display them, along with optional waiting messages if the automation needs to perform long-running processing in between forms. Use the existing Human Interaction “await form submission” trigger and “create a form” and “await form submission” actions. In the form design, enter ‘next’ as the form submission message to indicate that another form will be subsequently displayed. Optionally use the new “display form waiting message” Human Interaction action to display a popup waiting message along with a spinning animation icon if the automation needs to perform long-running processing between forms. This action can be used multiple times if needed to show progress. For more info, see Form Apps - APIANT

  2. In the assembly editor, the Stream Inspector’s “compare input vs. output” functionality is now limited to XML data that is less than 50KB in size, to avoid performance issues and possibly exhausting the server’s memory.

  3. In the assembly editor, the Stream Inspector’s “compare input vs. output” results can now be scrolled.

  4. Fixed an issue when using the “retry all” button in the top-level automation history view where nothing would be processed if a search query was entered, even though the screen would show errored transactions.

  5. The list of inactive automations at the bottom of the admin console’s “automations” screen has been removed.

  6. In the admin console, anywhere an automation id number is displayed they are now links that can be clicked to open the account’s dashboard in a new browser tab/window with the dashboard filtered to only show that automation.

  7. In the admin console’s work queue screen, mousing over the list of automations being processed will now pause the refreshing of the list. Mouse out of the list to restart its automatic refreshes.

  8. The automation builder will no longer allow a subroutine to be saved if it doesn’t contain a Subassembly Output action.

  9. The help documentation that appears when the “Learn” links at the top right of screens are clicked now sits side-by-side with the application screen, rather than overlaying it. This allows the app to be used normally while also being able to read help documentation.

  10. The System app’s “execute automation” and “wait for latched automations” actions have been fixed so the system’s jspTimeoutSeconds setting won’t time out the actions (for the “execute automation” action, if the “wait to complete” setting is checked).

  11. Slack actions and triggers have been refreshed so they work with their latest API changes.

  12. The system can now be optionally configured to load balance work to a cluster of worker servers per tenant id. The default load balancing is per account id, which does not take tenants into consideration.

  13. Forms can be pre-populated with input data via URL query parameters whose names match UI element names in the form’s design. This works for both standalone and embedded forms. For action forms, any URL query parameters will override field mappings.

  14. Form elements can be hidden via URL query parameters. Use a query parameter of “elementname_visible=false” where ‘elementname’ is the name of the UI element in the form design.

  15. Dropdown UI elements in forms can now have an array of values mapped as input to use as the list of choices to display in the dropdown’s pick list.

  16. If a webhook automation has a transaction being retried, subsequent webhooks will remain queued until the transaction is no longer being retried. This change was made in order to avoid possibly swamping the server if a large number of webhooks are being received for a single automation and a retryable error like an API rate limit causes all of the received transactions to be retried.

  17. Subscription plans now support a monthly form submissions limit that works the same as the monthly task limit. Includes System app webhook triggers when form submissions reach 75%, 90%, and 100% of the monthly limit.

  18. Added a “rating stars” form element.

  19. Added a “file upload” form element. The form emits the URL to the uploaded file. Uploaded files remain on the server in temp storage for 24 hours.

  20. Fixed a null pointer exception that would occur in the Row Builder module when a configured data path did not match any data in the input XML when running on the server.

  21. Fixed the browser-side implementation of the Data Rows - Sort module so it correctly sorts when data values contain numbers even though the value isn’t a valid number. The server-side implementation was not affected by the same data values.

  22. Automations having a Human Interaction “new form submission (instant)” trigger now have dashboard gear menu options under the Manage section to obtain the form’s URL and its embed code.

  23. Text entry fields within forms can now have prompt text specified. Prompt text appears within the edit field until typing begins. It is an alternative to using label text that appears above the fields.

  24. Text entry fields within forms can now have their height and font size specified. Multiline text entry fields can now have their font size specified.

  25. When mapping action fields, if a search is performed now only actions and trigger that contain matching fields remain visible.

  26. New options appear above the form designer at its top right to copy and paste entire form designs. Although form designs get copied when “create a form” actions are copied, this new copy/paste functionality can be used to copy form designs from a form trigger to a form action.

  27. Elements and containers within forms can now be cloned. On Mac, hold the Option key while initiating a drag. On Windows, hold the Control key.

  28. When mapping action fields, the list of actions is now sorted in reverse, such that the immediately preceding action is at the top of the list.

  29. The “automation break loop” icon has been changed from a hand to a stop sign.

  30. In the automation builder, clicking on the text underneath triggers and actions will now let the item be renamed.

  31. In action configuration settings, text entry and scrolled text entry settings are now defaulted to always be data-mapped and the “data map?” checkbox no longer appears for these settings.

  32. In action configuration settings, multi-input and key-value settings are now data-mappable.

  33. Form elements now have a “y offset” setting to control their vertical positioning.

  34. When a form element is selected, pressing the Delete key will delete the element. Pressing the up arrow key will select the item’s parent container.

  35. The automation editor’s subroutine catalog now displays the “Mine” catalog as the first tab.

  36. The Transform Text app has a new “emit first non-empty value” action.

  37. The URL system app has been renamed to HTTP and its actions and trigger have been deprecated and replaced with an improved action and trigger.