The core of the Fonteva 20Spring.1 release is enabling Fonteva to utilize Salesforce Sharing Sets. Sharing Sets require time and patience to successfully configure in your org and subsequently enable the update to Spring.1. Please read this checklist in its entirety before beginning your update. This is designed to thoroughly inform you on how Sharing Sets affect your update and guide you step-by-step on how to update to 20Spring.1.
If ever you are uncertain, you always have the friendly ear of Fonteva Customer Support. Don't hesitate to call on them with any questions or to walk you through this update.
You will perform the following steps to completely and successfully update to Fonteva 20Spring.1:
Introduction to Sharing
Learn what Salesforce sharing sets are and how they impact you.
Deactivate customizations (Triggers, Workflows, Flows, Process Builders) associated with the Attendee object.
Perform Pre-Update Configuration
Verify you are on the right release to update to Fonteva 20Spring.1
Update to Fonteva 20Spring.1
Update from your current version to Fonteva 20Spring.1
Update Billing Address Metadata
Updating the Billing Address metadata will allow for the billing address to populate on Sales Orders and Receipts.
Configure Sharing Sets
Walk through the steps to set up Sharing Sets in your org.
Reactivate customizations (Triggers, Workflows, Flows, Process Builders) associated with the Attendee object.
Run Access Manager
Complete your update.
Fonteva recommends updating and testing first in a sandbox environment before updating your working environment. This will help you avoid any mishaps and ensure you prepare carefully without creating issues for your working environment.
Introduction to Sharing
What is Sharing?
Salesforce and Fonteva both feel strongly about ensuring the security of our customers and their data. To ensure security, Salesforce requires its partners to align with their security requirements. A key element of these requirements is called Sharing.
By enabling Sharing, Salesforce restricts the visibility of records to the individuals that own those records. Salesforce understands that this may be too restrictive in certain scenarios. Let's take the example of John, the administrator, creating a Sales Order for Jane:
John is creating the Sales Order for Jane, the contact on the Sales Order. Because John created the Sales Order and is the owner of that record, only he can see the Sales Order record. John wants Sharon to see this record in the Community Portal, but she can't due to this restriction.
To grant visibility to Contacts on records they do not own, Salesforce has created Sharing Sets.
What Are Sharing Sets?
Sharing Sets allow administrators to give access to records in the system to community users that are Contacts in the database. In the scenario above, the administrator would need to create a Sharing Set that allows Jane visibility of the Sales Order in the Community.
With 20Spring.1.0, Fonteva has enabled Sharing Sets within our Community. This enhances the security of Community Portals and makes sure that your data is safe.
Begin Your Update:
Start reading through the update here, beginning with Pre-Update Configuration.
These are other pages included in the Release Notes that contain more helpful, technical information about the release: