UI Policy conditions use sys_id in mobile instead of display value.

Steps to Reproduce

  1. Log in to the demo instance.
  2. Import the attached UI policy MobileSysidbug, or create a policy with the following information:
    • Filter Condition:  Caller starts with ACME
    • Execute if true:
      function onCondition() {
    • Execute if false:
      function onCondition() {
  3. Navigate to Incident and open any incident, remembering the incident number.
  4. Change the caller to any caller beginning with ACME and save the form.
  5. Note that the alert pops up true.
  6. Change the caller to any caller beginning with anything other than ACME.
  7. Note that the alert pops up false.
  8. Go to the mobile UI ($m.do).
  9. Navigate to Incident and open the same incident used in step 3.
  10. Make sure the caller starts with ACME.

Expected Behavior:  The popup should show as True since the caller does start with "ACME".

Actual Behavior:  The sys_id for the caller is returned rather than the display value, so there does not appear to be a match, and the popup shows as False.


If you are able to upgrade, review the Fixed In field to determine the versions that have a permanent fix to this issue.

Related Problem: PRB602990

Seen In

Dublin Patch 3

Fixed In

Eureka Patch 3

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2016-03-03 11:30:34