Default filters on related lists are not getting applied in Service Operations Workspace - Support and Troubleshooting

Default filters on related lists are not getting applied in Service Operations Workspace .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Description :

Default filters on related lists are not getting applied in Service Operations Workspace

Steps to Reproduce : 1. HOP onto a Y P11 OOB instance (empayp7) 2. Navigate to the incident table and open any incident in native UI.

3. Configure the related lists on the "Service Operations Workspace" form view and add the "Incidents by Same Caller" relationship. 4. Within the newly added relationship, add a default filter with the condition as "State is New" and "Created before today". 5. Notice on refresh of the incident form, this filter is persisted in UI16/Polaris. 6. Now navigate to SOW and open the same incident that was opened in Step 2.

7. Click on the "Incidents by Same Caller" related list tab. 8. Notice that the default filter is not applied.

Solution: When a user simply *modifies* the filter, *without* clicking "Set as Default Filter" afterward, then the modified filter doesn't reflect in Workspace for the related list. This is the expected behavior.

If the form is simply refreshed in Core UI, you'll continue to see the modified filter. However if you start fresh from the Incident list and open a record, you will see the default filter that was saved - you will no longer see your personally-modified filter. Same, if you click "next" to navigate to the next record from the original list, the filter you modified (but did not set as default) is no longer there in Core UI.

When a user modifies the filter on a related list *without* then clicking Set as Default Filter, the modified filter is not intended to be saved as a User Preference for the next time they open the same form.

If an admin clicks Set as Default Filter after modifying a related list's filter, that change is reflected in Workspace as expected.

If an end user modifies the filter on a Core UI related list *without* then clicking "Set as Default Filter", the modified filter is not intended to be saved as a User Preference for the next time they open the same form. Simply refreshing the current form may still show the modified related list filter, but navigating to the next record (or navigating to a record from the list) uses the default filter that was saved by an admin.

If an admin clicks "Set as Default Filter" after modifying a related list's filter in Core UI, that change is will be reflected in Workspace as expected.