Create Entity Nodes in Policy Designer

A Create Entity node represents an action to create new records in any baseline or custom entity family. The fields in the new records are populated with the input values that you specify on the Properties window for the node.

The outputs of the Create Entity node are the following system fields for the records that the node creates: collectionA set of results from a Query node or a set of readings associated with input nodes such as Measurement Location, Health Indicator, or OPC Tag., Content GUID, and Entity KeyThe Entity Key output can be used in subsequent action nodes, such as the Create Relationship node, but will return a value of 0 if used in a calculation or a Return Value node, since the Entity Key is not available until the record is saved at the end of policy execution..

Node Properties

The Properties window for a Create Entity node contains the items that are described in the following table.

Item	Description	Notes
Family ID list	Specifies the type of records that the Create Entity node will create.	The Family ID list contains all of the baseline and custom entity families in GE Digital APM for which you have update privileges.
Site Key section	Specifies the Site Reference Key(s) of the site(s) to which the new records should be assigned.	You can select to specify the output of a predecessor node in this section.
Auto-map field values? option	Specifies whether you want to automatically map values from a collection to fields in the selected family.	When the values that you want to use to update a record are contained in a collection, you can use this option instead of, or in addition to, specifying the corresponding value for each field individually.
Field values collection section	Specifies the collection that contains new values for fields in the selected family.	This section is enabled only when you select yes for the Auto-map field values? option. The collection that you specify in this section is used to populate the fields in the created entity(s) for the selected family. In the records that are created, the fields that are populated are those in which the Field ID matches a Column ID in the collection. Any columns in the collection that do not match a Field ID are skipped.
button	Adds a new row to the Create Entity node.	Each row represents a field that you want to modify in the corresponding record(s). Note: If you are using the auto-map feature, you are not required to add rows to the Create Entity node, but you can use a combination of auto-mapped fields and individually specified fields if you want to. However, if the same field is specified by each method, the individually specified field takes precedence over the field from the auto-mapped collection.
Field column	Specifies a field in the selected family that will be modified.	Both baseline and custom fields will appear in each list.
Value column	Specifies the new value for the corresponding field.	You can select to specify the output of a predecessor node in this section. IMPORTANT: If a field has complex behavior defined by field-level rules (e.g., rules for valid values) and field-level behaviors, this behavior will not be reflected in the Properties window or detected by policy validation. Therefore, you are responsible for ensuring that the values you specify are valid according to any baseline or custom field-level rules for the corresponding field. If a field value is defined by a system code, the value that you specify in the corresponding section must be the system code, not the value that is displayed to the end user. If a field has a Unit of Measure (UOM), associated with it, you must specify the value using the base UOM in which your database stores the values.
button	Deletes the corresponding row from the Properties window.	None

Hint: Click here to see an example of this node used within a complete policy model.