Get familiar with Next-Gen Process Composer

The Next-Gen Process Composer is the core component of the design-time environment, encompassing all the necessary resources and process-related features that enables you to create and design comprehensive end-to-end process automations.

The Next-Gen Process Composer comprises three main components: Elements and properties, Process editor, and Process editor toolbars. Review the following information to understand the available capabilities that can help you accelerate development and create more robust automations.

Components of Next Gen Process composer

Elements and properties

Use the Elements panel to add flow elements and sequence flows to your business process by simply dragging and dropping them onto the process editor canvas. The element panel contains all the nodes that can be used to define a process workflow. These activities are separated into three main categories:
  • Task: Task nodes consist of human tasks such as Form, Approval, and Document Validation that display information and gather inputs from user groups, as well as automated tasks such as Bot and API that integrate specialized business services, boosting productivity. A process automation contains the following elements:
    • API: API tasks retrieve data for process automation and respond faster than bot automation when invoked in the same process. The API Task is utilized for API-driven cloud automation, often handling data queries and transformations between different systems.
    • Bot: Bots created in the Bot editor perform specific tasks based on triggers or conditions, and they are available for selection in Process editor to automate repetitive, rule-based tasks.
    • Filter: You can apply a filter to a process automation variable in Process editor. For example, if you have a table as the output of a form, and one of the columns is labeled Approved, which contains Yes or No values, the filter task will be able to retrieve only the rows that have Yes in that column.
    • Process: The Process task is used to initiate child processes from the parent process, enabling data transfer between them.
    • Approval: Configure an approval task to share requests with decision-makers before the process automation is completed. The need for approvals applies to many business tasks, such as time off or purchasing requests. Developers can use the approval task to automate a process where users can submit and receive approvals while staying notified of progress without breaking from the streamlined workflow.
    • Document Validation: Document automation uses the technology of Automation Co-Pilot for Business users to manage the end-to-end document extraction process. Each incoming document creates a new request, which triggers the extraction process. If a document requires manual validation, the Automation Co-Pilot creates a validation task and assigns it to a validation team.
    • Form: Users can easily interact with bots through a customizable web interface that allows for direct engagement and invocation of specific functions. The Form task activity is used to assign a task to a user or group. Forms are associated with a Form task to capture data from a form displayed in Automation Co-Pilot and convert it into a process.

    See 프로세스 자동화에 태스크 추가.

  • Conditional: Conditionals are used in process automation to manage the flow of a program based on specific conditions, further enhancing efficiency. The rules and conditions that determine when and how bots and forms interact guide the flow of data and actions within the automation. For example, the If/Else pair and Else If, which facilitate internal and conditional branching in process automation.

    See 프로세스 자동화에 조건 추가.

  • Event: Event activities in your process determine the start, end, and ability to skip specific steps or direct the flow to certain stages based on predefined conditions of your business process, ensuring a productive and efficient process flow. You can use the following events in your process automation:
    • Start: A start node indicates the beginning of a process. It starts with an input variable. Each process can have only one start node, and start nodes cannot be deleted.
    • End: This node denotes the end state of a process, which can be functionally classified as Completed, Failed, or Cancelled.
    • Go to : This node denotes the transfer/navigation of flow to another task in the process. Routing a flow to a specific task is usually based on some conditions. Go to is also one of the endpoints of a particular flow in the process.

    See 프로세스 자동화에서 이벤트 추가.

To adjust or modify the properties of a node, click the element you want to edit and then go to the properties panel on the right side of the interface. In this panel, you will find various options and fields. You can change the values according to the element you selected, customizing the node to better meet your needs.

Process editor

The editor serves as the central workspace within the Next-Gen Process Composer.

In the Process editor, you can create end-to-end process automations that seamlessly connect bots and forms. Each process automation includes the logic that triggers these bots and forms, while also managing the flow of data between them. Once you have developed a process automation, you can check it in to deploy it in the public workspace, making it accessible to other users. You can also import, export, run, delete, and check out process automations as needed.

When you create a new process automation or open an existing one, it opens in the new Process editor by default. You can use the new unified editor's enhanced features and capabilities to start creating and designing in the new editor. This new editor provides clear, visually organized node visualizations, allowing you to work efficiently and design using different tasks, bots, APIs, and forms. The improved usability and navigation make it easier for you to access dependencies without extra steps. These enhanced capabilities allow you to design complex, high-level business process modeling.

However, if you want to open the same process in the old editor, you have an option to switch from new to legacy editor. Click the three vertical ellipsis and select Switch to legacy editor.
Note: When you open a process in the new editor and want to switch from new to the legacy editor, any new features or disconnected nodes created in the new editor will be lost if you switch back to the old editor.

See Process Editor.

Process editor toolbars

The Process editor toolbar offers quick access to essential controls for process design. It allows you to implement logic conditions, add swimlanes, and manage endpoints with functions such as copy, paste, and cut. Additionally, you can double-click to replace items directly on the editor, enhancing your workflow efficiency.

See Process editor toolbars.