Overview #
The integration between Quality Clouds and Xtype enables organizations to establish a governed, automated, and quality-driven release process for ServiceNow.
By combining QC Livecheck with Xtype’s deployment orchestration, every update set is automatically verified before reaching production, ensuring only compliant and high-quality changes are deployed.
This collaboration delivers:
Continuous governance and quality assurance
Automated validation of every update set
Full visibility and traceability across the DevOps pipeline
Protection of production environments from non-compliant updates
Governance and Continuous Improvement #
This integration enforces a closed-loop governance model, where:
Every failure drives corrective action.
Every correction is revalidated.
Only compliant updates progress to deployment.
Through this automated validation process, organizations maintain consistent quality, faster releases, and complete traceability across ServiceNow environments.
Key Benefits #
Automated Governance: Quality validation becomes a built-in step in the release pipeline.
Full Traceability: Direct access to QC reports ensures auditability and transparency.
Quality Assurance: Blocks non-compliant updates automatically.
Efficiency: Avoids redundant validations and accelerates safe releases.
Use Case Example #
At the core of this integration’s use case, lies Quality Clouds Livecheck, which performs automated code and configuration analysis for ServiceNow update sets.
Xtype leverages this capability to enforce release policies, ensuring that any update set failing QC standards cannot proceed to deployment.
How It Works
When a deployment is initiated in Xtype, the system checks whether the update set has a valid QC Livecheck record.
Based on the result, Xtype decides whether to continue, rerun the check, or block the deployment.
Each step is fully traceable, with direct links to the QC reports for transparency and auditability.
Note:
This integration is flexible and customizable — each organization can adapt it to their internal release governance model.
The following workflow and examples illustrate one possible use case of how Quality Clouds and Xtype can work together.
Use Case Workflow #
In this example, the deployment workflow includes two scripted steps that enable continuous governance and automated validation through Quality Clouds:
1. Quality Clouds Verification
This step checks:
Whether a Livecheck has already been executed for the update set.
The outcome of that check (Passed / Failed).
Action Concept:
If the update set already passed a Livecheck, Xtype can skip revalidation to save time in the deployment process.
If no Livecheck is found or if the last result failed, Xtype proceeds to the next step.
2. Quality Clouds Livecheck Execution
This step ensures continuous governance by triggering a new Livecheck when needed.
Xtype executes the check through the QC integration.
The system waits for the QC analysis results.
A direct link to the QC report is displayed in Xtype for review and traceability.
Action Concept:
Automatically verify update sets before promotion, ensuring compliance with quality and governance standards.
Use Case Outcome
#
Scenario 1: Update Set with Passed Livecheck
The update set already has a successful QC validation.
Xtype detects this and skips redundant validation.
The workflow proceeds automatically, providing a link to the QC report for reference.
Outcome:
Deployment proceeds smoothly, saving time while maintaining compliance.
Scenario 2: Update Set Without Livecheck
Xtype identifies that the update set has no existing QC validation.
It automatically triggers a new Livecheck, waits for the results, and continues once it passes.
A link to the QC report is made available for audit and review.
Outcome:
Validation is enforced automatically, ensuring no unchecked code is deployed.
Scenario 3: Update Set with Failed Livecheck
The update set previously failed a QC validation.
Xtype initiates a secondary Livecheck to confirm the failure.
If the issue persists, the deployment is automatically blocked.
The verification step includes links to both failed and retried QC reports for analysis and correction.
Outcome:
The deployment is halted until issues are resolved and the update set passes QC validation.
This ensures that only compliant and high-quality updates progress through the release pipeline.
