CPI Validation - CPILint
CPILint is a command-line tool used to validate SAP CPI IFlows against a predefined set of rules. These rulesets can include naming conventions, preferred mapping types, scripting technologies, and other best practices. When executed, CPILint analyzes the IFlows and reports any deviations from the defined ruleset, helping ensure consistency, maintainability, and high quality across all integration artifacts.
To validate a package:
Go to a required package in the Release Packages screen under Release Section and click Actions. Click Validate to start the validation process.
A pop-up dialog appears prompting you to select the appropriate SAP CPI target environment from the list.
After selecting the target environment, click the Validate button to initiate the validation process.
Validation Report
Validation report is visible only after the validation process is complete. To view the validation report:
1. Go to a required package and click Actions. Click Validation Report.
2. The validation report is displayed below.
3. Expand the artifact to view the details.
CPI Downgrade Check
This feature ensures that the correct user story is reused during a downgrade operation when a target version already exists.
How It Works
During a downgrade, the system checks whether the target version is already associated with a user story.
If a user story already exists for the target version, the system displays that existing user story.
After the downgrade validation is successful, the system reuses the same artifact-assigned user story.
The reused user story is displayed in the Target User Story column.
CPI Governance
The CPI Rules section in ReleaseOwl provides a centralized configuration interface to define and enforce governance policies and best practices for SAP Cloud Platform Integration (CPI) artifacts. These rules help ensure that integration artifacts comply with established security, coding, and operational standards across projects.
Design Guidelines Report
Under CPI governance, ReleaseOwl includes CPI Design Guidelines that are automatically validated as part of the validation reports. These guidelines consist of built-in rules and industry best practices designed to help developers build high-quality, standardized, and maintainable integration flows.
During the validation of CPI Design Guidelines, ReleaseOwl evaluates integration artifacts against built-in rules and best practices. These guidelines help developers create high-quality, standardized, and maintainable integration flows.
The validation generates compliance reports (Compliant / Non-Compliant) with defined severity levels (High, Medium, Low). The reports are accessible directly within the Integration Flow editor and provide actionable insights, including navigation to the affected steps.
Additionally, the reports reference recommended integration packages such as the CPI Cloud Exemplar to help developers learn and apply proven patterns for performance, security, and efficiency, ensuring consistent integration quality across projects.
Last updated