Data Content Manager can be used to define data models to be used in ServiceNow. Those data models are also called “Blueprints“. And a blueprint basically includes:
- Selected data classes or tables as “containers”
- References and relationships between the containers as “links”
- And “filters” to define the data content per container in more detail.
Combinations of containers, links and filters will create a blueprint. So, one could say that these are the elements of a blueprint.
In Data Content Manager application these Blueprint elements are considered “global”, meaning for example that a single class used in multiple blueprints is a single Blueprint element, used by multiple blueprints. Same applies to links, a “Managed by” reference between a Business application and a User is also a single element that can be used in many different blueprints.
What can you do with Blueprint elements?
We introduced Blueprint elements in DCM release 3.3. And we are currently developing more features that utilize the elements. But already now, blueprint elements can be used for grouping audit results. This alone can be a very powerful thing.
The feature image of the post is showing an example blueprint related to Application CI class. And on the right side of the picture we are showing audit results against that blueprint grouped by Blueprint elements (instead of Audited records).
In the later releases we are showing and using these elements in the Blueprint Designer to identify where and how different elements are being used. And also used to identify “unique audit messages” from different audits to simplify the remediation process.