Support & FAQs
We’ve gathered the most asked questions to make your experience smoother.
1. Where do you store the credentials?
Credentials are stored in a credential manager section on the administration page. Only the user who created the credentials can view them.
2. How do we handle user permissions in ReleaseOwl?
User permissions are managed through roles. Specific roles can be assigned to users, defining their access levels and permissions within the project.
3. Can the same environment be connected to different projects?
Yes, the same environment can be connected to multiple projects, allowing for flexible management of deployments across various projects.
4. Can we create projects and pipelines based on regions?
Yes, you can create different projects for different regions and specific pipelines for each project.
5. Can we create a role for notifications and assign it in the release pipeline?
Yes, notifications can be customized based on roles or specific components, and you can define which users or roles receive notifications at different stages of the release pipeline.
6. Can we update credentials via API instead of manually through the web page?
Currently, this is not supported. However, we can consider it based on requirements.
7. What is the difference between Call Out and RO Agent?
Call Out is used to call an external system, while RO Agent is used to trigger testing tools like UI Path, Tosca, HCLOne Test.
8. What is the flexibility with critical objects?
In the event of modifications to critical objects maintained in Transport Management, you will receive a warning indicating that a critical object has been altered. Only modified critical objects added to the transports are identified as critical and not the modifications made to the object using the critical object.
9. How is static code analysis performed using ATC?
ATC checks are set up in the SAP backend; only the variant is used to check the source code from ReleaseOwl.
10. Is Object Key level conflict possible in ReleaseOwl?
It needs to be checked with the ReleaseOwl team.
11. Is retrofit possible for customizing?
Yes.
12. Is conflict identified at the object level or granular key level? Are there any limitations?
It is identified at the object level, not at the key level.
13. What HANA monitoring capabilities are available in ReleaseOwl?
ReleaseOwl provides rudimentary monitoring capabilities for HANA DB.
14. Are custom checks like Code Inspector available?
Yes, they are run in the background and shown in the validation report.
15. Is this platform for developers or admins?
ReleaseOwl is designed to be used by both developers and admins.
16. Is there any customization possible in ReleaseOwl?
No, since it is a no-code tool, customization is not possible. However, enhancements can be done based on customer requests.
17. How will the integration with ITSM be handled?
ReleaseOwl has a callback framework to integrate with external systems. Brigade informed that they are using Freshdesk as their ITSM tool.
18. What kind of user roles and permissions can be configured in ReleaseOwl?
ReleaseOwl allows for role-based access control, where different roles can be assigned to users, such as developer, QA, and manager roles. Permissions can be set to control who can create, import, or approve transports and changes.
19. Can a developer schedule on-demand releases using the ReleaseOwl platform?
Yes, developers can schedule on-demand releases in the ReleaseOwl platform. The platform provides flexibility to trigger releases manually or schedule them according to specific business requirements.
1. If an artifact is not deployed in QA, does it copy the configurational parameters from dev and deploy?
Yes, the system will indicate if an artifact is not deployed in QA and will copy the parameters from development.
2. How does ReleaseOwl handle Docker image management and deployment to public clouds?
ReleaseOwl primarily supports SAP deployments. Custom requirements can be discussed based on specific needs.
3. Can ReleaseOwl support deployments to multiple systems like two production systems?
Yes, it supports deployment to multiple systems.
4. Is it possible to import transports to more than one system in the release pipeline?
Yes, ReleaseOwl supports importing to multiple landscapes (n+2).
5. How can different pipelines be used in ReleaseOwl, and who can change them?
Different pipelines can be defined for various release scenarios. Only users with the appropriate role-based permissions can select or modify the pipelines.
6. Can user stories from different ALM projects be included in a single release package?
Yes, as long as they are part of the same ReleaseOwl project.
7. How many pipelines are usually created for a customer?
Typically, 2 or 3 pipelines are created, depending on the customer’s needs.
8. Is it possible to deploy to multiple tenants in parallel?
Yes, by configuring the deployment process accordingly.
9. Can ReleaseOwl be deployed in our environment instead of your cloud?
The platform is primarily SaaS, but on-premises deployment can be discussed further.
10. If we add a system while registering an environment that is not present in STMS routes, can TRs be moved to the added system?
No, it is not possible since transport routes are not set up.
11. Can you move TR between different ReleaseOwl projects?
Yes, it is possible.
12. How will you move the retrofit TRs to its own landscape?
You can sync the transports in the project associated with the retrofit landscape and move across systems using the release pipeline.
13. When will the TR be visible in retrofit?
Based on configuration, TRs will be visible on the retrofit screen.
14. Can we select multiple TRs to retrofit?
No, only a single transport can be retrofitted at a time.
15. Can you assign the same landscape to multiple projects?
Yes, it is possible.
16. Can you prevent developers from approving or importing their own transports?
Yes, it is possible.
17. What is the use of a custom component?
Components are used for the segregation of development. They can also be used to send approvals to people who are segregated based on development.
18. How is the sequencing of transports done?
An auto-sequence feature is available at the user story level. All the transports in a particular user story can be sequenced using this feature.
19. What happens if a transport fails during the deployment process?
The pipeline stops at the failed transport. Notifications are sent regarding the failure. The user story should be re-promoted, and all the transports will be imported again, ignoring the successfully imported transports from the previous execution.
20. Is there a way to automate the retrofitting process for transports?
While retrofitting usually requires manual intervention to resolve changes and merge conflicts, ReleaseOwl provides tools to facilitate the process. However, the actual retrofitting process may still involve some manual steps.
21. How are logical dependencies managed between user stories?
Logical dependencies are currently under development. Tagging user stories and transports to form dependencies is being worked on.
22. Is version comparison available for on-premise systems?
It is available for workbench requests only.
23. Can you modify a user story once it is promoted?
You cannot modify a user story after promotion. If the pipeline is stopped due to approval rejection or deployment failure, you can modify and promote it again.
1. What tools are supported for static code analysis, and can we integrate our own tools?
ReleaseOwl supports out-of-the-box integration with SonarQube. Custom tools can also be integrated.
2. Can you integrate multiple ALM tools like Jira, ServiceNow, etc.?
Yes, ReleaseOwl integrates with multiple ALM tools, including Azure DevOps, Jira, 4me, and ServiceNow.
3. How does ReleaseOwl handle integration issues between multiple landscapes like CPI, BTP, AWS, and GCP?
ReleaseOwl automates deployment on SAP BTP and handles integration issues across various platforms.
4. Will Change requests be created in the ITSM tool?
Yes, a callout task will create a change request based on configured parameters, and once approved, the pipeline will proceed.
5. Can any Git-based version control system be integrated?
Yes, any version control system can be integrated.
6. Are you connecting to the domain controller via RFC?
No, it is connected via HTTP or HTTPS.
7. Can CPI rules be created in formats other than XML, such as YAML?
Currently, only XML is supported.
8. Are ATC checks stored somewhere in your tool so that they can be checked later?
Yes, it is available in the validation report.
9. Can we run unit tests for ABAP Git or gCTS in CI/CD pipelines?
Yes, it is supported.
10. Can ReleaseOwl trigger GitLab jobs?
Currently, no, but it can be discussed further.
1. Can ReleaseOwl run a large number of test cases across multiple virtual machines?
Yes, it integrates with Tosca for this purpose.
2. How does the validation report handle old transports that may have been created a long time ago?
The validation report revalidates all transports at the time of execution, ensuring all changes are checked against the current environment.
3. Is there any validation for changes that are moved to QA before moving to Prod?
Yes, following standard SAP procedure, the import to Prod is not possible unless it's first in QA.
4. How are retrofit requests displayed in the retrofit section?
They are visible based on configurational settings.
5. How does ReleaseOwl handle retrofitting for multiple transports?
Retrofitting is managed through the conflict resolution screen, allowing users to resolve conflicts between parallel development landscapes.
6. Is it possible to mock test cases in ReleaseOwl?
Yes, this feature is under consideration.
7. How do you handle large transport validation checks without timeouts?
Validation checks are asynchronous to handle large transports efficiently.
8. Will ReleaseOwl consider changes like pretty printer or space as a conflict?
Yes, any modifications made to the object are shown as a conflict.
9. Can you send ATC reports to SonarQube?
Currently, it is in the backlog.
10. Can ReleaseOwl intelligently identify test scripts related to objects?
We have BPCA integration, which will create a test scope and can be utilized for testing.
1. Is ReleaseOwl certified by SAP?
Yes, it is certified by SAP and available on the SAP Store.
2. What is the duration for the implementation of ReleaseOwl?
Implementation typically takes about 40 hours.
3. Is ReleaseOwl native to SAP?
Yes, ReleaseOwl is 100% native to SAP.
4. How does ReleaseOwl replace existing SAP tools like CHaRM?
ReleaseOwl replaces CHaRM by offering comprehensive transport management, deployment sequencing, and impact analysis within a single platform.
5. Will it support Fiori objects using VS Code?
Yes, the build pipeline supports deploying Fiori/ABAP applications.
6. How can we ensure the latest version is deployed at the user story level?
A warning system can be implemented to ensure the latest version is deployed.
7. How can we track who deployed the changes In CPI Tenant?
A feature to add comments in the version history in CPI Tenant and track deployments is being considered.
8. How does ReleaseOwl handle multiple environments and clients in the deployment process?
ReleaseOwl manages multiple environments and clients by providing customizable deployment pipelines, environment-specific configurations, and gCTS integration for SAP landscapes. Its centralized platform ensures seamless monitoring, governance, and collaboration across all deployment processes.
