What is the Process Mapper ?

The Process Mapper is an add-on that allows the user to create a process of dependent tasks. Basically, it is an editor to:

  • Set conditions between tasks
  • Link variables between tasks
  • Build extendable workflows

Task execution can be monitored from the Process Mapper (as well as the Task Monitor tool).

It is important to note that the conditions and the mapping are written in the task document itself (and not in the process map).

What is a process map ?

A process map is a group of tasks arranged in some structure of linkage and can be displayed graphically in a Process Mapper window.

  • Tasks can be added to a process map on the fly, even during the execution or at the end of the current execution
  • A process map itself only contains references to the tasks defined within it and their position on the screen (as said earlier, it does not hold the actual conditions and variable links defined between the various tasks)
  • A process map is owned by one (1) user and cannot be shared to project and team members
  • The “Clone from here” button duplicates the currently selected task and the dependent tasks (this does not create a new process map)
  • The “Duplicate the process map” button in the tool bar, creates a new process map by duplicating all tasks of the current process map

What is a process map template ?

A process map template is a released process map that can be shared between project and team members using the standard Gateway mechanism. Tasks with the status “TEMPLATE” are created to keep the conditions and variables mapping.

Depending on permissions, users can take a process map and instantiate it as a new process map from this process map template to start working.

Process map versus Task hierarchy ?

A process map displays the graphical links between tasks.
A task hierarchy is a group of tasks that are executed within a parametric study process (or parametric study process map).
A process map generates one task hierarchy “master”. When you clone tasks under a process map, the sub-hierarchy is created under this “master” process map.

Graphical interface

The Process Mapper is an add-on that allows the user to create a process with dependent tasks.

This add-on is divided into 3 main zones as shown in the screen shot above:

  • The first (1) zone is the control panel. You can manage the process map using these controls.
  • The second (2) zone is the work-space. Using this area you manage your task hierarchy and create dependency links between them. By selecting a specific task (click the task box) the details of that task are shown in the third (3) zone.
  • The third (3) zone shows the details for the selected task. This area contains two specifics areas (shown as 4 & 5 in the screenshot):
    • The area 4 is used to show the variable mapping and shows the linkage to variables of previous tasks.
    • The area 5 shows the execution environment details for this task.

1. Task bar

This area is made up of several buttons:

  1. Open a process map
  2. Create a new process map
  3. Edit the process map properties (Name/Description/Tags/Wiki)
  4. Save the current process map
  5. Save as a new process map
  6. Save the process map as a TEMPLATE, that can then be shared through projects and teams
  7. Open the Task Monitor to drag and drop tasks into the process map
  8. Open the Application Management to drag and drop tasks into the process map
  9. (Clone all) Duplicate the process map: this action create a new process map by duplicating all tasks of the current process map
  10. Submit all the tasks in the process map

2. Workspace Area

In this area, you can add some tasks already create from the Task Monitor or some new tasks from the Application Management. To do this, you have buttons in the upper task-bar:

  • Application Management :
  • Task Monitor:

When you have opened the Task Monitor or the Application Management, you just have to drag an item and drop it in the work-space area to add the (new) task.

You can do lot of actions from the task by the contextual menu:

1: Open the Task Details window for the task.

2: Open the Data Monitor window for the task.

3: Open the File Explorer at the task run directory.

4: Select/Unselect the task.

5: Display the task details in the area 2.

6: Create links between selected tasks by order ().

7: Remove links between selected tasks.

8: Edit the task information.

9: Edit the task throw the application.

10: Submit the task.

11: Remove the task from the work-space.

12: Clone all the taks from this task to the deeper dependencies tasks, but stay within the current process map.

3. Details Area

In this area, you have all information from the selected task.

  • Task icon ()
  • Task name (Broadcast [4])
  • Task status (REGISTERED)
  • Task description (Calculation of the weather…)
  • Task application (Job Submitter) + Application wiki page button ()

You have 2 specific areas to customize the task input and to see the execution environment:

  • Mapping field
  • Execution environment field

Then, you have the possibility to see the wiki page of the task or create it if it doesn't exist with the button at the bottom:


4. Mapping Area

In this area, you can use the results (outputs) from previous tasks linked with the actual task to an entry value of the actual task (input).

To select the output, press to help you to select a good mapping.

A context menu appears to select items.

The first item is the tasks from that you want take the output.

In case of multiple tasks are linked to the current, you will have multiple choice in the contextual menu.

After having selected the task, you have to select the output that you want use for the mapping.

The list of all the output appears.

And then you can add an operator or select an other output or set a value to complete the mapping.

In this example, the Broadcast task input is the output of the Wind task (to know the force of the wind and then broadcast the information).

You can select the execution environment with the field Environment. You have the choice between the environment from the linked tasks or with its own environment.

In this example we have for the Broadcast task the same execution environment as the Wind task.

5. Execution environment Area

In this area, you can see the execution environment of the selected task.

You can see the information about:

  • The execution cluster (rnd01)
  • The associated project (Wheater News)
  • The associated accounting (Production)
  • The run directory (/home/broadcast_user/run)