CMDB Page Layout Extension
Cloudaware CMDB ships with standard page layouts and Lightning record pages for common CMDB objects (accounts, instances, virtual machines, applications, and so on). In many environments, administrators want to add fields, sections, or related lists to these layouts so that teams see the most relevant information for their workflows.
This guide explains how to extend standard layouts safely using Salesforce customization.
What You Can Change
A standard layout includes such components as tabs, tiles, and sections. The Related CIs related list is located within the tabs.
- Reorganize fields and sections – group related fields together (for example, ownership, environment, security posture) or add new sections for custom attributes.
- Expose custom fields – surface custom CMDB fields, calculated attributes, or enrichment fields on the CI detail page.
- Add related lists – show related objects (tickets, incidents, vulnerabilities, backups, applications) that are important for your process.
- Tune quick actions – adjust actions and buttons that appear on the record (where allowed by profile and package configuration).
Core Cloudaware‑managed fields and relationships should remain on the layout so standard workflows, reports, and modules continue to function as designed.
How to Customize Layouts
Layout extensions for CMDB objects are managed from within the Cloudaware UI using the Layout Editor:
- Log in to your Cloudaware account and open CMDB Navigator.
- Select an object type (for example, AWS EC2 Instances) and open any CI record from a list view.
- In the upper‑right corner of the CI record page, click the three‑dot menu (⋮) and choose Edit Layout Extension to open the Layout Editor.
- In the Layout Editor, add or update the JSON that describes your layout extension.
- Click Validate to check the JSON. If validation succeeds, click Save.
- Click Close Editor → OK, then click Refresh layout on the CI page to see the changes applied.
The Layout Editor JSON is evaluated on top of the standard layout, so you can extend the layout with additional sections or configuration without replacing the underlying Cloudaware‑managed layout.
JSON Examples
The Layout Editor accepts JSON that describes how to extend the standard layout. The concrete schema may evolve; treat the examples below as patterns rather than a strict contract.
Example: Add a Custom Section
1-row 1-column section
The first example adds a Custom Fields section after CI Record Information on the Details tab, with a single column that shows the Environment__c field:
{
"sections": [
{
"name": "Custom Fields",
"after": "CI Record Information",
"tab": "details",
"rows": [
{
"columns": [
{
"field": "Environment__c"
}
]
}
]
}
]
2-row 2-column section
The second example adds an Application Details section after Special Fields on the Details tab, with two rows and two columns (Application ID and Cost Center in the first row, Contact and Line of Business in the second):
{
"sections": [
{
"name": "Application Details",
"after": "Special Fields",
"tab": "details",
"rows": [
{
"columns": [
{
"field": "Application_ID__c"
},
{
"field": "costCenter__c"
}
]
},
{
"columns": [
{
"field": "contact__c"
},
{
"field": "lineOfBusiness__c"
}
]
}
]
}
]
}
Example: Add a Custom Tile
{
"infoBlocks": [
{
"name": "Blended Cost",
"after": "IDS",
"tab": "details",
"field": "CA10__mtdBlendedCost__c"
}
]
}
This example adds a custom tile 'Blended Cost' to the AWS EC2 Instance record layout.
Example: Add a Related List
{
"relatedLists": [
{
"childRelationship": "CA10__Azure_Virtual_Machine_Fact__r",
"recordType": "caAzureVirtualMachineFactRm",
"tab": "details",
"columns": [
{
"field": "CA10__caUuid__c"
}
]
}
]
}
To find the childRelationship name for a related list, open Setup → Object Manager → select the parent object → locate the lookup to the child object → inspect the Child Relationship Name. For Cloudaware‑managed package objects, prepend CA10__ and append __r (for example, a Child Relationship Name of Azure_Virtual_Machine_Fact becomes CA10__Azure_Virtual_Machine_Fact__r). For custom, non‑package objects, append only __r.
In real layouts, you can combine multiple sections, tiles, and related lists in a single JSON document. Always validate your JSON in the Layout Editor before saving.