Edit Start Unit

Edit Start Unit

Overview

The Start Unit is the entry point of a flow in the Automation Flow Designer/Editor. It defines when and how an automation flow is initiated and marks the start of execution. The start unit is mandatory for the flow, where you need to define the systems for your automation. It is responsible for capturing initial input data and passing control to the next unit in the flow, triggering it based on defined conditions or events.

Purpose of the Start Unit:
  1. Marks the beginning of the flow execution
  2. Initializes the flow
  3. Accepts input parameters (if configured)
  4. Passes control to the next connected unit
Key Characteristics:
  1. It is mandatory in every flow.
  2. Only one Start Unit is allowed per flow.
  3. It cannot have any incoming connections.
  4. It can have one or more outgoing connections (depending on flow logic).
How It Works:
  1. The flow is triggered (manually, via API, schedule, etc.).
  2. The Start Unit receives the input data.
  3. Execution proceeds to the next connected (trigger) unit.

Accessing Start Unit Properties

  1. The Start unit is the first unit of any flow. By default, the unit is present and cannot be deleted. However, you can modify its properties.
  2. To view/modify the unit property, click on the Start unit. Upon clicking the unit, a property panel opens below it, and the unit is highlighted.
  3. The property panel will open and display the Processing section.
    Please note that the start unit will not have the Input and Output sections in the property panel, unlike other units.
  4. The tabs will vary based on the selected triggers:
    1. Port Assignment
    2. Test Message
    3. User Settings
    4. HTTP Parameters (for HTTP triggers only)
  5. You can switch between the tabs by clicking on them.

Port Assignment Tab

  1. By default, the Port Assignment tab will open.
  2. It provides information about the system attached to the automation.
  3. The section shows two columns:
    1. The first column (left) provides the system's port information. This indicates which system is involved in the automation.
    2. The second column (right) lists the SLDs you have already created. You might have multiple SLDs with the same type. You need to map the SLD to the system port. Select the SLD that you want to use. Once the SLD is selected, the band in the left-hand column will display a tick icon. A toaster message confirms that the system is assigned successfully. 
  4. Please note that if you have not assigned any system to your automation, the second section will be empty with an Add Entity button. 
  5. You can assign the entity to automation using the Add Entity button.
Notes
If the unit is deactivated, all bands will be shown in read-only mode. You cannot assign a system to your automation while it is deactivated. To assign the system, you need to activate the unit first.



Assign System to Automation

This section explains how to add systems to your automation.

User Settings Tab

  1. This section explains how to view and modify your automation's user settings.
  2. To view the user settings, click on the User Settings tab.
  3. Based on the selected automation, the settings will be provided. These settings may vary from automation to automation. However, an (i) icon will describe the settings.
  4. Hover over the (i) icon, and a tooltip will appear displaying the description of the setting. 

Modify User Settings

  1. You can modify the name of the settings in this section.  
  2. Click inside the field that you want to modify. As you click inside the field, the edit mode gets activated.
  3. Edit the settings' names as needed.
  4. Once the modification is complete, click the Save button in the action area of the screen. 
Notes
If you try to exit the screen without saving the modification, a confirmation message will appear.  


Test Message Tab

Purpose:
  1. Simulates real input data
  2. Helps test mappings, conditions, and transformations
  3. Validates flow logic before deployment
  4. Assists in debugging
How It Works
  1. You define a sample XML structure in the Start Unit.
  2. When you test the flow, the system uses this XML as the input.
  3. The flow processes the data as if it were triggered by a real trigger (API, queue, timer, etc.).
Key Points: 
  1. It is used only for testing
  2. It does not affect production execution
  3. The XML structure should match the expected input schema
This section explains how to work with the XML message of your automation. This message allows you to test your automation. The Test Message (XML) is a sample input payload used to test and simulate the flow execution during development. It allows you to validate how the flow behaves without needing an actual external trigger. 
  1. To access the Test Message tab, click on it.
  2. The panel exhibits the Test Message (XML). This XML will serve as the default test message, containing the requisite XML structure. Nonetheless, modifications to the XML are permissible as needed.
  3. Above the message, a drop-down list displaying the XML names—shown below—is available. You may select any other XML for your purposes. Please be advised that the drop-down will only list the XMLs you have created.
  4. Adjacent to the drop-down, a (+) icon is available to create a new XML.
  5. Beneath the drop-down, a toolbar is provided to assist with XML modifications.

Add a new XML

  1. To add a new XML file, click the (+) icon shown on the screen.

  1. Upon clicking the icon, an Add Test Message pop-up will appear.
  2. Enter the desired name in the Name field and click the Add button.

  1. Once you click the Add button, the system will generate the structured XML and display it on the screen. 
  2. By default, the newly created XML will be selected in the drop-down.
  3. To save the XML, click on the Save button provided in the action area of the screen.

Modify the Existing XML

  1. Once you have created an XML file, you can modify it as needed.
  2. A toolbar is provided on top of the XML file, and you can make use of that to modify the XML. Refer to the Toolbar article to know how to use the toolbar. 
  3. Start modifying the file directly on the screen. Once modified, click on the Save button.


HTTP Parameters Tab

Upon clicking the unit, the Start Unit property panel will open. The HTTP  Parameters tab will appear only if the HTTP trigger is configured. This tab lets users define static HTTP headers and query parameters that the integration passes with incoming requests. The panel is split into two collapsible sections: Header and Query.



You can define one or more static HTTP headers or query parameters by entering key-value pairs. They can add as many rows as needed using the ⊕ button, remove individual entries with the delete icon, and collapse either section to reduce visual noise. These parameters are sent in the HTTP request when the Start unit triggers the integration flow.

Header Section

A collapsible section for defining HTTP request headers.
  1. Collapse/Expand chevron (^) — Click to collapse or expand the Header section.
  2. Key field (required *) — A text input where the user enters the header name. In the example, the value is H1.
  3. Value field (required *) — A text input where the user enters the header value. In the example, the value is 001.
  4. Delete icon (trash/bin) — Appears to the right of a filled key-value pair. Click to remove that header entry.
  5. Second Key / Value pair (empty) — A blank entry row with placeholder text Key and Value. Users type here to add a new header parameter.
  6. Add icon (⊕) — Click to add another key-value pair row to the Header section.


Query Section

A collapsible section for defining HTTP query string parameters, structured identically to the Header section.
  1. Collapse/Expand chevron (^) — Click to collapse or expand the Query section.
  2. Key field (required *) — A text input for the query parameter name. In the example, the value is Q1.
  3. Value field (required *) — A text input for the query parameter value. In the example, the value is 01/02.
  4. Delete icon (trash/bin) — Removes the filled query parameter entry.
  5. Second Key / Value pair (empty) — A blank row for adding a new query parameter.
  6. Add icon (⊕) — Click to append another query parameter row.

    • Related Articles

    • Edit XSLT Unit

      Overview The XSLT Unit is an action unit in the Flow Editor/Designer that enables you to transform XML data using XSLT (Extensible Stylesheet Language Transformations) during execution. It allows complex XML transformations, mappings, and ...

    • Edit Delegate Component Unit

      Overview A Delegate Component Unit in a flow diagram represents a self-contained, reusable block of logic that performs a specific task. You can reuse it whenever needed within a larger process, much like using a pre-built piece in a puzzle. What it ...

    • Edit Delegate Automation Unit

      Overview The Delegate Automation unit in a flow diagram represents a step where the workflow performs an automated action without manual intervention. It’s designed to execute predefined tasks using scripts, bots, or automation services. What it ...

    • Edit Subscription Trigger Unit

      Overview Trigger Units are responsible for starting the execution of a flow. They define how and when a flow is triggered. A flow always begins with a Start Unit, and immediately after that comes a Trigger Unit. The following trigger units are ...

    • Edit Queue Trigger Unit

      Overview Trigger Units are responsible for starting the execution of a flow. They define how and when a flow is triggered. A flow always begins with a Start Unit, and immediately after that comes a Trigger Unit. The following trigger units are ...