This article explains how to upgrade the ScreenMeet package for Salesforce managed package to the latest version. It is intended for Salesforce Administrators who manage the ScreenMeet integration in their Org.
The upgrade steps depend on the package version currently installed. Steps 1, 3, 5, and 6 apply to every upgrade. Steps 2 and 4 apply only to specific starting versions.
Prerequisites
Salesforce System Administrator permissions in the Org you are upgrading.
Administrator access to the ScreenMeet Console.
A Salesforce sandbox for testing the upgrade before you upgrade production.
Test the Upgrade in a Sandbox First
Perform and test the full upgrade process in a sandbox before you upgrade your production Org. This confirms that your page layouts, permission sets, and customizations work with the new package version.
Step 1: Check Your Current Package Version
Identify the ScreenMeet package version installed in your Org. The version number determines which upgrade actions you must complete in Step 2 and Step 4.
In Salesforce, go to Setup.
In the Quick Find box, search for and select Installed Packages.
Find ScreenMeet or Remote Support in the list.
Record the value in the Version Number column.
Keep this version number available for the remaining steps.
Step 2: Back Up ScreenMeet Session Data (Versions Older Than 1.9)
Complete this step only if your current version is older than 1.9. If you are on version 1.9 or newer, skip to Step 3.
Back Up Session Data Before Installing
The ScreenMeet custom objects changed in version 1.9. Export your existing ScreenMeet session data before you install the new package.
In Setup, use the Quick Find box to search for and select Data Export.
Export all records from the following objects:
screenmeet_ScreenMeet_Sesion__cscreenmeet_ScreenMeet_Session_Device_Info__cscreenmeet_ScreenMeet_Session_Log_Event__c
Save the exported files in a secure location before you continue.
Step 3: Install the Latest ScreenMeet Package
Install the latest ScreenMeet package from the Salesforce AppExchange. This step is required for all upgrades.
Click Get It Now to start the installation.
When prompted, select Install for Admins Only.
Complete the installation.
Step 4: Perform Version-Specific Upgrade Actions
After installation, complete the actions for the version you recorded in Step 1. Older versions require the actions for every newer version range as well.
Current Version | Required Actions |
|---|---|
1.15 or newer | None. Go to Step 5. |
1.12 to 1.14 | Replace the Lightning Component. |
1.9 to 1.11 | Replace the Lightning Component, migrate permission sets, and remove the old CSP Trusted Site. |
Older than 1.9 | All of the above, plus update customizations to the new data model. |
Version 1.15 or Newer
No further actions are required in Salesforce. Go to Step 5.
Versions 1.12 to 1.14: Replace the Lightning Component
Update your record page layouts to use the latest ScreenMeet Lightning Component.
Edit each record page that uses the ScreenMeet widget, such as Case or Lead.
Remove the old component:
ScreenMeetLiveWidgetorScreenMeetWidget.Add the
ScreenMeetSessionWidgetcomponent to the layout.Click Save, then activate your changes.
Versions 1.9 to 1.11: Migrate Permission Sets and Remove the Old CSP Trusted Site
Complete the Lightning Component actions for versions 1.12 to 1.14 first, then complete the permission set and CSP Trusted Site actions below.
Migrate to managed permission sets. Version 1.12 introduced managed permission sets. Move your users from the old custom permission sets to the new managed sets.
In Setup, go to Permission Sets. Duplicate ScreenMeet permission sets appear. The old custom sets show a Delete option. The new managed sets do not.
Rename each old set to avoid confusion, for example
Old ScreenMeet Agent.For each permission set, such as
ScreenMeet Agent, open the old and new sets side by side and click Manage Assignments in each.Add all users from the old set to the new managed set.
After you confirm that all users are migrated, remove the users from the old permission sets.
Optional: Delete the old permission sets.
Remove the old CSP Trusted Site. The Content Security Policy (CSP) entry is now included in the managed package. Remove the manually created entry.
In Setup, search for and select CSP Trusted Sites.
Find the trusted site with the URL
*.screenmeet.comthat does not have a package icon in the Action column.Click Delete next to this entry.
Versions Older Than 1.9: Update Customizations to the New Data Model
Complete all actions for versions 1.9 to 1.14 first. Then update any custom reports, triggers, flows, processes, or custom code that reference the old ScreenMeet objects so they use the new objects.
Old Object (Before 1.9) | New Object |
|---|---|
|
|
|
|
|
|
Customizations Break Without This Update
Any report, trigger, flow, process, or custom code that still references the old objects stops working after the upgrade. Update every reference before you upgrade production.
Step 5: Configure and Validate in the ScreenMeet Console
Connect the upgraded Salesforce package to your ScreenMeet service account. This step is required for all upgrades.
Ensure the Service Account Setup is complete.
Log in to the ScreenMeet Console as an administrator.
Go to the Salesforce Integration section.
Click Configure and Validate.
Wait for the process to complete successfully. The upgrade is then finished.
Verification
After you upgrade your production Org, test the ScreenMeet integration to confirm that the upgrade succeeded.
Confirm that agents can start ScreenMeet sessions from record pages.
Confirm that all ScreenMeet integrations work as expected.
Confirm that your reports populate with new session data.