Upgrading your ServiceNow + ScreenMeet application

Upgrading your ServiceNow application (2.5+ -> latest)

Upgrading your ServiceNow application is simple. Depending on the age of your package, you may be required to update some settings, as discussed below.

1. Pull the latest version of the ServiceNow ScreenMeet application from the ServiceNow store
   1. https://store.servicenow.com/sn_appstore_store.do#!/store/application/10bec847db946010d10fd1d3ca961916/2.7.4?referer=%2Fstore%2Fsearch%3Flistingtype%3Dallintegrations%25253Bancillary_app%25253Bcertified_apps%25253Bcontent%25253Bindustry_solution%25253Boem%25253Butility%25253Btemplate%25253Bgenerative_ai%25253Bsnow_solution%26q%3Dscreenmeet&sl=sh
2. Install it in either a lower environment or production based on your requirements.
3. Navigate to console.screenmeet.com as a ScreenMeet administrator.
4. Navigate to Organization -> Settings and Policies
5. Navigate to ServiceNow integration
6. Click on "Configure" at the bottom of the page.
7. If the configuration step above fails, see the resolution steps below.

Resolution for configuration/validation failing

1. Navigate to the ServiceNow instance as an administrator.
2. Search OAuth in the Filter Navigator at the top left of ServiceNow
3.  Inside of the System OAuth category of ServiceNow.
   1. select Application Registry
   2. Click on ScreenMeet Connect
   3. Click the lock icon next to the Client Secret field - 
      1. If this displays a long random string, the integration will not work successfully. 
   4. Replace the Secret with Gfjkhfs48fhs
   5. Click on "update"
   6. Refresh the ServiceNow incident/object that the widget is being used on
      1. If the ScreenMeet component still perpetually spins, log into the ScreenMeet console referenced in Resolution #1 and click on configure and validate instance again.
4. If this does not correct the issue, ensure the Service account username/password are valid/accurate.
   1. If further assistance is needed/the above does not resolve the issue, please open a support desk ticket below for further assistance.
   2. https://screenmeet.atlassian.net/servicedesk/customer/portal/2/group/2/create/9

Upgrading your ServiceNow application (legacy installations - 2.x -> 2.5+)

As of version 2.5, ScreenMeet requires a service account to be set up as part of your instance configuration. 

To reduce downtime during the upgrade process, please follow these steps in the sequence provided:

1. Set up your service account

• Create a new user named "ScreenMeet Service Account" or other desired name
• Choose the password (you will need to enter this later in the ScreenMeet console)
• Check off "Web service access only" to restrict regular logins as this user
• Add the following roles to the user:
  • x_prois_sm.remote_support
  • x_prois_sm.service_account
• Save the user
• Ensure that the user is configured such that their password never expires to avoid service interruption

2. Enter service account info into ScreenMeet console

Make sure you are signed in with an account which has either the admin or x_prois_sm.remote_support_admin roles.

1. Navigate to https://console.screenmeet.com/servicenow
2. Click on "Service-Now" as the login method
   
3. Enter your instance URL into the text box
4. Click on "Universal" as the instance type
5. Click on "Sign in to My Service-Now Instance"
6. Accept the ScreenMeet Connect permissions dialog
   
7. While logged in as an Administrator, navigate to the ScreenMeet Settings page (https://console.screenmeet.com/organization/config)
8. Click on Service-Now Integration
9. Leave the User Service Account toggle in the OFF state for now
10. Enter the Service Account Username
11. Enter the Password for Service Account
12. Click on Save Configuration

3. Install the new app (version 2.5 or later) in your instance

Install the ScreenMeet app via the standard app store process on your instance.

4. Toggle the "Use Service Account" in ScreenMeet Console

1. Return to the ScreenMeet console -> ServiceNow integration
2. Toggle the User Service Account toggle to the ON state
3. Click on Save Configuration
4. Click on Configure and Validate Service-Now Instance
5. Once you see a green checkbox, everything should be working normally