Loading...

Executing a Workflow

Table of Contents

Executing from the CommCell Console

Note: Workflows must be deployed before they can be executed. For instructions on deploying a workflow, see Deploying a Workflow.

  1. From the CommCell Browser, go to Workflows.

    The Workflows window appears in the pane on the right.

  2. Right-click the workflow and click All Tasks > Execute.
  3. From the Run workflow on list, select the engine to use to execute the workflow and then provide values for the workflow inputs.

    If you select Any, the workflow engine with the latest deployed version of the workflow is used.

  4. Click OK.

    You can track the progress of the workflow job from the Job Controller tab.

Workflows can be scheduled. For instructions on scheduling a workflow, see Scheduling a Workflow.

Executing from the Command Line

Note: Workflows must be deployed before they can be executed. For instructions on deploying a workflow, see Deploying a Workflow.

Workflows can be executed from the command line using an XML template. For instructions on executing a workflow from the command line, see Command Line Interface - Executing a Workflow.

Executing from Reports

Workflows can be executed from reports associated with the Proactive Support feature. For information about Proactive Support and the related reports, see Enabling Proactive Support.

Executing from the Web Console

Note: Workflows must be deployed before they can be executed. For instructions on deploying a workflow, see Deploying a Workflow.

Forms Application

Workflows can be executed from the Web Console by clicking the Forms link on the My Applications page. For additional instructions, see Forms - Web Console.

Use the following check list to make sure your workflows appear as expected in the Web Console:

  • Workflows are deployed.
  • The correct permissions are set for the target users or user groups. For details on workflow permissions, see Configuring Workflow Permissions.

URL

Workflows can be executed using a Web Console URL, for example, http://client.mydomain.com/webconsole/forms/?workflowName=Demo%20-%20New%20Machine%20Request&name=scsdfcd&Memory=16&Disk=500&software=Backup&software=Outlook&_submit=true.

Syntax

http://host_name/webconsole/forms/?workflowName={workflowName}&workflowId={workflowId}&input_name_1={inputValue}&input_name_2={inputValue}&input_name_N={inputValue}&_submit={true/false}

Parameters

Note: Special characters and spaces must be encoded before they are sent in the request.

Name Description
workflowName The name of the workflow.
workflowId The ID for the workflow. The ID parameter is not required, but it is used if an incorrect Workflow name is provided. To obtain the ID, go to the Forms application in the Web Console and hover over the name of the Workflow.
input_name The value of the workflow input needed to execute the workflow. Use the following format for the input names and input values:

input_name_1={inputValue}&input_name_2={inputValue}&input_name_N={inputValue}

where:

  • Each input name and value is separated from the next input name and value with an ampersand (&)
  • input_name_1 to input_name_N are the workflow inputs
  • input_value is the value for the workflow input

For example:

email=jsmith@mycompany.com&services=all&companyName=mycompany&name=Jess%20Smith&userName=jsmith

_submit Defines how the workflow inputs are handled.

Valid values are:

  • true, the Workflow runs with the inputs provided in the URL
  • false, a user input dialog box appears with the workflow inputs prepopulated

Workflow Engine Selection

When workflows are executed from the Web Console, the workflow engine is automatically selected for the user. If the workflow is deployed on multiple workflow engines, then the following priority order is used to select the engine:

Condition 1: If the workflow engine is installed on the Web Server computer, then this workflow engine is selected.

Condition 2: If Condition 1 is not met, then preference is given to a workflow engine that is not installed on the CommServe computer.

  • If multiple engines are found for Condition 2, the engine with the latest deployed version of the workflow is selected.
  • If multiple engines have the latest deployed version, the engine is selected using the alphabetical order of the client names.

Condition 3: If Condition 2 is not met, then the workflow engine installed on the CommServe computer is selected.