Configuring CMDB Workspace

Plan and configure your implementation of CMDB Workspace.

Configuration overview

1. Set up CMDB Workspace

   Request the store app and enable demo data.

2. Configure any of the following options to show the most relevant data in your organization:
   • Modify important actions on the Home view of CMDB Workspace
   • Add a quick link to the Home view of CMDB Workspace
   • Configure datacenters for Cloud vs Non-cloud resources in CMDB Workspace
   • Configure classes for Cloud vs Non-cloud resources in CMDB Workspace

• Set up CMDB Workspace
  Set up and access the CMDB Workspace store app.
• Modify important actions on the Home view of CMDB Workspace
  Modify the appearance order and other properties of the important action cards that appear on the Home view of the CMDB Workspace.
• Add a quick link to the Home view of CMDB Workspace
  For an immediate access to tools or data that you need, add your own quick link to the Home view of CMDB Workspace.
• Configure datacenters for Cloud vs Non-cloud resources in CMDB Workspace
  The Cloud vs Non-cloud resources chart in CMDB Workspace determines which CIs and application services are stored on a cloud and which aren't in the organization. In addition to base system classifications, you can add cloud versus non-cloud classifications that reflect specific datacenter deployments in the organization.
• Configure classes for Cloud vs Non-cloud resources in CMDB Workspace
  Include or exclude pairs of CI Class/Type in the Cloud vs Non-cloud resources chart that appears in CMDB Workspace.
• Request additional attributes for new CIs
  Integrate a request for specific CI attributes when manually creating a new CI in your workspace. Then, when creating a new CI in the respective workspace, users can enter values for the requested attributes, as appropriate for the new CI.
• Limit the class list for new CIs created in a workspace
  Limit the selection of classes for a new CI being manually created in your workspace, to only those classes that are relevant to that workspace. When then creating a new CI in the respective workspace, users can only select a class that is authorized as an option.