Repository

Repository

External resources like masks, searches and variables are managed in the repository. That information is relevant for implementation modeling.

The repository offers an overview of the masks, searches and variables used in the implementation process and allows their editing. A selected mask can e.g. be opened and modified via the Edit button in the GUI builder. Similarly, selected searches can be edited via

.

Masks and searches

Masks and searches can be added to a process from another process. A change of these masks or searches will trigger a verification of its use in other processes. This verification process may cancel the editing. When a mask or search is edited and saved, then all relevant data in the process is marked with that change, i.e. the changed data will also be visible in the change log.

Any elements added to the process can also be removed again via the context menu.

Searches and masks from the CURSOR standard or a partner module can be overloaded independently of the process. At the time of deployment, the definition is loaded from the top-most customizing layer. The removal of an overloaded search or mask will reset the process to its original state.

In addition, you can copy the name of the selected entry to the clipboard via the context menu in order to insert it afterwards comfortably into BPM scripts.

Variables

Variables can be defined for the process, which will then be easily accessible in scripts via auto complete. A new variable is created via Add variables.

In addition to a name and description, each variable has a data type. Variables of type Object can be used anywhere. The data type somewhat restricts where a variable can be used: primary keys, for example, are required for the selection of datasets. This variable can, however, have the wrong data type assigned. A correct type assignment cannot be guaranteed during compilation or at runtime in the BPM script. IContainer allow the synchronization of data between the process and the CRM system.

The use type is an important factor for the definition of input and output variables in sub processes. The default is process-internal.

Incorrectly created variables can be post-edited via the context menu in the tree node. The name of a variable must only be changed if the variable is not yet in use. Superfluous variables can be removed via the context menu.

These variables can be selected e.g. via auto complete in script tasks (shortcut CTRL+ SPACE BAR).

That is how process variables are registered. Any typing errors are prevented.

Global variables are special variables for the distribution of customizing packages, which are defined in CRM (Admin console/Customizing/Global variables) and used in the process. They can differ in test, approval and production systems. Variable settings used in the process can be configured differently for production and test systems without having to adjust the process. Global variables will only be available after the system has been relevantly configured. Please contact your consultant.

A data type can be explicitly assigned to process variables in the repository. This will enhance process quality, because the type compatibility will be checked when the variable is assigned in a sub process. The use of a specific data type furthermore allows additional functionalities, e.g. the automatic data synchronization for variables of type IContainer. The variables are preassigned with the data type Object. The data type of a variable can also be changed in retrospect. The data type of a variable is displayed in auto completion, in the repository and in the variable drop-downs. User tasks requiring a primary key will only allow the addition of variables of type PrimaryKey. Existing processes and process variables can be used without the need for any changes.

A script variable can, however, be assigned an incorrect data type. Correct type assignment cannot be guaranteed during compilation or at runtime in the Groovy script.

You can use a variable of type IContainer in the implementation model in the following elements in the following way if you have defined the property "Auto synch" in the repository:

• User task, there "Detail mask": "Update automatically" (default: active) and/or "Auto save" (default: active).

• Message intermediate in event: "Update automatically" (default: active)

• Timer intermediate event: "Update automatically" (default: active)