Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Create custom activities using custom activity designer templates

Log in to subscribe to topics and get notified when content changes.

Create custom activities using custom activity designer templates

You can create and update different types of custom activities in the Workflow Editor using a custom template.

Before you begin

Roles required: workflow_admin or activity_creator

About this task

The Activity Designer contains common steps which are applicable to all the activities that you create. This procedure guides you through the common steps and the order they should be set up. You specify an activity template before you create a custom activity.


  1. Navigate to Orchestration > Workflow Editor.
    The Welcome tab of the Workflow Editor opens.
  2. On the Custom tab in the palette, click + to create a new activity select the appropriate template from the list.
    Arrow pointing to the plus sign on the Custom tab
    The Activity Designer form appears, with a stage indicator at the top. All new activities start at the General stage. The current stage shows with a blue underscore.
    Figure 1. Activity designer stage indicator

    Activity designer stage indicator
  3. Add the general properties.
    This information is standard for each custom activity, include a name, description, and other related information.
  4. Create the template Create input variables for the template.
    Create the variables to pass into the activity in the Inputs form of the activity designer.
  5. (Optional) Add a pre-processing script.
    For input validation or transforming input data, you might need a pre-processing script.
    Note: This step is not included in the Run Script activity.
  6. Click Continue to open the Execution Command form, then fill out the Execution Command step based on the corresponding execution templates:
  7. (Optional) Test your inputs.
  8. (Optional) In the Outputs form, define local and/or output variables.
    Local variables can be used for temporary storage when cascading parsing rules. For example, you might extract an XML payload from within a JSON payload. A local variable can access the XML document and use that as a source for another parsing rule. The graphic shows a Local1 variable source to parse data for Output2.
    Figure 2. Define local variable
  9. Use one of the options to assign values to Outputs:
    Parsing rule You can create a parsing rule and map them to the output fields by dragging and dropping the variables into the parsing rules structure. The REST, SOAP, and JDBC templates provide auto-mapping to create the parsing rules automatically. If available from the test inputs form, auto-mapping should be used when possible.
    Post-processing Post-processing scripts allow you to code your own output data validation, output parsing code, and related tasks. Post-processing executes after the execution command results have been returned and before the parsing rules and conditions are run. Click Go to Post-Processing (Advanced) to create a post-processing script.
    Note: If you create a script, this step reflects as a stage in the indicator.
  10. Click Continue to open the Conditions form to create exit condition rules for your activity and then click Save.