Pattern Configuration nodes
Patterns support having configuration that allows the behavior of the pattern to be modified without needing to learn and edit TPL. This data is stored in one or more Pattern Configuration nodes that are related to a Pattern Module node. As a pattern's configuration cannot be pre-determined, the default list of attributes for a Pattern Configuration node is limited to generics.
Pattern Configuration node lifecycle
The following section describes the scenarios in which a Pattern Configuration node is created, updated or removed.
Creation
Pattern Configuration nodes are created as a result of activating a Pattern Module that contains a configuration block. As such the creation of Pattern Configuration nodes is driven by the management of Patterns. See Knowledge management for details.
Update
The update of a Pattern Configuration node is driven by the User modifying the attributes in the UI.
Removal
Pattern Configuration nodes are removed when their associated Pattern Modules are destroyed.
Attributes and relationships of the PatternConfiguration node
The attributes of the PatternConfiguration node are described in the following table:
UI Name | Description |
|---|---|
Name | Pattern configuration name |
Pattern Configuration Version | Pattern configuration version |
Pattern Configuration Description | Pattern configuration description |
Not shown in UI | Flag indicating if configurtion is active |
Not shown in UI | List of name for configuration values |
Not shown in UI | Number of non-default values |
The relationships of the PatternConfiguration node are described in the following table:
UI Name | Relationship | Description |
|---|---|---|
Deprecated Pattern Configuration |
| Pattern Configuration that has been deprecated by this one |
Deprecating Pattern Configuration |
| Pattern Configuration that deprecated this one |
Pattern Module |
| Pattern Module |
Comments
Log in or register to comment.