Handler - AutoEntityCreation
AutoEntityCreation handler creates a new data card automatically when a data card containing an attribute with AutoEntityCreation handler is created. (Please note that similar functionality can also be implemented with a listener.)
Uniqueness check is ignored for attributes that are included in an automatically created data card.
An automatically created data card is created on a template that is denoted by its template code in the metadata of the parent attribute. Also, attributes that are included in an automatically created data card must be denoted by their attribute codes in the parent attribute's metadata. Hereby, the attribute values that an automatically created data card gets are fetched from the parent data card according to the attributes that are denoted in the parent attribute's metadata. It is possible to create more than one data card automatically, as long as they base on different templates.
In order to succeed in creating a parent and an automatically generated data card, the creator must have the Create permission to both templates.
The folder where the automatically created data card is created to can be specified in the parent attribute's metadata. If the folder is not specified, an automatically created data card is located in the same folder as the parent data card. If more than one data card is created automatically, they can be created into different folders.
The user has to have a Create permission to the folder to where the data card will be stored.
If the parent attribute's data card is reference, the attribute references to the automatically created data type. Remember to define attribute as multivalue, if you want to create more than one datacard automatically. Otherwise all the cards are created, but only one of the cards is referenced.
AutoEntityCreation handler metadata:
For example, when you create a new server, you can use AutoEntityCreation handler to create a system-monitoring data card simultaneously.
To function as intended, one template should have only one AutoEntityCreation handler at a time. If a template includes more than one attribute with an AutoEntityCreation handler, the one that functions is selected at random.
The following tables provide information on the attribute settings and metadata requirements for AutoEntityCreation handler. Compulsory metadata is provided in a Required attribute metadata table including proposals for possible metadata values.
Table 1. Attribute Settings
| Handler name | Datatype |
|---|---|
AutoEntityCreation |
String or Reference |
Table 2. Required Attribute Metadata
| Name | Value | Description |
|---|---|---|
templateCode |
attributeCode |
In the
In the
Notice that you can define multiple template codes, each in its row. |
map_templateCode_attributeCode |
attributeCode |
In the Name field, replace templateCode with the code of the template, on which you want to base the automatically created data card. Again, in the Name field, replace attributeCode with the code of the attribute you want to include in the automatically created data card.
In the |
Table 3. Optional Attribute Metadata
| Name | Value | Description |
|---|---|---|
folder_templateCode |
folderCode |
Defines the folder where the automatically created new data card is created. (If this metadata is not configured, the new data card will be created in the same folder as the parent data card).
In the
In the |
Table of Contents