What is the purpose of the pre-release? Pre-releases are early builds of Sage products made available to developers while the final production version is still in development. These builds may be subject to change, and we greatly appreciate your feedback and support during this phase. Participating in a pre-release gives you early visibility of upcoming changes and allows you to: - Familiarise yourself with new features
- Test and validate your product integrations
- Prepare for general availability
We always endeavour to release the final production build to our developer community ahead of general availability, but pre-releases offer an even earlier opportunity to engage with the product. How do I receive pre-release communications? You need to be on our Developer Programme distribution list to receive pre-release communications.
If you’re not currently receiving emails, contact us at [email protected] with: - Your active Sage Developer Programme account number
- Contact name
- Email address
Important: Being on the distribution list does not guarantee selection, as pre-release programs may be limited to selected participants. How do I participate in a pre-release? To be eligible for participation, you must be on our Developer Programme distribution list.
If you receive a pre-release email, you must: - Review the pre-release agreement included in the email.
- By downloading the software, you agree to the terms of that agreement.
Where can I access the pre-release software? A download link will be provided in the pre-release communication. Note that access is time-limited and will expire prior to general release. Will my existing serial numbers and activation keys work? Your existing Sage 50 and Sage 200 product licences will continue to work with this pre-release version. If there are any exceptions, these will be clearly communicated in the pre-release email. What are the installation guidelines? Unless otherwise stated in the pre-release email, standard installation guidelines should be followed. Additional guidance specific to pre-release builds includes: - Installing on a clean PC or image
- Fully removing the pre-release version after testing
- Not distributing the software to third parties
These steps help ensure a stable testing environment and prevent conflicts with production versions. How will I know what’s new in the pre-release? Feature updates and changes will be shared via email, but full documentation will be available at general release in the help files. Who should I contact for support or to report issues? Support for pre-release builds is limited because the product is not yet fully released. For assistance, you can contact the Developer Services team at: [email protected] To help us investigate your issue quickly, please include detailed replication steps and any supporting evidence when reporting a technical problem. |