Use case: During the initiation of a new change request (Change > Create), the user experience has to automatically redirect users to the "ALL" tab by default.
Solution Proposed:
User preferences primarily track the way individual users interact with various features so that new sessions activate the user's last settings.
These user customizations are stored as records in the User Preference [sys_user_preference] table and are updated each time the user changes the setting. The UI displays according to each user's preferences.
Navigate to User Administration > User Preferences for a list of user preference records.
Records for the system-wide value, which applies to users who have not customized the feature, have these values: System=True and User=blank. For each user who customizes the features, a separate record is created with these values: System=False and User=<username>. As a result, the same customizable UI feature may have multiple user preference records. The system-wide preference is active during the user's next session. If the user customizes the behaviour, a new user preference record is created and used for subsequent sessions.
Name: sn_chg_model_ui.landing_page.chg_model_filter (The name of the feature or functionality)
To find the UI pages, navigate to System UI > UI Pages.
Each UI page has a URL computed from the application scope, page name, and the .do file extension.
For example, to display the page called glidewindow_example on the demo system, you would navigate to https://<instance name>.service-now.com/glidewindow_example.do. If the page was part of a custom application called example_app, you would instead navigate to https://<instance name>.service-now.com/x_example_app_glidewindow_example.do.
On line 4, the redirection of the change model landing page is designed to align with the user's last preference. However, it's noteworthy that in line 5, a specific value ("all") has been hardcoded, leading to the landing page being redirected to the "all" tab regardless of the user's previous preferences. This effectively overrides any user-specific settings, potentially impacting the intended customization of the landing page based on individual choices.
