Best Practices for Managing Multiple Versions and Bug Fixes in ServiceNow Plugins
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-08-2025 12:05 AM
Hello everyone,
I am currently working on a ServiceNow plugin, and I’ve encountered a few questions related to managing multiple versions (such as 2.x and 3.x) and handling bug fixes for older versions after newer ones have been released. I would appreciate any guidance or best practices from the community.
Here are my questions:
Is it possible to develop and release bug fixes for a previous version (e.g., 2.x) after releasing a newer version (e.g., 3.x) in ServiceNow?
How do I manage multiple versions (2.x and 3.x) of a plugin in ServiceNow without conflicts?
What steps should I take to ensure backward compatibility when developing bug fixes for 2.x while working on 3.x?
Can I submit a patch for an older version (2.x) to the ServiceNow Store after releasing 3.x?
What’s the process for submitting bug fixes for 2.x to the ServiceNow Store after the release of 3.x?
Thanks in advance for your help!