7 docs tagged with "Business Process schema"

Unlike Bot Tasks that are completed automatically, Manual Tasks (MT) require involving a human who is either a cloud worker or an internal employee.

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.

The Transformation step is a no-code bot step that allows you to implement complex scenarios with rule conditions.

The guide describes two automation use cases leveraging no-code Work.AI features and contract-based data schemas:

The article lists operators supported for no-code Transformation and Decision rules steps.