This topic highlights the key differences, enhancements, and new features introduced in the new editor compared to the previous version, helping you transition smoothly and leverage improved capabilities.

Changes to the user interface

comparison old vs new editor

  • The property panel has been updated with a rearranged layout for task type fields to enhance usability.
  • Help text and descriptions have been added to specific fields within the properties panel for each element, providing clearer instructions and improving the overall user experience.
  • For task types (Bot, Document Validation, API, Filters, Forms, Approval, and Process), the following label changes have been made in the properties panel:
    • Element name is now Element ID
    • Task name is now Task name (optional)
    • Additionally, for task types (Bot, Form, API, Approval, and Process), the Browse button has been renamed to Choose to better reflect its function.
Review the table to understand the additional label changes in the properties panel for each task type:
Elements Type Former editor Equivalent new editor
Left panel -
  • Logic
  • End point
  • Conditional
  • Event
Start event Label Variable Input variables
End event Label End process status Status
Go to event Label Select target task Target task
Document validation Label Learning instance version Learning instance version (optional)
Bot Labels
  • Select bot
  • Task Bot inputs
  • Automation Execution mode
  • Automation queue timeout
  • Bot
  • Input values
  • Execution mode
  • Queue timeout
API Labels
  • API task
  • API task inputs
  • API
  • Input values
Filter Labels Criteria for Filter Filter criteria
Form Labels
  • Select form
  • Form inputs
  • Add form button
  • Button label and Button style
  • The assigned group of the request
  • Specify user group
  • Assign this task to
  • Form
  • Input values
  • Action buttons
  • Label and Type
  • Assigned group
  • Specific user group
  • Task assignment
Form - Make the form read-only check box Form mode field with two tabs (Interactive and Read-only)
Approval Labels
  • Approval content form
  • Form inputs
  • Action buttons
  • Label for the approve button
  • Label for the decline button
  • The assigned group of the request
  • Specify user group
  • Assign this task to
  • Form
  • Input values
  • Action button labels
  • Approve button label
  • Decline button label
  • Assigned group
  • Specific user group
  • Task assignment
Process Labels
  • Select Process field with two tabs to select from (Public folder and Private folder)
  • Process inputs
  • Assign request to
  • Process field with Choose button to select the files from Private or Public folder
  • Input values
  • Task assignment

Changed behavior

The following list highlights the changes in the new editor compared to the former editor:
  • When you create a process in a new editor, you can use the alphanumeric characters in the Element ID. However, the following characters are not allowed:
    • dollar sign ($)
    • ampersand (&)
    • at sign (@)
    • period ( . )
    • braces (not curly brackets) { }
    • brackets [ ]
  • For task types (API and Bot), the Run bots and dependencies using field is not available in the new editor.
  • The Preview option in the former editor is now replaced with Show details in the new editor for task types. When you select a file link, you can hover over the info icon to view additional information, such as the folder path, status, modified by, and time. You can click the file path link to view the file.
  • The Bot priority option is not available in the new editor for Bot task type.
  • In the former editor, if you have added a Form button and then click Make the form read-only, the system displays a prompt message. This prompt message is not displayed in the new editor. Additionally, when you select Make form read-only in the new editor, the system automatically removes all form buttons and disables the Add button.
  • When you create a process in the former process editor and use variables with the variable type set as output while assigning default values, a change in behavior occurs when you transition to the new editor. In the new editor, you will observe that the output variables are listed in the Variables section. However, the variable expressions set as default values for the variables you created will not be shown there. Instead, these expressions will now appear as part of the Output variables section in the property panel of the Start node.

    Alternatively, any constant values assigned as default values to output variables will still be visible in the Variables section.

  • In the former editor, when you add a Form Task to configure the settings of process automation, you use the Feed data into form field option to input a list of options along with their default values. However, when you open such process in the new editor, you will observe a change in terminology and structure. The Feed data into form field is now renamed to the Input values field in the Form element.

    Moreover, there is a change in how the data is displayed. The two distinct fields for List of options and Default values are now combined into a single field. In the new editor, the default values will be presented first, followed by the list of options, separated by a semicolon.

    Note: The individual list of options and default values will be separated by commas within this combined field.

    For example, if you had previously defined default values and options in the former editor, they will now appear as follows in the new editor: Submit; Primary, secondary, tertiary.

Known limitations

The following are some known limitations of using the Next-Gen Process Composer to develop automation within the process editor.
  • When a Goto element is added in the process editor below any node by double-clicking from the left panel, it is inserted as an disconnected node on the canvas. However, its placement is far away from the selected node, making it difficult to locate.
  • Currently, the system allows you to add an If-Else conditional statement after the Start node to your process workflow, which is unexpected behavior.