The Code Monitor view in Quality Clouds allows Architects and platform teams to compare the code of two instances—or two versions of the same instance—side by side. This makes it easy to track changes over time, validate deployments, and understand how development assets evolve across environments.
Perfect for reviewing code consistency and ensuring that what you deploy is exactly what you expect.
Benefits
#
The Code Monitor view helps teams:
- Compare code between instances or versions with clear side-by-side visuals.
- Identify differences across apps, CEs, and lines of code with automatic highlighting.
- Validate consistency before deployments, reducing errors and rework.
- Track development evolution over time across environments.
- Increase governance and improve release confidence.
It is especially useful for Architects, Admins, Customer Admins, and Project Users who need visibility into code movement and environment parity.
What It’s Used For
#
Use the Code Monitor view to:
- Confirm that lower environments match production before promoting updates.
- Understand growth in configuration elements and development assets.
- Detect unexpected changes or missing components.
- Compare the same application across two different instances or time periods.
- Catch environment drift early.
This view strengthens release management and ensures smoother deployments.
What the View Shows
#
In a simple side-by-side comparison, you can view:
- Instance selection, target environment, and scan date
- Version and patch details
- Lines of code scanned
- Inventory metrics: Apps, New CEs, Total CEs
- Application-level filters
- Detailed configuration elements comparison
Highlighted differences between versions or instances
All differing CEs are automatically marked to simplify analysis.
How to Use It
#
- Open the Code Monitor view and select the target environment and scan date.
- Choose the applications you want to compare.
- Toggle Highlight differences to instantly surface discrepancies.
- Filter by All, Active, or Inactive elements to refine your analysis.
The view requires at least two scans or two environments to generate comparisons.
Use Case
#
Before deploying to production, compare your test and production instances to confirm they match. Any unexpected differences are instantly highlighted, ensuring a smoother and safer release.
