Grouping relevant configData together - config data sets explainedA config data set (CDS) is a normal node in the data model that has a special "flag" to indicate that it groups together a set of relevant configData items. All configData at that node and to any of the childNodes and includedNodes below it are now managed together as a single data set. If the incoming data is impacting any of the items in the data set, then SWEAGLE will track it as a change to the data set with a pending snapshot and stored snapshots under full life cycle control. Example In the example screenshot there is a data model with the top-level node being the environment type (PRD for production), and there are 2 environments of that type (PRD1 and PRD2). By making the PRD1 node a config data set all configData is now grouped together at this node level. Any incoming changes for the configData at any level down in the tree will now be automatically captured and put under version control using the snapshot concept of SWEAGLE. Other tools can consume data through the SWEAGLE API by simply referring to the CDS name and providing an exporter with arguments. All assigned validation policies to this CDS will be automatically triggered whenever there is incoming data that impacts anything in this data set. How to create a config data set A user with EDIT permissions for that node will: open a data change set (or scope into an existing one)navigate to that node in the data modelfrom the node menu (top right), select "create config data set) and enter a name. The default is the nodeName but it can be any other unique name. SWEAGLE recommends using the full pathname as it is unique and simple to follow. The config data set name appears alongside the node once a node is defined as a config data set. Select a node in the data model and in the node details panel on the right side, scroll down until you see that the node is included in the "config data set: <name>". When the user How to remove a config data set A config data set can be removed from the system. removing the config data set only removes the config data set and all of its snapshots. It will NOT delete the node itself in the data model. A user with EDIT permissions for the node to which the config data set refers to will: Open a data change set (or scope into an existing one)Navigate to "stored" and select the config data setIn the detail page select the menu button at the right side and choose "delete"Approve the data change set Note: This cannot be reverted. The config data set is completely deleted and all the snapshot data is removed from the system.