Disabling Next Experience to use Connect in Classic UI16Connect Chat is not supported with Next Experience. However, system administrators can allow specific users that use Connect Chat to turn off Next Experience and use the Classic UI16. This enables your instance to use Next Experience, while still enabling system users to disable the Next Experience UI to use Connect Chat in Classic UI16. Roles required: system admin There are two options to allow system users to turn off Next Experience UI, even when the system properties are enabled on an instance. Option 1: Allow users to turn Next Experience on and off themselves as needed using a user preference toggle.Option 2: Forcibly turn off Next Experience for a system user. You can optionally set a system property to allow users to opt back into Next Experience if desired. These options are explained below. Option 1: Allow users to turn Next Experience off and on Create the following system property: Navigate to the system properties table by entering sys_properties.list into the application navigator.Create a new system property with the name glide.ui.polaris.on_off_user_pref_enabled and set the value to true.Manually refresh the web browser so that the newly created system property updates are made and system users can access the Next Experience toggle. Result: All users can navigate to user display preferences and enable or disable Next Experience so that they can use Connect. Known Issue: The Polaris user preference setting does not support dynamic display of Connect Chat modules nor user notifications settings at this time. Option 2: Turn off Next Experience for a user by default System administrators can set a system user preference to disable Next Experience UI for users by default. You can set a system property to enable specific users to turn Next Experience on if desired. Navigate to the system user preference table by entering sys_user_preference.list into the application navigator.Create a new record and set the following values. System administrators are required to create a new record for each user. FieldDescriptionUserSelect the user that you would like to default to Classic UI16. NameEnter Glide.ui.polaris.use.ValueSet to false to default the user to Classic UI16. To allow specific users to optionally enable Next Experience UI, follow the steps in Option 1: Allow users to turn Next Experience on and off above. Result: When the user logs in, their instance defaults to Classic UI16 and Next Experience is disabled. When Next Experience is disabled, users can use Connect Chat. Users can optionally enable Next Experience when the glide.ui.polaris.on_off_user_pref_enabled system property is set. Considerations and Behavior with Next Experience Disabled Available Functionality and Administrator Access In the San Diego release, the following Connect Chat functionality will remain available only when the Next Experience system property glide.ui.polaris.experience is set to false. Group messagesPeer-to-peer messagesRecord conversationsVTB conversationsLive feed Connect Chat administrator setup pages are not available from menu items, however they can still be accessed and edited using the following navigation methods: Group messages: Enter live_message.list into the application navigator. Once the table is loaded in the list view, apply a new filter. Dot-walk by selecting Show Related Fields, Conversation > Live Group Profile fields, and type equal to Connect.Peer-to-peer messages: Enter live_message.list into the application navigator. Once the table is loaded in the list view, apply a new filter. Dot-walk by selecting Show Related Fields, Conversation > Live Group Profile fields, and type equal to Peer.Actions: Enter connect_action.list into the application navigator.Action icons: Append the browser URL with connect_action_icon_classes.do.Properties: Append the browser URL with system_properties_ui.do?sysparm_category=Connect&sysparm_title=Connect%20Properties. User Preference Setting and Notification Limitations for Connect Chat When a user has Next Experience UI turned on, they cannot send or receive Connect Chat messages. For Connect Chat to function, both the sender and receiver must be using Classic UI16 with the Next Experience disabled. This unique scenario should be noted: User 1 sets their display preference to disable Next Experience UI then sends a Connect Chat message to User 2 .User 2 keeps Next Experience UI on and does not receive a notification of the new Connect Chat message. Considerations and Behavior with Next Experience Enabled The following Connect Chat menu items, including administrator setup pages will be hidden from the UI when the Next Experience system property glide.ui.polaris.experience is set to true. This property is set to true upon upgrade to the San Diego release. Connect > Connect Chat > Administration: Group messagesPeer-to-peer messagesActionsAction iconsProperties Before Upgrade Connect Chat administrator setup pages are available as menu items in the application navigator. After Upgrade Connect Chat administrator setup pages are not available as menu items in the application navigator. Theming Instances with Next Experience UI enabled use style records within the Polaris theme to display company logos rather than configuring company logos via UI16 configuration preferences. Users who are using UI16 may notice the company logo no longer displays when Next Experience UI has been turned on for an instance. This is expected behavior.