80 docs tagged with "Business Process design"

Description

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.

A Business Process (BP) is an automation flow combining Manual Tasks, Bot Tasks, Model steps, decision or transformation rules, or nested processes.

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 information in the article relates to the low-code approach of creating AI Agents using IA Cloud Developer.

Business Requirements Document (BRD) is a document to record the functional, quality, and usability requirements in formats easily consumable for future analysis, architectural and design activities, and, most importantly, in a format understandable by all business stakeholders.

Goal

Deploy project to Control Tower

A crucial aspect of installation and further support is implementing a Use Case so that you can change any setting outside of the implementation code without recompiling, updating, or re-deploying your Use Case. 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.

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.

OCR Bridge is introduced to improve:

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.

What is Open Development Framework

Operations are templates from which you can create the following:

Templates provide a way to reuse objects. Almost every object within IA Cloud Enterprise, including Manual Tasks and Business Processes, is based on templates.

Before getting into the details, let's take a quick overview how a simple Bot Task looks like in terms of the ODF 2 framework:

There are two ways to initiate the BP creation flow:

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

Checklists are helpful as quality control techniques for documenting requirements. They can include a standard set of quality elements to capture the requirements. The purpose of a checklist is to ensure that items defined by the organization or the project team are essential and included in the final requirements or that issues determined by the project team are addressed.

High-level description

After creating an ODF 2 project from the Full 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 Full Archetype’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

What is assembly?

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

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

The qualification mechanism is no longer available for access control purposes. It is replaced with a new user management approach.

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

Business analysis is a disciplined approach to introduce and manage changes for organizations, whether for-profit businesses, governments, or non-profits. Business analysis is done to define solutions that will maximize the value delivered to the business and lead the business through the unknown or unmapped territory to get it to its desired destination. The value of business analysis is in realizing benefits, avoiding cost, and identifying new opportunities and required capabilities. Through the effective use of business analysis, we can ensure an organization realizes these benefits, ultimately improving how they do business.

Design concepts

Control Tower is the heart of Intelligent Automation Cloud used for automation. Use Control Tower 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 Use Case exchange data. The section provides a reference on how to organize your Data Model through Use Case 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.

MVP concept

High-level description

Major technical concerns of Use Case delivery

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

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.

Each project you create from an ODF Archetype includes an [ARTIFACT]-package module. Inside the module, the resources directory contains a pre-configured structure where you can put Use Case assets for further deployment to Control Tower (CT).

Definitions

In order 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 initiation phase is critical for project success as most preparation and business analysis activities are conducted during this phase. Effective, detailed, and qualitative requirement gathering at the project's beginning helps to maximize benefits and minimize costs while delivering value to a customer. Having a clear scope and success criteria enables you to achieve all this.

Developer approach to publishing

Various requirements make the core content of any project. They are stated, implied, or even unknown yet to a client and revealed only during the analysis. Formally captured requirements compile the project scope.

The requirements management knowledge area implies that requirements are managed and maintained throughout a project. It is paramount that the Data Analyst understands the requirements' lifecycle and knows how to manage requirements. This process identifies tasks that should be performed to keep requirements up-to-date, accurate, and consistent.

To bring to a client most of the value with the help of a selected solution, the team should identify most critical requirements for the project success, their urgency, and the appropriate delivery order. Requirements prioritization is used to serve this goal. It is a process of decision-making to determine the relative importance of requirements based on their relative value, risk, the difficulty of implementation, and other criteria. As a result of this activity, the requirements are listed in their implementation order.

The Data Analyst should know and use techniques to elicit, specify or model the requirements. You can apply the techniques separately or as a combination. Let's consider the most common techniques.

This article describes how to pass data between Business Process (BP) steps, both manual and bot ones.

High-level description

There are certain situations where the four-business-process design is an unwanted complication. In the case of simple PoC or an educational project, it can be time-saving to simplify a project generated from the ODF 2 Archetype.

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 Intelligent Automation Cloud automation solution implementation.

Definition

ODF 2 allows splitting a Transaction into multiple sub-transactions so that each resulting sub-transaction contains a single data entity derived from the data stored in the original Transaction. After that, such sub-transactions are processed the same way as common Transactions. At some point, you must join them back to the original one.

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 associated with this.

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.

All requirements should be analyzed in terms of success criteria or the standards by which the team and the client can judge whether an automation goal is achieved. Success criteria are often linked to metrics.

High-level description

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