Skip to main content

Reports (Salesforce UI)

Cloudaware runs on the Salesforce platform so that you can use built-in Salesforce Reports to create tabular, summary, and matrix reports on CMDB objects. This guide explains how to build reports on CMDB data in the Salesforce UI.

When to Use Salesforce Reports​

Use Salesforce Reports when you need to:

  • Create tabular or grouped views that go beyond a single CMDB list view.
  • Aggregate CMDB fields with counts, sums, averages, or other summaries.
  • Share scheduled report emails or subscriptions with stakeholders.
  • Create report-based dashboards for CMDB data.

For ad‑hoc scoping and exploration, start with CMDB list views and the Browse Objects feature. Use Salesforce Reports when you want to formalize and share those insights.

Access Reports in Cloudaware​

  1. Log in to Cloudaware.
  2. From the top‑right, open the App Launcher → Reports & Dashboards.
  3. Click New Report (Lightning view) or open the Reports tab (Classic views) to start building a report.
tip

Depending on your tenant configuration, you may see the Lightning report builder or the Salesforce Classic report builder. Both can be used with Cloudaware CMDB objects.

Select a Report Type​

The first step is selecting a report type, which determines:

  • The primary CMDB object (for example, AWS Accounts).
  • Any related objects that can be joined in the same report (for example, AWS S3 Bucket).
  • The fields available for columns, filters, groups, and summaries.

For example, to report on AWS accounts and their related S3 buckets, search for the report type AWS Accounts with AWS S3 Buckets. Use the All category if you are not sure where the report type is listed.

Build Reports in Lightning View UI (Enhanced)​

Use the Lightning report builder for new reports when it is available.

After you choose a report type, click Start Report. The steps are the following:

  1. Add columns:
    • In the Outline panel on the left, use the Columns list or search bar to add fields as columns (for example, Account Name, Region, Environment, Owner, Coverage flags).
    • Use drag‑and‑drop to reorder columns.
  2. Add filters:
    • In the Filters panel on the left, add conditions on CMDB fields (for example, Environment = Production, Region = us-east-1, Backup Coverage = False).
    • Use filter logic (AND/OR) to model more complex conditions.
    • In Show My/Time frame controls, choose whether to see all records or a subset (for example, All AWS Accounts, All EC2 Instances created in the last 30 days).
  3. Group and summarize:
    • In the Outline panel, under Groups, pick fields such as Account, Region, Environment, or Application to create row (and optionally column) groupings.
    • Add summaries (COUNT, SUM, AVG) on numeric fields (for example, number of instances per account, total cost field if available).
  4. Run and refine:
    • Click Run to view the report in full.
    • Adjust columns, filters, and groupings as needed, re‑running until the report matches your requirements.

Click Save to store the report in an appropriate folder (for example, a CMDB or Operations folder with shared access for your team).

Build Reports in Classic View UI (Legacy)​

The core steps are the same:

  1. Open the Reports tab and click New Report.
  2. Select Other Reports in categories on the left.
  3. Choose a report type (for example, AWS Accounts with AWS S3 Buckets) and click Create.
  4. Use the fields list on the left to add or remove columns.
  5. Use the Filters pane to define criteria (fields, operators, values, and filter logic).
  6. Run the report, then save it to a folder.

If both UIs are available, prefer the Lightning report builder for new work; it offers a richer experience and better integration with dashboards.

From CMDB Views to Salesforce Reports​

CMDB list views and queries are often the starting point for report design:

  • Use a list view or Browse Objects to prototype the filters and columns interactively.
  • Once the scope is clear, recreate the key filters and fields in a Salesforce report on the corresponding CMDB objects.
  • Use report summaries and groupings to add roll-ups that list views do not provide.

This approach keeps report logic aligned with how teams already filter and tag data in CMDB.