Software Update Policy

1. Update Categories

RPTech Software Marketplace provides regular software updates to ensure that your software remains secure, stable, and feature-rich. Our updates are categorized into four distinct types, each serving a specific purpose in maintaining and improving your software experience.

Understanding these categories helps you plan for updates, manage your systems effectively, and ensure continuous operation of your business processes powered by our software solutions.

1.1 Major Releases

Major releases represent significant new versions of our software products with substantial new functionality, redesigned features, and architectural improvements. Major releases are typically designated by a change in the major version number (e.g., Version 1.x to Version 2.x).

• New modules, features, and capabilities
• Significant user interface redesigns and improvements
• Architectural changes for improved performance and scalability
• Database schema changes and migration requirements
• Breaking changes that may require code modifications in integrations
• Updated system requirements
• Comprehensive release notes and migration guides provided
• Typically released annually or semi-annually

Major releases may require separate purchase for perpetual license holders. Subscription and annual license holders receive major releases as part of their subscription. Enterprise license holders receive all major releases included in their agreement.

1.2 Minor Updates

Minor updates add new features, functionality enhancements, and usability improvements within the current major version. These updates are designated by a change in the minor version number (e.g., Version 2.1 to Version 2.2).

• New features within existing modules
• User experience improvements and workflow enhancements
• Performance optimizations and efficiency improvements
• New integrations with third-party services
• Additional reports, dashboards, and analytics features
• Updated documentation and help resources
• Typically released quarterly

Minor updates are included for all active license types with current maintenance or subscription coverage. No separate purchase is required.

1.3 Security Updates

Security updates address vulnerabilities and threats that could compromise the security of your data or systems. These updates are prioritized and released on an urgent basis as needed.

• Critical security patches (released within 48 hours of vulnerability identification)
• High-priority security updates (released within 1 week)
• Medium-priority security hardening (included in next scheduled update)
• SSL/TLS certificate updates and renewals
• Dependency and library security updates
• Security configuration improvements
• Released as needed, with no fixed schedule

Security updates are provided at no additional cost for all active license holders. We strongly recommend applying security updates as soon as they are available to protect your systems and data.

1.4 Bug Fixes

Bug fixes address defects, errors, and issues identified in the software. These fixes are prioritized based on severity and impact on business operations.

• Critical Bug Fixes: Emergency patches for issues causing data loss, system crashes, or security vulnerabilities. Released within 24-48 hours.
• Major Bug Fixes: Fixes for significant functionality issues. Included in the next scheduled update or released as a standalone patch within 1-2 weeks.
• Minor Bug Fixes: Fixes for non-critical issues. Included in regular maintenance releases.
• Regression Fixes: Fixes for issues introduced by previous updates. Released as hotfixes within 1 week.

2. Update Delivery

Software updates are delivered through the following mechanisms:

• Automatic Updates: For cloud-hosted and subscription-based products, updates are automatically applied during scheduled maintenance windows with advance notification.
• In-App Notifications: For desktop and self-hosted products, update notifications appear within the software interface. You can download and install updates directly from the application.
• Download Portal: All updates are available for download from your account portal at http://localhost/wms. Simply log in to your account and navigate to the Downloads section.
• Email Notifications: Update announcements are sent to the email address associated with your account. These emails include release notes, download links, and installation instructions.
• API Delivery: For products with API-based update mechanisms, updates are delivered through secure API endpoints.

Update availability and delivery methods may vary by product and license type. Please refer to your product documentation for specific update instructions.

3. Compatibility

We strive to ensure backward compatibility across minor updates within the same major version. However, please be aware of the following:

• Backward Compatibility: Minor updates (e.g., Version 2.1 to Version 2.2) are designed to be backward compatible. Existing configurations, customizations, and integrations should continue to work without modification.
• Breaking Changes: Major releases (e.g., Version 2.x to Version 3.x) may include breaking changes that require modifications to integrations, custom reports, or configurations. Detailed migration guides are provided with major releases.
• Third-Party Integrations: Updates to third-party integrations may be required to maintain compatibility with our software updates. We will notify you in advance if a third-party integration update is required.
• Database Compatibility: Database schema changes in major releases require migration. Automated migration scripts are provided for all supported database platforms.
• API Versioning: We maintain API versioning to ensure that existing integrations continue to work after updates. Deprecated APIs are supported for a minimum of 12 months after deprecation notice.

