This section is meant to give an overview over the configuration and setup options in CDCM, especially when starting from a fresh deployment or with a fresh space. So this page can be seen as a starting point or checklist that covers (on a surface level) all configurations that need to be made in order to use the core functionalities of CDCM. The detailed documentation on the different sections are linked.
Configuration Needed for Core Functionality
Bare minimum
In order to use the very basic functionalities of creating units in different configurations that can reference other units the following steps have to done.
Create concept types for configuration items, configurations, units and configuration areas. It makes sense to do it in this order so that the associated types can be set directly during creation of the type.
Create a configuration area and enable at least one unit type in it by adding it to the “Associated Unit Types” list.
Create at least one configuration area scoped role that has the necessary permissions and assign that role in your identity provider.
After that it is possible to create units with multiple configurations which then can have configuration items that reference other configurations.
Expand a concept type for more functionality
The previously created concept types can be configured further so the concepts can hold more information and have more functionality.
To do this the following sections in the administration area are relevant:
Properties - the smallest unit to hold information in a concept. Different customizations can be made.
Complex properties - can hold multiple different properties that logically belong together (e.g. a complex property called “project member” might hold the properties “name”, “email-address” and “project responsibility”)
Master data table - tables of static data that can be displayed in properties and managed independently from the units
After creating properties and complex properties the concept types can be tailored to the needs of the users by selecting a concept type and configuring it via the sections listed below to (see here for detailed information):
Meta definition - chose which properties and complex properties should be part of this concept
Header/Details UI - configure the UI that is shown when a instance of this concept type is viewed by a user in CDCM
Delegated UI - configure the UI that is shown when a delegated UI of a concept is shown in another application
Calculated fields / Guard script - here it is possible to define custom JavaScript code add more functionality to the concepts (see here for detailed documentation)
State model - configure which states this concept can have and define the transitions between them
Add additional storage locations to a configuration area
One important feature of CDCM is the integration of different authoring tools like codebeamer or sharepoint online. These integrations are called storage locations in CDCM and can be individually managed.
The following two steps are needed in order to use these integrations and create references to objects directly in those external tools:
Create and manage them in the “storage location” administration section
Enable them for a configuration area by adding them to list of storage locations in the configuration area detail view
Add Comment