The Tuple Store lets you store data directly within Hero_Flow without the need for an external data base.
Create new tables (schemas) and write tuples into them or upload CSV files and let Hero_Flow create a new tuple set from those uploaded files.
Merge Flow Branches
It is now possible to /wiki/spaces/AH/pages/1179699. This allows automation designers to use similar data from different data sources within the same automation Flow.
- Detect output fields - Adds string fields to the output arguments if they do not already exist.
New Function: MicrosoftGraph Lookup
The MicrosoftGraph Lookup function retrieves email message data with an email id using the Microsoft Graph API.
Custom Docker Containers
Control CPU Usage of Docker Containers
Automation designers and system administrators can fine-tune the CPU consumption used by a given containerized function when a Flow executes.
This new feature is particularly helpful to prevent resource starvation between Flows when multiple automations with containerized functions are running. The feature also provides predictability on automation run time.
Generate Multiple Output Tuples from a Single Input Tuple
This capability further expands the possibilities for containerized functions by allowing developers of containerized functions to generate multiple tuples from a single tuple input.
This is particularly helpful for document review use cases in which multiple types of documents are bundled in a single PDF file.
Resize Hero_Flow Dialog Windows
Automation designers can now resize any dialog in the Hero_Flow platform.
Automation designers can now use the new Table component to populate tables in task details pages.
This feature is particularly useful for invoice review as well as document review use cases in which data extracted from tables can be validated and curated.
Robin end users can edit existing values or add or remove records.
Adjust the Text Area Size
The Text Area component can now be configured to have any default size when presented to Robin end users.
After loading the Task Details page, the Robin end user can see (and still resize) the intended content per automation designer specifications.