UI Policy conditions allow you to specify conditions on date fields. They include an operator of 'is less than' that is designed to allow you to construct conditions comparing two date fields. You can apply offsets to the comparison field. In UI Policy conditions, they do not appear to work. If you turn on UI Policy debugging, the messages say the LESSTHAN operator is unsupported.

Steps to Reproduce

  1. Create a new UI Policy on change_request:
    • Set Short Description to test
    • Select the On load option
    • Select the Active option
    • Select the Reverse if false option
    • Select the Global option
    • Set Order to 100
    • Give it a condition of [Planned start date] [is] [less than 3 Days after Created]
  2. Click Save.
  3. For the UI Policy Actions.
  4. Click New and create one for the field change_plan to make it readonly. 
    This means that if you create a new change and the Planned start date is less than three days out, you are not allowing enough time for planning and you cannot input the change_plan.
  5. Save the UI Policy.
  6. Create a new change request.
  7. Set the Planned Start Date to tomorrow.
    Note that the change_plan field should be readonly, but nothing happens.
  8. If you enable UI Policy debugging, the following messages appear:

    11:41:01 (825)change_request.do GlideFieldPolicy: Running "Test" UI Policy on "change_request" table
    11:41:01 (825)change_request.do GlideFieldPolicy: >>> evaluating conditions:
    11:41:01 (825)change_request.do GlideFieldPolicy: evaluateTermDate - unsupported operator 'LESSTHAN'. Returning FALSE.
    11:41:01 (826)change_request.do GlideFieldPolicy: > start_date's value of "2014-01-16 11:40:11" with the condition( LESSTHAN sys_created_on@day@after@3) evaluates to FALSE
    11:41:01 (826)change_request.do GlideFieldPolicy: <<< condition exited with: FALSE

    11:41:01 (826)change_request.do GlideFieldPolicy: Setting "disabled" to "false" on "change_plan" field


There is no known workaround for this issue. If you are able to upgrade, review the Fixed In field below to determine the versions that have a permanent fix. You can also subscribe to this known error article (click Subscribe button at the top of the article) to receive notifications when more information is available about this issue.

Related Problem: PRB593878

Seen In

Calgary Patch 2 Hot Fix 5
Eureka Patch 8

Fixed In


Associated Community Threads

There is no data to report.

Article Information

Last Updated:2016-04-12 08:17:40