Enabling Toggle button to switch Next experience UI

 

Enabling Toggle button to switch Next experience UI


The San Diego new release comes with a new UI and we called it as “Next Experience UI” or 

To enable it we have a system property glide.ui.polaris.on_off_user_pref_enabled that we need to set to true in our ServiceNow Instances. If a single user wants to switch back to UI16, it is not possible. As there are no options or toggle buttons available by default similar to Switch to UI 15.



Switch UI 15:



For that, we have to enable another system property glide.ui.polaris.on_off_user_pref_enabled that should be enabled or set as true.


Note: There is a dependency to work that toggle button.The Next experience (glide.ui.polaris.experience) property should be set to true, to visible that toggle button.


Enable Unified Navigation:





Additional Information

Enabling the system property "glide.ui.polaris.on_off_user_pref_enabled" is not showing option to switch the UIs in the user preferences settings for the user.

https://community.servicenow.com/community?id=community_article&sys_id=7d41b6f61bb6c15098a1ece6b04bcb70

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1113554


Community questions - Force "current" user logout from UI Action 

Similar article written by Maik -  Allow users to switch between Next Experience UI and UI16

Similar article written by Mark  - Enable/Disable Next Experience UI on user level (San Diego)


Thanks,

Sagar Pagar






Comments

Post a Comment

Popular posts from this blog

Script Action and Example

Script Actions The Script actions feature allows to create server side scripts that can run on server side and perform multiple tasks asynchronously. It will run or execute after the event has triggered in the system scheduler. For example: modifying records,    A script action can only be triggered by an event using gs.eventQueue() method.  Script actions are maintained in the System Policy —> Script Actions [sysevent_script_action] table in ServiceNow.   Available Fields For Script actions we have these fields. Name: Add a unique name for a script action. Generally to maintain script actions we should maintain the naming conventions.  Example: Let's take example, we have to create a script action for Close incidents/Problems when Change request gets closed, so name will be Incident-Probelm Closure Application: The application that contains this script. Example: Global or scoped applica...
Read more

#BuildWithCreatorStudio Challenge

Image
  🚀 Excited to share that I've completed the #BuildWithCreatorStudio challenge! 🚀 Using ServiceNow Creator Studio, I built a streamlined Employee Relocation process for India. Here’s a quick look at the automated steps I created: Request Submission: Employees can easily submit their relocation requests, listing the details needed. Manager Approval: The request goes to the employee’s manager for review. They can approve or reject based on the information provided. TCBP Team Validation: Once approved by the manager, the TCBP team reviews and validates the request details. Notification: After final validation, the TCBP team approves the request and notifies the employee of next steps. This simple workflow ensures all requests are reviewed thoroughly by both the manager and TCBP team. Thanks to Creator Studio’s easy, no-code interface, I built this application in under an hour—way faster than I expected! Want to create something yourself? Check out the #BuildWithCreatorStudio chall...
Read more

System Properties & it's Usage in ServiceNow

Image
  System Properties System properties used to store configuration information that rarely or never changes. We can add or update to control the system behavior. It is best practice to use a system property instead of hard cladding the fixed values.System properties store configuration information that rarely or never changes. System properties are maintained in the System properties [sys_properties] table in ServiceNow.   Available Fields For System property we have these fields. Name: Add a unique name for a system property. Generally to add or maintain system property we should maintain the naming conventions. Example: Let's take example, we have to create a property for Team Development Code Reviewers assignment group, so name will be team.development.code.reviewers   Description: Type a brief description for the property. What is the purpose/function and where will it be used? Type: We have multiple data types for a property. For example- Integer, String, Choic...
Read more