The Model steps (previously, AutoML Bridge) enable integrating and executing a Machine Learning (ML) model or model-related operations in a Business Process (BP). In addition to the legacy Execute AutoML Model (AutoML Bridge) step, Work.AI offers the following no-code Model steps:
Bot Tasks contain work to be done by WorkFusion's bots automating human labor. Bot Tasks can exist only as a Business Process step, and you can create them using code tools or in a no-code manner.
To add a Manual Task (MT) to a Business Process (BP), use one of the following methods:
The feature is available since Work.AI v10.2.9.2.
The no-code Rate Limiter bot step enables you to control the number of records passing through the step within a specific time frame. This is particularly beneficial for implementing rate-limiting at a granular level, such as per AI Agent, reducing the impact on resources when two AI Agents are running in a single environment.
In Work.AI, the OCR step is available in two variations:
Designing a Business Process (BP) means creating and configuring a sequence of code-based or no-code steps, such as Manual or Bot Tasks, nested processes, or rules, as required to accomplish a business goal.
A contract defines the input and output of a BP element, such as a bot step, connector, Manual Task, Model step, and so on. Contracts allow designing a BP data schema in a no-code manner.
A Decision rules step allows you to configure decision rules and routing outcomes in a no-code manner.
Using the no-code Connector step, you can apply multiple configuration options to handle different connection scenarios and create custom connectors for the integration of external services into your automations.
The Transformation step is a no-code bot step that allows you to implement complex scenarios with rule conditions.
Connectors in the Work.AI platform enable Business Processes (BPs) and AI Agents to communicate with external systems. They provide standardized integration points for retrieving and enriching data, sending information to third-party services, triggering workflows based on external events, and orchestrating end-to-end automation across enterprise environments.
Templates are intended to simplify document ingestion by enabling automated information extraction from structured forms (for instance, ACORD). When a template is created, blank forms are annotated with labels. Based on these labels, data is then extracted from input documents.
This guide gives you a quick introduction to custom dashboards: how to create datasets and charts and organize them into a dashboard. Since WorkFusion Analytics is originally based on Superset, you can refer to the Superset official documentation for additional details.
The guide describes two automation use cases leveraging no-code Work.AI features and contract-based data schemas:
The Task Designer Operation is the recommended method to design Manual Tasks (MT). It provides a no-code way to implement Manual Task forms: to generate them from template or other models or to build them manually in a drag-and-drop editor.
The article lists operators supported for no-code Transformation and Decision rules steps.
A dataset is a container for documents and all related meta information, such as:
To access a list of available Machine Learning (ML) models, select AutoML > Models. Control Tower updates the list every time a new model is deployed to your environment or you complete a training run.
To access a list of available pipelines (artifacts), select AutoML > Pipelines. Control Tower updates the list every time a new pipeline is deployed to your environment.
To access the lists of training and test runs and explore their details, select AutoML > Experiments. Control Tower updates the lists every time you start a training or a test accordingly.
If you have several Business Processes (BP) where one BP produces data for another, you can apply the event-based communication mechanism and configure the data transfer between them. You can set a sub-process to start from another BP based on a specific event or set transaction processing to be launched from another transaction in a different BP using no-code sub-process steps.
To start a Business Process (BP) based on external events or scheduled polling of a source system, you can apply the no-code Trigger element.
The article illustrates how you can set up normalizers via AutoML UI to achieve a better-quality model output for a dataset.
The article is a tutorial on how to create an end-to-end Business Process (BP) for information extraction (IE), comprising the following steps: