...
Navigate to the Workflows screen and click on Create Workflow.
On Create Workflow screen, add the new workflow details. Following are the details available on the screen:
Add ‘Name’ represents the name of the Automation Workflow.
‘Identifier’ represents the unique identifier of the workflow.
Add 'Description' for the workflow.
Add ‘Retry Configuration’. The configuration enables the system to retry executing the operation in case of an error.
Add the number of ‘Total Attempts’ for retries in case the operation fails.
Configure the ‘Retry Time’ to define the time interval between each Attempt.
Click on Create to create the Workflow.
...
Table of Contents | ||||
---|---|---|---|---|
|
Configure Workflow Parameters
...
On the Workflow section, select the new workflow.
On the workflow screen, open the Properties Panel → Workflow Inputs tab.
In the Input Parameters section, add the input parameters required for the business workflow.
Click on + to add the Input Parameter
Add the Parameter name and Data type.
Mark Required if the parameter is required to execute the process.
Add Required Field Validation Message.
Select the Validation Type if applicable.
Similarly, add other parameters as required.
Define Workflow Variables
...
On the Workflow Designer screen, drag and drop the Create ServiceTask control. Here we can configure the task or action to be executed in the Target system.
Select the Service Task and open the Properties Panel. On the Properties panel, configure the operation to be executed in the Target system. Add the following details:
On theProperties panel → General tab, add the general Service Task information:
Add the Service Task Name and any Documentation detail.
In the Connected App, select your Target system.
Select the Instance that connects to your target environment. Refer to Create Integration Operations for more information on integration App and Instance creation.
Alternatively, you can also drag and drop the Connected App from the left pan on the designer. This automatically creates a Service Task for the selected Connected App. Add the Service Task details and required Instance for your target environment.
Configure Input-Output Variables
...
Select the Service Task and navigate to the Properties Panel → Input/Output tab. Configure the Input and Output parameters for the operations.
In the Input Parameter section, add the input parameters required to execute the task on the target system.
Click on + to add to create a new Input Parameter.
Add Parameter name.
Select Text Data type.
Select Required if the attribute is required for the operation.
Add Required Field Validation Message.
Add Validations as required.
Next, add Mapping to define the way the parameter should accept the value. The parameter can accept value from the user’s input, existing parameters from earlier steps, or from the Workflow.
Define the Direct Mapping to represent the Mapping type. You may use:
Step Output Parameter to use output parameter from the previous steps.
Step Meta Parameter to use metadata parameters from another Service Task in the Workflow as input.
Workflow Input Parameter to accept information from user’s input. You may use the User-defined or System Defined attributes created as the Workflow Input parameters (created in Point 3).
Workflow Variable to use the system-defined or user-defined Workflow Variables such as workflow ID, Tenant ID.
Set Constant Value to assign a default constant value to the parameter.
Constant Transform Function to use a transformation function to assign a value to the parameter. You can use the out-of-the-box Random UUID function to generate a random universally unique identifier.
Expression is used when you want to apply a Mathematical operation or method to process an expression.
For a Required field, add Default Value.
You can also use a Transformation function to update the value before using the same in the workflow. Select Apply Transformation and pick the required out-of-the-box Transform Function.
Follow the above steps to add as many input parameters as required.
In the Response Output Parameters section, create the parameters or attributes to hold information received as a response for the target system.
Click on + to add to create a new Output Parameter.
Add a Parameter name.
Select Text asData type.
Add a Default value if required.
Select Extractor type to represent the type of expression to extract information. For example, select JSON web service response is a JSON path.
Add Expression to represent the response path of the value to be assigned to the attribute.
Configure Operation
...
On the Input/Output tab, scroll down to the Meta Parameter section.
Click on + and the Parameter name:
Click Save.
Info |
---|
To use the value of in Response Header, ensure that the Meta Parameter name is the same as the Header Name. |
...
On the Workflow Designer screen, drag and drop the XOR Gateway. Use the connect tool to create a link between the link and the gateway.
Use the Connect tool in left pan to connect the gateway to existing elements.
Alternatively, you can also select the existing element and add the gateway as the next step.
Once added, on the Properties panel → General tab, add Name and Documentation information.
Once the XOR gate is added, add the next steps and rules to govern the next steps in the workflow. You can add Service Tasks to execute a task or add another XOR gate to evaluate another rule.
...
Select XOR gateway and use the Sequence Message Flow or Association tool to create a link with the next element.
Now select the link to add the associated rule.
On the SequenceFlow properties panel, add the rule to be evaluated.
Add rule Name and Documentation details
In the Condition Expression field, add the rule. Here you can refer to a parameter from the previous step and create the rule.
To refer a parameter from a previous step, use $.out_<Activityname>_<paramtername>. For example, ${out_Activity_17mx2d1_default_status == 'SUCCESS'}.
Note: Select the element and copy the element ID from the properties panel.
Follow the same step to create as many rules as required.
...
Create StartEvent: Start Event represents the beginning of the Business Workflow. Every workflow or Sub-process starts with the start event. To add a Start event, drag and drop the event on Web Designer.
Create an End Event: End Event represents the end of a process or sub-process. A business workflow can have multiple End events. Each path in the workflow always ends with an EndEvent.
Use the Hand tool to scroll through the Workflow Designer window.
Use the Lasso Tool to select and move a section of the workflow process. All the connections are rearranged based on the new position of events.
The Space Tool is used to create or remove space in the workflow. The tool creates space in the workflow for adding more events.