4. System Requirements

System requirements may change with major releases. We publish updated system requirements at least 60 days before the release of any major version. Current system requirements for each product are available on our website and in the product documentation.

• Minimum hardware specifications (CPU, RAM, storage)
• Supported operating systems and versions
• Database server requirements and supported versions
• Web server requirements and supported versions
• Browser requirements for web-based products
• Network requirements and port configurations
• Third-party software dependencies

It is your responsibility to ensure that your system meets the minimum requirements for the software version you are running or planning to upgrade to. We recommend performing a system requirements review before any major upgrade.

5. End Of Support

RPTech Software Marketplace follows a defined lifecycle for software version support:

• Current Version: Fully supported with all update categories (major releases, minor updates, security updates, and bug fixes).
• Previous Version: Supported with security updates and critical bug fixes for 12 months after the release of the current version.
• Legacy Versions: No active support. Security updates and critical bug fixes are not provided for versions older than the previous version.
• End-of-Life Notification: We provide at least 12 months' notice before ending support for any software version. Notifications are sent via email and posted on our website.
• Extended Support: Extended support for legacy versions may be available as a paid service. Contact our sales team for extended support options.

We recommend keeping your software up to date to ensure continued access to security updates, bug fixes, and new features.

6. Upgrade Policy

The following upgrade policies apply to our software products:

• Version Upgrades: Upgrading from one major version to the next is available for all license types. Perpetual license holders may need to purchase an upgrade license. Subscription and annual license holders receive upgrades as part of their subscription.
• Upgrade Cost: Upgrade pricing is determined at the time of the major release. We offer discounted upgrade pricing for existing customers compared to new license pricing.
• Upgrade Path: We support direct upgrades from the previous version to the current version. Upgrades from older versions may require incremental upgrades through intermediate versions.
• Upgrade Assistance: Professional upgrade assistance is available for customers who need help with the upgrade process. This includes pre-upgrade assessment, upgrade execution, post-upgrade verification, and data migration.
• Upgrade Window: There is no?????? deadline for upgrading to a new major version. However, we recommend upgrading within 12 months of a major release to remain within the supported version lifecycle.

7. Update Notifications

We notify customers about available updates through the following channels:

• In-Software Notifications: Non-intrusive notifications within the software interface alert you to available updates. These notifications include the update version, release date, and a brief summary of changes.
• Email Notifications: Update announcements are sent to the email address associated with your account. For security updates, notifications are sent immediately upon release.
• Release Notes: Detailed release notes are published for every update and are available on our website and in the download portal. Release notes include new features, improvements, bug fixes, known issues, and upgrade instructions.
• Dashboard Announcements: Important updates and security alerts are displayed on your account dashboard when you log in at http://localhost/wms.
• Changelog: A comprehensive changelog is maintained and accessible through our documentation portal for each product.

8. Rollback Policy

In the event that an update causes issues in your environment, the following rollback provisions apply:

• Pre-Update Backup: We recommend creating a full backup of your system before applying any update. For cloud-hosted products, automatic backups are created before each update.
• Rollback Window: For cloud-hosted products, automatic rollback is available within 72 hours of an update. For self-hosted products, you may manually restore from your pre-update backup.
• Emergency Rollback: If an update causes a critical issue, contact our support team immediately for assistance with emergency rollback procedures.
• Data Integrity: Rollback procedures are designed to preserve data integrity. However, any data entered or changes made after the update may be lost during the rollback process.
• Post-Rollback Support: After a rollback, our support team will work with you to identify the cause of the issue and develop a plan for safely reapplying the update.
• Cloud Products: For cloud-hosted products, our operations team manages the rollback process. Contact support for immediate rollback assistance.