76 docs tagged with "Business Process design"

The AutoML Bridge step enables the AutoML model execution with the Bridge Framework.

Bot Tasks contain work to be done by WorkFusion's bots. In a Business Process (BP), the bots complete those steps that are more suited for automation than human labor. Bot Tasks can exist only as a Business Process step.

Composite rules define a Business Process (BP) flow variant, depending on the Record column values.

You must link all Business Process (BP) elements by connections defining the flow of data file Records. The arrow displays the connection direction.

You can add a Manual Task (MT) to a Business Process (BP) using one of the following methods:

When designing a Business Process (BP), you can include another BP in it. This allows you to reuse process designs and improve BP testing, monitoring, and visualization.

OCR Bridge is introduced to improve the following:

A Business Process (BP) is an automation flow combining Manual Tasks, Bot Tasks, Model steps, decision or transformation rules, or nested processes. Work.AI allows you to implement two types of Business Processes (BP):

Designing a Business Process (BP) means creating and configuring a sequence of steps, such as Manual or Bot Tasks, nested processes, or rules, as required to accomplish a business goal.

The guide illustrates the implementation of a schemaless Business Process (BP) for website rating from a Bot Task using the Work.AI Developer and Control Tower capabilities.

Goal

Deploy project to Control Tower

A crucial aspect of installation and further support is implementing an AI Agent (or AI Digital Worker) so that you can change any setting outside of the implementation code without recompiling, updating, or re-deploying your AI Digital Worker. Typically, this is achieved by making your configuration external to the source code.

The custom bot step configuration user interface is used to simplify the specification of configuration parameters for bot steps. The feature enables the creation of complex forms using frameworks like FormIO or React and is supported for Java Native Workers (JNWs), Triggers, Bot Config Bundles (BCBs), and WebHarvest tasks.

A contract defines the input and output of a BP element, such as a bot step, connector, Manual Task, Model step, and so on. Only Business Processes of the schema-based design require setting up contracts.

Using the no-code Generic Connector, you can apply multiple configuration options to handle different connection scenarios and create custom connectors for the integration of external services into your automations.

When you design a Business Process (BP), you can apply rules that affect what path to follow in the BP depending on various conditions. Thus, you can end your BP early if some issue is detected or the data is not enough.

The ODF 2 provides the built-in ORM layer and comes with OrmLite as the default ORM framework used primarily to access Data Store data.

Business Processes (BP) with the same name have a common template, otherwise known as Definition. If you modify the design or parameters in one BP, the modification also affects all other instances with the same definition.

Engine

Operations are templates from which you can create the following:

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.

Before getting into details, let's take a quick look at a simple Bot Task within the ODF 2 framework:

Work.AI offers two types of Business Processes (BP):

After reading this guide, you'll know how to prepare and run a Business Process with a trained model and a Manual Task.

High-level description

After creating an ODF 2 project from the Simple Archetype, deploy it to a Control Tower instance.

Introduction

High-level description

High-level description

High-level description

In the article, the standardized Data Store schema is understood as equivalent to the ODF 2 example project's Data Store schema. With few exceptions, it utilizes concepts from Transaction and Multi-process layers of the ODF 2 architecture. If you do not use the Multi-process layer, you can ignore some entities, and this won't impact the framework integrity. In extreme scenarios, when even the Transaction layer is not used, the Data Store schema should be designed from scratch.

Data flow

The article dwells on the structure of a project created from the ODF 2 Simple Archetype. For more details on creating a new project, see Start Maven project.

What is Assembly?

Maven archetypes are templates enabling to create projects based on a set of core files quickly. The article contains information on the ODF 2 Simple Archetype.

The qualification mechanism is no longer available for access control purposes and is replaced by a new user management approach. However, to support training before employees begin performing actual tasks, WorkFusion provides a special Qualification Business Process (BP), which you can deploy and configure as described below.

Previously, it took a long time to transfer a Business Process with all dependencies. It required multiple operations and manual steps, in-depth model knowledge, Nexus, and s3 credentials.

