Toggling journal fields to show one field breaks UI policy.
Steps to Reproduce
Go to sys_user_preference_list.do and set the user preference glide.ui.activity_stream.multiple_inputs to true with the user set to System Administrator.
If this user preference does not exist:
- Click New.
- Set the following values:
Type: true | false
User: System Administrator
- Click Submit.
Navigate to Incident > Open and select an incident.
In the incident form, right-click in the header and choose Configure > UI Policies.
Click New to create a UI policy, complete the required information, set the filter [Assignment group] [is] [CAB Approval], right-click in the form header and choose Save.
In the same form, go to Related Links and in the UI Policy Actions tab, click New.
Create a new action with the following values and then click Submit.
Field name: Additional comments
In the incident form, click the filter icon next to the Activity section and uncheck Additional comments (Customer visible).
Impersonate the System Administrator.
Navigate to Incident > Open and select an incident using the filter [Assignment group] [is] [CAB Approval].
Note that the Additional comments field is hidden per the UI Policy you created.
Leave the incident open and select an incident using the filter [Assignment group] [is not] [CAB Approval].
Click the journal field toggle to display only one journal field.
Return to sys_user_preference_list.do and verify that the user preference glide.ui.activity_stream.multiple_inputs is false for System Administrator.
Go to the other incident and reload the form.
Note that Additional comments (Customer visible) field is showing and not hidden per the UI Policy, and that the Work Notes field is not showing at all.
This issue does not occur if the UI Policy is deactivated.
This issue is under review. To receive notifications when more information is available, subscribe to this Known Error article by clicking the Subscribe button at the top right of the article. If you are able to upgrade, review the Fixed In field to determine whether any versions have a permanent fix.
Related Problem: PRB917322