UKI CRM update for standalone, Sage 200 / Sage 300 / Sage ERP 1000 CRM connected customers
Notice 20-X | 30 April 2020
Technology is always changing, including how Sage software works alongside associated software including Operating Systems & Browsers. Sage CRM is impacted by changes to the TLS protocol being made to browsers and operating systems.
What are the upcoming changes?
The Internet Engineering Task Force (IETF) no longer recommends the use of older TLS versions. Apple, Google, Microsoft and Mozilla have announced a unified plan to deprecate the use of TLS 1.0 and 1.1 early in 2020. We've recently posted a blog to outline some of these changes.
Operating system changes to prevent the use of TLS 1.0 / 1.1 can also be expected but may impact businesses earlier, if the business IT policy removes the use of this protocol ahead of software vendors.
What does this mean for my business & customers?
Vendors of browser technology are actively working to deprecate TLS 1.0 / 1.1 technology and dates vary. Currently Sage CRM 2018 R2 is only partially supported for use with TLS 1.2.
Over the next few weeks, software patches will be released for all supported versions of Sage CRM from 2018 R1 onwards, to ensure TLS 1.2 compatibility.
Depending on what version is currently installed and how Sage CRM is currently used, steps, including upgrades, will need to be completed to ensure the software continues to work & services aren't disrupted.
What are the key dates?
TLS is not provided by Sage, the dates will vary dependant on the operating system, browser and business policy and as such is outside our control.
What is the product impact?
Please review the sections below to identify the steps by product:
Sage CRM Standalone
The following versions will have a patch released:
- 2020 R1 will become 2020 R1.1
- 2019 R2 will become 2019 R2.1
- 2019 R1 will become 2019 R1.2
- 2018 R3 will become 2018 R3.3
- 2018 R2 will become 2018 R2.3
- 2018 R1 will become 2018 R1.2
Please update to these patches as soon as possible to ensure no business disruption.
Sage 300 with CRM
We are finalising the approach for Sage 300 and the following knowledgebase articles will be updated with details shortly.
Sage 200 CRM
Sage 200 has several integrations. As the connector is no longer supported, the new Sage CRM patches will only be tested against the Sage 200 classic integration.
Consideration will also need to be made around the recent TLS communication we issued.
In all cases the CRM patches will be tested against the following recently released remastered versions.
- Sage 200 Summer 2017 RM with Sage CRM 2018 R3.3
- Sage 200 Summer 2018 RM with Sage CRM 2018 R3.3
- Sage 200 2020 R1 with Sage CRM 2020 R1.1
The support matrix will be updated as follows:
Sage 200 Version
|2020 R1||2020 R1.1|
|2019 Summer||2018 R3.3|
|2019 Spring||2018 R3.3|
|2018 Winter||2018 R3.3|
|2018 Summer RM (Remaster)||2018 R3.3|
|2018 Summer||2018 R3.3|
|2018 Spring||2018 R3.3|
|2017 Winter||2018 R3.3|
|2017 Summer RM (Remaster)||2018 R3.3|
|2017 Summer||2018 R3.3|
|2016 SP2 RM (Remaster)||7.3 is not TLS 1.2 compatible and customers using CRM should upgrade to a suitable combination as soon as possible|
|2016 SP2 RM||7.3 is not TLS 1.2 compatible and customers using CRM should upgrade to a suitable combination as soon as possible|
Sage ERP 1000 v4 & integrated Sage CRM
Sage CRM only integrates with Sage 1000 ERP v4 and is reliant on the Sage 1000 API.
For any systems where TLS 1.0 / 1.1 has been deactivated, either manually or via software vendors, new product installs and integrations to CRM will not work.
We will be providing the following:
- Updated APIs for Sage ERP 1000 v4 SP10 and SP11
- ERP 1000 v4 SP11 will be tested against CRM 2020 R1.1
- ERP 1000 v4 SP10 will be tested against CRM 2018 R3.3
We'll provide further communications when the API and CRM patches are ready.
When will the software be available?
We plan to make all updates available no later than end of May 2020.