Create a probe activity Use these instructions to create a custom Probe Orchestration activity. Before you beginRole required: activity_creator or workflow_admin About this taskFor instructions on using the activity template process flow, see Create custom activities Procedure Navigate to Workflow > Workflow Editor. In the workflow palette, select the Custom tab. Click the +icon. Select the Probe template. The template opens in the General stage. Figure 1. Activity designer stage indicator Complete the fields shown in the table. Table 1. Fields common to all activity designer templates Fields Description Name Descriptive name of the activity. Select a unique name that makes the activity easily identifiable in the palette. If you do not name the activity, it is identified in the Data tab of the workflow editor with an index number when it is added to a workflow. This index reflects the order in which the custom activity was added to the workflow. Only custom activities and their output variables appear in the Data tab. Short description Brief description of what the activity does. Image Icon that identifies an activity of this type in the workflow palette. Protection policy Setting that controls access to the code in the Pre Processing and Post Processing script fields of this activity. Use these settings to protect your intellectual property: None: Script is unprotected. Read-only: Script is in plain text, but read-only. Protected: Script is encrypted and read-only. Important: Make sure to set this field properly before submitting the record. After you save the activity, this field becomes read-only. Execution template Predefined template selected for this activity. Application Current scope set on the instance. To view the scope, click the gear icon on the right side of the title bar in any record or list and look at the value in the Application field. The activity runs in this scope within a workflow. You cannot view or change the scope for the instance in the workflow editor. Accessible from Accessibility setting for this activity, by scope. The following options are available: All application scopes: This activity is available to all application scopes. This application scope only: Use of this activity is restricted to the scope named in the Application field. Category Category for this activity in the Custom and Packs tabs. All categories are listed under their scope in the collapsible hierarchy. Description Detailed description of the activity. Click Continue to advance to the Inputs stage. Create Probe template input variablesCreate the variables to pass into the Probe activity in the Inputs form of the activity designer. Configure the Probe execution commandUse the input variables you created to configure the command that Orchestration executes on the target.Probe template pre-processing fieldsUse the Pre Processing form of the activity designer to define a script to run before the activity executes.Probe template execution parametersYou use execution parameters to create the input process script in the Pre Processing form.Probe template outputsProbe output variables contain values returned from an endpoint that are available to other activities in a workflow or internally to the activity.Probe template post-processing fieldsUse the Post Processing form of the activity designer to define a script to run after the activity executes.Probe template post-processing parametersUse these parameters to create a post-processing script.Probe template conditionsCreate the exit conditions for your activity in the Condition column and set the order for each.
Create a probe activity Use these instructions to create a custom Probe Orchestration activity. Before you beginRole required: activity_creator or workflow_admin About this taskFor instructions on using the activity template process flow, see Create custom activities Procedure Navigate to Workflow > Workflow Editor. In the workflow palette, select the Custom tab. Click the +icon. Select the Probe template. The template opens in the General stage. Figure 1. Activity designer stage indicator Complete the fields shown in the table. Table 1. Fields common to all activity designer templates Fields Description Name Descriptive name of the activity. Select a unique name that makes the activity easily identifiable in the palette. If you do not name the activity, it is identified in the Data tab of the workflow editor with an index number when it is added to a workflow. This index reflects the order in which the custom activity was added to the workflow. Only custom activities and their output variables appear in the Data tab. Short description Brief description of what the activity does. Image Icon that identifies an activity of this type in the workflow palette. Protection policy Setting that controls access to the code in the Pre Processing and Post Processing script fields of this activity. Use these settings to protect your intellectual property: None: Script is unprotected. Read-only: Script is in plain text, but read-only. Protected: Script is encrypted and read-only. Important: Make sure to set this field properly before submitting the record. After you save the activity, this field becomes read-only. Execution template Predefined template selected for this activity. Application Current scope set on the instance. To view the scope, click the gear icon on the right side of the title bar in any record or list and look at the value in the Application field. The activity runs in this scope within a workflow. You cannot view or change the scope for the instance in the workflow editor. Accessible from Accessibility setting for this activity, by scope. The following options are available: All application scopes: This activity is available to all application scopes. This application scope only: Use of this activity is restricted to the scope named in the Application field. Category Category for this activity in the Custom and Packs tabs. All categories are listed under their scope in the collapsible hierarchy. Description Detailed description of the activity. Click Continue to advance to the Inputs stage. Create Probe template input variablesCreate the variables to pass into the Probe activity in the Inputs form of the activity designer. Configure the Probe execution commandUse the input variables you created to configure the command that Orchestration executes on the target.Probe template pre-processing fieldsUse the Pre Processing form of the activity designer to define a script to run before the activity executes.Probe template execution parametersYou use execution parameters to create the input process script in the Pre Processing form.Probe template outputsProbe output variables contain values returned from an endpoint that are available to other activities in a workflow or internally to the activity.Probe template post-processing fieldsUse the Post Processing form of the activity designer to define a script to run after the activity executes.Probe template post-processing parametersUse these parameters to create a post-processing script.Probe template conditionsCreate the exit conditions for your activity in the Condition column and set the order for each.
