This article summarizes the upgrade process for accounts moving from SFDC version 9.x or 10.x to version 11.0
This document goes through the process of customers who will be upgrading from a current managed package (version 10.9 or older) to the new Consensus version 11 plugin.
Configurations you can re-use with version 11:
- The API Keys
- The Connected App and Site
- The IDP Login URL
- Site URL
Please make sure that before you upgrade, you access the "cDemo" object in your current package, and make sure that the"Track Field History" option is enabled.
Here is a higher level outline of the steps required for completing additional config and Layout updates post-V11 upgrade.
- Confirm the Configuration page is still populated (or reconnected to existing or new API Keys). On our testing, this information remained populated.
- Confirm everything still looks good on the User Info table post-upgrade.
- You will need to kick off permission and data updates manually again to bring in data once more to the environment. Manually starting the Data Update again, will also start the new schedule job called “RecentDemoBoards” that we’ve introduced in this managed package, which is meant to be a more frequent, “lighter” request to Consensus for updated data from that day’s activity that needs to be synced to SFDC.
- It is recommended to update the standard object Page Layouts to make sure our DemoBoard and Invitation objects are added to each as a related list. This will most likely entail you remove the previous VisualForce Page leftover from V10 as well.
Here's an example from the Opportunity Object, along with the fields that would be good to add to the related list view as columns.
Recommended Columns/Fields for the DemoBoard related list:
- Creation Date (the date stamp Consensus recorded the demoboard being created in our system)
- Organization Name (Org/Account name recorded from Consensus)
- Total Invitations
- Total Views
- Total Shares
- Total DB Watch Time (total watch time of from all recorded activity on the DemoBoard)
- Details URL (The Consensus URL where you can see more details about all stakeholders and their respective analytics)
- Days Since Last Activity
Recommended Columns/Fields for the Invitation related list:
- Creation Date (the date stamp Consensus recorded the invitation being created in our system)
- Heatmap URL (link to view heatmap recorded for the stakeholder’s activity on the DemoBoard)
- Invite Opportunity Stage
- Total Watch Time
2. Update Layout Page (Pictured below is Lightning page builder):
- Create a new custom tab called “Consensus”
- Add our new customer managed component called “cCreateDemoBoard” as element within the tab
- Add 2 related lists elements (single) to the tab, for DemoBoards and Invitations.
In version 11.0, Instead of providing a Consensus User Profile, we are now including a 'Consensus User' Permission Set to assign proper access to our objects and fields
- Each user can only have one profile in Salesforce. Thus, system administrators previously needed to clone our profile and copy over all of our settings to whichever profiles they wanted to have access to the app.
- Permission sets, however, are special sets of permissions and one user can have as many permission sets added to them as necessary. So now, with the use of a permission set, the system administrator can simply assign that permission set on top of whatever user or profile they want, simplifying the setup process.
Please make sure your Consensus Users are assigned access to the correct objects by giving them our new permission set.
*Important Note if you're on 11.0 - DISREGARD FOR 11.1*
- As of 5/4/23 It is a known issue currently that we need to adjust the permissions shipped with the current 11.0 package in production. After installation, please "clone" the provided "Consensus Users" permission set, and then follow the steps below to add the correct access for Consensus users. If you want to avoid these manual steps below, please upgrade to version 11.1 where we improved the permission set to include the correct access and apex classes out of the box.
Step 1: Clone current “Consensus Users” permission set
Step 2: System permissions > Turn on “View all custom settings.”
Step 3: Add the following Apex Classes to the new cloned permission set:
Apex Class Name
Step 4: Consensus User Info object settings:
Give read access to the fields.
Step 5: Demo, DemoBoards, Invitations, Features and Views Object.
Give Read access to all fields
Step 6: Assign the permission set to the Connected App
Site Object Settings
If you haven’t checked on the Site object settings as well, we’d recommend reviewing the Site’s access to the Consensus User Info fields. Please got to Sites > Public Access Settings > Object Settings, and then edit the Consensus User Info object settings to ensure the site has read access for all fields in that custom object.
This is important for CRM Sync, and other features that rely on logically referencing this object and it’s fields for proper routing.
You may need to re-add the correct Apex Classes to the public site settings.
- Step 1: Go to “Setup” > search for “Sites” and select the Consensus site that you created for the previous version of our SFDC application.
- Step 2: Select “Public Access Settings” > The choose the option for “Apex Class Access”. Then “Edit” the selected apex classes.
- Step 3: Check that the correct Apex Classes are added or re-add them if necessary. Make sure to Save your changes
If you “Test” the CRM sync connection from Consensus and notice it’s not working, you may need to regenerate new keys to reset the CRM Sync bridge that allows Consensus to have access to a list of Accounts and Opportunities during (external) DemoBaord creation in our web app or other plugins.
- Generate new keys from Configuration page in Consensus SFDC app
- Add the new keys to the CRM Sync page in Consensus, and select the “Test” button to make sure you get a green “success” message.
You may need to re-download the metafile and reset SSO with Consensus. You can find more details on setting up the Connected app and SSO at this knowledgebase article: