13.4.1. Process Template Terminology

Engineering Knowledge Manager

User's Guide | Chapter 13: Defining Process Templates in EKM Studio | 13.4. Defining Process Templates in EKM Studio |

13.4. Defining Process Templates in EKM Studio |  | 13.4.2. Steps for Defining a New Process Template
Prev |  | Next

### 13.4.1. Process Template Terminology

Let's start with defining some process template terms that are used throughout the EKM Studio interface.

Nodes

  Nodes are used to define tasks that a person or machine will perform as part of a process. In addition to the simple node, there are the following specialized nodes that can be utilized in an EKM process: auto node, batch node, iteration node, monitor node, update analysis project node, and custom dialog node.

  Application

    An external application that is defined for an EKM server, and that is launched by a batch node.

  Node

    A node is the simplest type of node element and can be used to model a manual task. For example, you could use a node when you want to assign a task to a particular user or group, or when you want it to be completed when an assignee marks it as complete. On completion, the assignee may be prompted to enter some variables that could be used as inputs for other nodes, or in deciding the paths taken by the process. Nodes are represented in a process diagram with the icon shown above. See Editing a Node.

  Auto Node

    An auto node can be used to model an automated task such as generating a report, archiving data, or performing a validation. It is executed automatically by a process when it is encountered. Auto nodes are represented in a process diagram with the icon shown above. See Editing an Auto Node.

  Batch Node

    A batch node can be used to model long-running automated steps such as executing external applications for preprocessing, running simulations, and postprocessing. Batch nodes are represented in a process diagram with the icon shown above. See Editing a Batch Node.

  Iteration Node

    An iteration node can be used to model an iterative process such as approvals and iterative simulations. It defines an iteration condition that holds until it is not satisfied. Iteration nodes are represented in a process diagram with the icon shown above. See Editing an Iteration Node. You can also create nested iterations. See Creating and Editing Nested Iterations for details.

  Monitor Node

    A monitor node can be used to monitor external processes or batch tasks. A monitor node will wait until all the monitored processes are completed and only then will it go to the next stage. You can open the monitor node while it is running to view the status of all monitored processes. Monitor nodes are represented in a process diagram with the icon shown above. See Editing a Monitor Node.

  Update Analysis Project Node

    An update analysis project node can be used to update the analysis contained within an Analysis project folder. Analysis projects may reference external files that may change, and this also requires the project to update itself, so update is required even if the project contents have not changed. A simulation details report is created when this node is invoked, which contains extracted metadata of CAE files contained within the Analysis Project folder. If the Analysis Project folder contains a Workbench Project archive file (.wbpz), then in addition to generating a simulation details report, metadata will be extracted from all CAE files contained within the Workbench project and added to the Workbench Project archive file properties. Update analysis project nodes are represented in a process diagram with the icon shown above. See Editing an Update Analysis Project Node.

  Custom Dialog Node

    Custom Dialog Editor is a dialog box or wizard you create or modify and add to a process. You can interactively define all aspects of the custom dialog box (user interface elements, macros, and so on) in the Custom Dialog Editor, then save the resulting .pt.xml file on your local file system and publish the definition to EKM. For details on the Custom Dialog Editor, see Defining Custom Dialog Boxes and Wizards in EKM Studio.

  Process Template Node

    A process template node enables you to nest an existing process template within the current process template. When the process reaches the process template node, the first task defined in the nested template begins to execute. When the last task in the nested template has been completed, the process advances to the next node in the main process. When inserting a process template node you will be prompted to select a process template to insert. See Inserting a Process Template Node for details. Once inserted you can edit the node’s properties and specify input/output variables. For details see Editing a Process Template Node.

Transitions

  Transitions are links between a starting node (source) and an ending node (destination). A transition can have a trigger expression associated with it or it can just progress to the next nodes based on previous node completion. A trigger expression will determine whether the transition will be traversed in a process. If no trigger expression is specified, then the transition is always triggered. Transitions are represented in a process diagram as arrows. See Defining and Editing Process Transitions.

Variables

  Variables are used to store the state of a process once it has started, and must be defined in a process template. You can assign default values to the variables or specify other values that must be entered when the process is being executed. The value of a variable is also used to determine transitions that are triggered when an iteration is completed. See Defining Process Variables.

Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.

Prev | Up / Contents | Next

Release 18.2 - © ANSYS, Inc. All rights reserved.