Navigation:  Task library > Custom task library

In the settings under the Storage locations tab, directories for custom task libraries can be linked (see chapter Menu bar / Options / Settings / Storage locations). This requires the linking of an appropriately structured folder structure, which contains the user-defined tasks as individual ema simulations, with an associated *.csv file (“imk_ema_library_tasks_content”). Each user-defined task must be saved in an individual ema simulation. The *.csv file is created using the command Create content file for resource library (see chapter Menu bar / File). A training scenario on this topic can be found in the ema Academy.

 

Structure of the content file (*.csv)

 

In the *.csv file, a unique identifier for task groups (category headings) is assigned via the Resource_Path column and the paths (starting from the point at which the *.csv file is stored) are linked to the individual ema simulations for the individual tasks. A preview image can be integrated under Preview. The Parameters column describes the type of parameter (in this case “Tasks”, i. e. tasks) and Versions describes the version of the task.

 

The name of the category or task is entered in the default (for English names) or de-DE (for German names) column. In the example table below, the first two rows are categories, namely the category “User-defined complex tasks” and “1st example category”, which is why these do not require any further description from the following table columns.

 

In the default|description or de-DE|description column, the English or German description of the content of the 1st example action is stored. This and the following descriptions can then be displayed by pressing the F1 key in the same way as when calling up help.

 

Additional explanations can also be stored in this column, which are then displayed in a tooltip in the library and also taken into account when displaying the search results. To do this, the explanation must be entered in the corresponding designation field, separated by a “|” after the respective designation.

 

The default|start or de-DE|start columns can be used to describe the starting point at which the activity of the task begins. The content of the activities can be described in the default|content or de-DE|content columns. The end point of the task can be described in the default|end or de-DE|end columns.

 

Figure 192: Example of a *.csv file of a user-defined task library