Process Composer

Process Composer is an environment that leverages multiple products across the Automation 360 platform to deliver an Intelligent Automation experience.

Professional and Citizen Developers can use the Process Composer’s low-code features to collaborate and build end-to-end process automations. Process Composer displays correct data to the appropriate users and exchanges that data across multiple teams. Using a single, drag-and-drop visual interface, developers can quickly build long-running process automations that combine bots, forms, document processing, integrations, and API Tasks.

Benefits of Process Composer

Professional and Citizen Developers can:

  • Optimize complex workflows: Simplify business operations across departments by automating multi-user, multi-step tasks and approvals.
  • Empower employee experience: By transforming end-to-end processes, combine robotic tasks with connecting APIs and can insert humans-in-the-loop where needed.
  • Boost operational productivity for the organization: Time between tasks decreases, service level agreements (SLAs) are enforced, and teams are promptly alerted within their application of choice.

Process Composer components and elements

Process Composer is comprised of three components:

  • Process discovery component: You use Process Composer to discover processes, and then learn (reference) from them. An asset generated from Process Discovery can be a process workflow that gets translated into a process automation in Process Composer.
  • Process automation design component: You create and design process automations which link bots and forms together. Additionally, the process automation contains the logic that triggers the bots and forms, and coordinates the flow of data between them. A process automation contains the following elements:
    • Request: A specific instance of a process automation that defines a template of how bots and forms interact.
    • Initial data: Fed into the process typically entered by a user and consumed through a form as the first step.
    • Sequence of steps in a process automation: Which can contain any of the following process automation elements:
      • Form Task: Completed by users which enable them to invoke and interact with the bots through the customizable web interface.
      • Bot Task: Previously built in the Bot builder and available to select in Process Composer. The bots automate specific, repetitive, and rule-based tasks.
      • API Task: Task that connects to a specified API and retrieves data for the process automation to consume. When invoked from a process automation, API Tasks provide a faster response than a Bot Task when called in the same process automation.
      • Approval Task: Task that alerts a responder to approve shared data.
      • Document Validation: Task that requires document approval.
      • Input, output, and meta variables: Includes shared data in the process automation.
    • Logic conditions: Such as theIf/Else pair or Else if to include internal and conditional branching of the process automation.
    • End states: Closes each request (specific instance of a process automation) with a status such as: completed, failed, or canceled.
  • Process automation management component: After you have created a process automation, you can check it in to deploy and make available to other users in the web interface. Additionally, you can import, export, run, delete, and check out process automations.

Process composer diagram

Click Process Composer package to learn how to configure bots using actions from the package.