Download sample project

Design concepts

Control Tower (CT) is the central orchestration application of the Work.AI platform. It enables users to perform the following actions:

With ODF 2, we encourage you to use Data Stores as a universal and effective way to have different steps of Business Processes within your AI Agent exchange data. The section provides a reference on how to organize your Data Model through AI Agent automation.

The guide explains how to add a Manual Task to a Business Process based on ODF 2. When working with Manual Tasks, consider the following aspects:

You don't need to migrate existing BPs from ODF to ODF2 if you haven't faced any ODF limitations impacting BP quality. The Product supports the execution of BPs created on both versions of ODF.

You can create a package with a Business Process (BP) or a task and import it from one WorkFusion environment to another, for example, from DEV to UAT or PROD. Let’s assume the source is a DEV environment and the destination is a UAT environment.

High-level description

Major technical concerns of AI Agent delivery

The instruction describes running, stopping, and scheduling Business Processes based on the ODF 2 example project.

The Orchestration section guides you through the steps to deliver and orchestrate automations, including the involvement of a human worker in the loop. The figure below illustrates the actions available for the purpose via the Control Tower (CT) and WorkSpace (WS) user interfaces.

The article describes an AI Agent Asset Bundle. For details on the structure of an AI Agent Variation Asset Bundle, refer to Package assets into AI Agent Variation Asset Bundle.

The article describes an AI Agent Variation Asset Bundle.

The article describes an AI Agent Asset Bundle. For details on the structure of an AI Agent Variation Asset Bundle, refer to Package assets into AI Agent Variation Asset Bundle.

The article describes an AI Agent Variation Asset Bundle.

Stateless execution definition

To quickstart with Spoke, watch this tutorial video and practice the creation of a basic Spoke test.

There are some useful prepackaged task types not associated with any APIs. You can use them in the standard cross-process flow.

The REST (HTTP) connector is an external connector that listens to incoming HTTP requests and sends records to Control Tower (CT). Optionally, for sync requests only, it can also return transaction results as an HTTP response.

Developer approach to publishing

The ODF 2 example project is created to demonstrate key features of the framework. It contains four simple Business Processes that operate on a mock data model. While functional, these processes do not perform anything practically useful.

The article describes examples and techniques on how to pass data between Business Process (BP) steps, both Manual and Bot ones.

High-level description

Software development life cycle (SDLC) is a process for planning, creating, testing, and deploying an information system. The instruction focuses on a recommended SDLC approach for the Work.AI automation solution implementation.

ODF 2 allows splitting a Transaction into multiple sub-transactions and joining them back. This is usually done to process some data from the original Transaction in parallel.

Split and merge records

If you have several Business Processes (BP) where one BP produces data for another, you can apply the event-based communication mechanism and easily configure data transfer between them. To do it, you can start a sub-process from another BP based on a specific event or initiate transaction processing from another transaction within a different BP.

You can start a Business Process (BP) from a Manual Task. Below are some code samples of how you can perform various operations with it.

To start a Business Process (BP) based on external events or scheduled polling of a source system, you can apply a special no-code Trigger start element when designing your BP.

High-level description

The article is an example of the OCR Bridge step usage in the scope of the ODF 2 framework. The Bot Tasks used in the example are a part of Processing Business Process from the example project.

The Open Development Framework provides several prepackaged components that are ready for drag-n-drop usage.

Before validating a Business Process (BP), make sure the BP meets the following requirements:

Why WorkFusion recommends using version control

To access the list of Business Processes (BP), log in to Control Tower and go to Business Processes > View All.

A commonly encountered task in ODF 2 is waiting for the completion of all transactions in a given Business Process. There is no out-of-the-box solution that fits all use cases. For example, a Monitor Task often serves as the source of transactions, making it impossible to know when new ones appear. However, once all requirements are known, such a feature is quite easy to implement.

To illustrate how user Transactions are created and processed, let's simulate a simple scenario for a Business Process (BP) consisting of two Bot Tasks:

High-level description