15 docs tagged with "Business Process execution"

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.

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

Records and transactions

The page describes the process designed to enable the following:

Signal-based Business Processes (BPs) continuously receive records from input connectors, Triggers, or other BPs. In some cases, the flow of records can be very high or nearly infinite, resulting in excessive record accumulation within a single BP instance. This accumulation can lead to significant performance degradation during BP execution.

After you uploaded the input data, designed the Business Process (BP) flow, and set run options, it is recommended to test the Business Process and then run it in production.

Besides running Business Processes (BPs) manually, you can set them to run on schedule.

Download the Scheduler Business Process package.

To configure the settings for a specific Business Process (BP) run, select it in the BP list and navigate to the Run page.

To assist you in real-time process monitoring, analyzing data, and presenting it effectively, WorkFusion Analytics offers the following tools:

The monitor design assumes continuous managed loops generation during a scheduled period of time. For certain business needs, you may require to stop your Business Process (BP) immediately upon some trigger. Moreover, it is desired that the BP does not ruin transactions that already came out of the monitor's loop and are processed further.

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.

A Data Source is a mechanism providing input data and configuration for your Business Processes (BPs). The input format is best suited for those use cases where the data resides on an external source, such as an SFTP Server or Amazon S3 Cloud.

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 Results tab displays the output of a business process (BP) run. It is available as soon as the BP is launched on schedule or manually.