About the Monitoring Window

This topic provides you with information about the Monitoring Window. This Window is a tool you can use at runtime. It allows the end user to have a better view over what he has to do, separating each step of his Design Process. This tab can be used in any app.

This page discusses:

Accessing the Monitoring Window
User Interface

Accessing the Monitoring Window

The Monitoring Window is available for end users when a type containing a process has been added to the component. Open a component with a process and click the dedicated command.

Note: If a process is already present in the database, the Monitoring tab is launched automatically. On the contrary, if a process does not exist, the end user can keep working on the operations from the context menu.

User Interface

The monitoring tab enables the user to launch processes and also to have a status of what has already been done. This tab displays a list of all the processes of the current app. For each of them, a comment (if created by the expert user) appears to give more information to the user on how to use processes. If a process has already been executed (and not been deleted) or if it is currently running, the associated object (Product, Part, etc.) appears underneath the process and its status also appears. Each object displayed owns commands to pilot supervision easily. When the user executes a process, a new tab which embeds the supervision area is created in the monitoring tab.

The Monitoring tab includes two tabs:

Control Tab

This tab contains the list of the processes available in the current app. Each line of this list represents either a process or an object that owns a process (a typed object).

Note: Every available process of the current app appears in a tree and owns the command Execute to execute it. As a process cannot exist without a type, an object (object or feature) must be chosen to bear the type and to enable the execution of the process. Then the object associated with the process is aggregated by the process in the tree.

The Control tab is made up of six different fields:

Name: Corresponds to the process name.
Quality: Can be Process and Subprocess.
Status: Can be Ready, Running, Paused or Completed.
Description: Displays the description entered by the expert user when creating the application.
Triggered By: Indicates the name, the role and the project of the user who launched the application.
Started: Indicates the date and time the application was launched.

Supervision Tab

This tabs shows the whole process.

When the supervision tab is launched for a particular process, the user is presented with a workflow that starts with a virtual (not defined in WorkflowFoundation) Start node (A rounded node). The other nodes are rendered under the start node, ending in another virtual node: the End node. The workflow is always rendered in a top down layout.

Notes:

Conditional constructs (if/else groups) are represented by conditional opening and closing virtual nodes.
Empty branches of the conditional construct are represented by direct links between the opening and closing virtual nodes.
Loop constructs are represented by a dashed upward link from the end to the start of the loop.

This tab includes a series of widgets:

Play : Triggers the execution of the Design Process.
Pause : Freezes the process execution and allows saving what the end user did and where he was when propagating it in the database. When opening another session, the end user can recover the previously propagated persistent data by clicking the Play widget.
Reset : Resets the whole Design Process. Elements stored in the process (i.e. entered values, completed steps, etc.) can be recovered by clicking Play during the next session.

Supervision tab options

: Activates or deactivates Know-how Apps Components style nodes. Deactivate Use DPC style nodes if you want your graph to look like standard business process workflow models.


	Use DPC style nodes enabled	Use DPC style nodes disabled
A node that is ready to be executed
A node that is being executed
A node whose execution timed out
A successfully executed node
A node in error
A node that was not executed
A node with more than one iteration

Mode Selection: There are three modes available for the end user:
- The Automatic mode automatically triggers the execution of each task with no need for the end user to manually trigger every step.
- The Step by step mode requires the end user to manually trigger the execution of each available task.
- The As defined mode is the default choice and runs the task corresponding to what has been defined by the expert user.

Moving the cursor over a node:

Shows the node full name or the comment you added at build time. When a comment was added, click the button to open the target pointed by the comment. It can be a URL or a resource table.
Displays a quick note button you can click to add comments. Clicking this button opens a dialog displaying the note that can be edited. Closing the dialog box validates the content.
Indicates the condition of the block.
Highlights the corresponding end or start node.

The Monitoring Window proposes three ways to execute steps (manually or automatically). These options are available in a context menu appearing when right-clicking steps:

Operate : A step can be processed by selecting this function.
Operate Up To : It allows choosing a target step up to which the execution will be automatic. For this purpose, click Play , then right-click one of the following steps, a context menu appears and click Operate up to. Note that the execution stops one step before the selected step.
Operate up to including : The selected step here is included into this automatic execution. To do so, click Play , then right-click one of the following steps, a context menu appears and click Operate up to including.
Note: If you choose Operate up to or Operate up to including on a step located in a branch, the process does not stop if a branch is not active.