Fonteva is a powerful AMS that is native to Salesforce and seems to operate as one system. As with any software, there are routine updates to fix bugs and provide valuable features. Both Fonteva and Salesforce have their own updates and patches for their respective software. What does that mean for your organization? In order to avoid issues, you will need to apply patches and updates for both Fonteva and Salesforce.
Fonteva changed the naming convention of its releases. Here’s what you need to know…
Fonteva’s changed its naming convention with the latest Fonteva release – “Fonteva 20 Spring.”
| Period | Salesforce Release Date | Salesforce Release Name | Fonteva Release Date | Fonteva Release Name |
| Winter of 2017 | December 27, 2017 | Spring ‘18 Release | ||
| Summer of 2018 | May 2, 2018 | Summer ‘18 Release | June 2018 | 2018-R1 |
| Winter of 2018 | August 29, 2018 | Winter ‘19 Release | ||
| Winter of 2018 | December 20, 2018 | Spring ‘19 Release | March 2019 | 2018-R2 |
| Summer of 2019 | April 24, 2019 | Summer ‘19 Release | July 2019 | 2019-R1 |
| Winter of 2019 | August 28, 2019 | Winter ‘20 Release | ||
| Spring of 2020 | January 1, 2020 | Spring ‘20 Release | ||
| Summer of 2020 | May 13, 2020 | Summer ‘20 Release | September 2020 | Fonteva 20 Spring |
| Winter of 2020 | September 9, 2020 | Winter ‘21 Release |
Here’s how they’ve structured their naming convention:
| Legacy Naming Convention | New Naming Convention |
| Release Name: 2018 – R1R1 = Release Number2018 = Year releasedExamples:2018 – R2 2019 – R1 | Release Name: Fonteva 20 SpringFonteva = Platform20 = Year ReleasedSpring = Version |
Keep in mind…
Salesforce has a similar naming convention for Releases – “Winter ‘21 Release.” Although the names are similar, the releases are completely separate from each other. It is important to review both Salesforce and Fonteva Releases and make updates accordingly.
