Defining Properties for Workflow Cells

For each workflow cell, you must define the minimum properties required for publishing. After all cells have green check marks for their state icons, you can publish the workflow.

  1. In the Workflow Preview workspace, select the task group cell.

    The Properties pane displays the properties for the task group.

  2. Define task group properties, referring to the descriptions below if necessary.

  3. For each task cell in the task group, do the following:

    1. In the Workflow Preview workspace, select the task cell.

      The Properties pane displays the properties for the task.

    2. Define task properties, referring to the descriptions below if necessary.

Task Group Properties

Descriptions follow for task group properties:

  • Name: Name of the task group, which displays in the Workbench Toolbox under the group chosen for Category once the workflow is published.

  • Version: Release number for this iteration of the task group. The default is 1.

  • Icon: Image file to display as the icon for the task group.

  • Category: Group under which to place the workflow in the Workbench Toolbox. The default is ACT.

  • Abbreviation: Workbench system abbreviation.

  • Parametric: Indicates whether the task group operates only on design points. As such, the task group is added below the Workbench Project Schematic. This focus on parameters enables you to incorporate DesignXplorer-like functionality.

Task Properties

Descriptions follow for task properties:

  • Name: Name of the task.

  • Version: Release number for this iteration of the task. The default is 1.

  • Icon: Image file to display as the icon for the task.

  • Application Path: Path and name for the file to execute, which can be an EXE file for an external application or any file with which a system-installed program has been associated.


Note:  The application path is a fully qualified path. If you intend to share this project, use an environment variable in the application path so that others can then set this environment variable to the location on their machines where the executable file for the external application resides. For example, assume that the fully qualified path is E:\WorkflowDesignerInputFiles\ExampleAddinExternalSolver.exe. By changing it to %ExternalSolverExecutable%\ExampleAddinExternalSolver.exe, you allow users to set the path to the executable file in the environment variable %ExternalSolverExecutable%.