Model steps enable integrating and executing machine learning (ML) or AI-based models or model-related operations in a Business Process (BP). You can find available Model steps in Workflow Designer of a Business Process: in the Reusable components panel, navigate to the Bot tab and find the Models category.
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.
Unlike Bot Tasks that are completed automatically, Manual Tasks (MT) require involving a human who is either a cloud worker or an internal employee.
The no-code Data Store steps allow you to easily retrieve or modify data from Data Store tables using an SQL query. The steps send a query to a database, which then processes it and returns the result.
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 no-code OCR step lets you accomplish the following:
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 variables in a schema-based Business Process (BP). 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.
Connect to database
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.
The guide describes two automation use cases leveraging no-code Work.AI features and contract-based data schemas:
To design a form layout for a Manual Task (MT) added to a Business Process (BP), follow the steps below:
For monitoring process metrics, Work.AI offers Superset-based analytics installed together with the Product. To start working with the analytics, you only need to configure access. It does not require any additional third-party licenses and provides the following capabilities:
The article lists operators supported for no-code Transformation and Decision rules steps.
The AutoML menu in Control Tower allows you to perform the following actions without coding:
A dataset is a container for documents and all related meta information as required for model training or testing, 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.
As you train a model in the AutoML interface, you can fine-tune it with additional parameters using the Advanced parameters JSON editor.
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: