We recently have an issue raised from customer. The issue is: there're two dynamic policies applied to the same user:
"Policy 1" and "Policy 2 protector" associated with the desktop settings.
policy1's settings has no value set for the setting "Specify the URL that accesses the Protector server" and with "Don't set value" checked:
Policy2's settings has the value specified for this setting with "Don't set value" unchecked:
The setting "Specify the URL that accesses the Protector server" has the field name called: $Pref$PROTECTOR_LOCATION.
Scenario 1: When policy2 has higher precedence, $Pref$PROTECTOR_LOCATION is listed under “AlwaysSetItems” in the policy synopsis report:
Scenario 2: when policy1 has higher precedence, $Pref$PROTECTOR_LOCATION is NOT listed under “AlwaysSetItems”.
This does NOT mean the value of the setting is not applied to the user. Note here $Pref$PROTECTOR_LOCATION is only listed under “AlwaysSetItems” not outside of “AlwaysSetItems” in Scenario 1. So you don't depend only on this to decide if the setting with the value from policy2 is applied or not. Instead, PNAB >> $Policies needs to be checked and the value can be seen set well there in both scenarios.
This is working as designed that any setting with the field name starting with $Pref is not listed outside of “AlwaysSetItems”. Compare this with a different example, the field name starting with $DWA from mail settings >> Lotus iNotes is listed both under “AlwaysSetItems” and outside of it:
The inconsistency of the display of the two scenarios has been logged in SPR# DHUSAD7F5K. Development team has closed as no plan to fix as there is no function affected.