Generic Element node

The GenericElement's main role is for rapid prototyping of TPL patterns where the default BMC Discovery taxonomy does not already contain a more suitable node kind.

As the GenericElement is available by default, TPL can create it as required without needing to extend the taxonomy. For this reason there are few defined relationships; it is impossible to anticipate what will be needed.

It is recommended that the type attribute is set, so that the nodekind is logically sub-typed for multiple concurrent uses.

Once prototyping is finished it is expected that a more specific nodekind and associated taxonomy extension is considered.

Generic Element node lifecycle

The following section describes the scenarios in which a Generic Element node is created, updated or removed.

Creation/update

This is under the full control of patterns and as a result there is no default Generic Element node behavior.
 The generated key for a Generic Element node is entirely dependent on the pattern that creates the Generic Element node.

Removal

A Generic Element node can be destroyed in one of the following ways:

• Manually, by selecting the necessary Detail node, and picking Destroy from the Actions list.
• Explicitly by the pattern that created it. See Removal in the Pattern Language guide
• When the last related Inferred node that is linked to the Generic Element node is removed, so will the Generic Element node. This is a Cascade Removal type, see Cascade Removal.

Generic Element node attributes

The attributes and relationships on a Generic Element node are described in the tables below.The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.
 

Generic Element node relationships

The relationships on a Generic Element node are described in the table below.The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.