UI policy using Created field

[Bhoj Sancheti]

Hi All,

I am trying to create a UI policy based on the condition that the field 'Created' (system created date field) is empty. The UI policy is not working for the new record form unless I bring the field on the form layout. Once on the form layout the policy is working as expected. But from the product documentation of UI policy we do not need the field to be present on the form for the UI policy to function. Any help on this would be appreciated!

[Dr Atul G- LNG]

NO mate, my knowledge say, for UI policy filed must be on form.

[Bhoj Sancheti]

Your knowledge on this must be really high, but the documentation (official) itself says its not mandatory for the field to be on the form. Incase this is failing for this field then need to escalate to ServiceNow regarding the same unless there is a proven solution.

[Dr Atul G- LNG]

HI @Bhoj Sancheti 

I think , log a case via NOW Support and let's wait SN inputs. Bcz my understanding is still same.

Some fields have to hidden based on the date created lets says records created before a certain date should show old fields and records created post this date should show new fields. Thus created UI policies accordingly. Now in case for new record creation the created date is empty thus triggering the old fields UI policy showing old fields and once record is saved the created date gets a value and thus triggers the new fields UI policy, but for new records the new fields policy should trigger, to solve this added a condition along with existing condition that if created is empty (or logic with other condition on created date) then also trigger this. But this fails to trigger the policy. Only when the created field is brought to the form layout the UI policy triggers. This is the whole scenario.

Atul: Or may be the use case as mentioned above need to understand from functional side, and then we can see. 

Thus created UI policies accordingly. Now in case for new record creation the created date is empty thus triggering the old fields UI policy showing old fields and once record is saved the created date gets a value and thus triggers the new fields UI policy, but for new records the new fields policy should trigger, to solve this added a condition along with existing condition that if created is empty (or logic with other condition on created date) then also trigger this.

Atul: Something , good is missing here, I try to put this with pen paper , but not abel to link the dots.

[Amit Pandey]

Hi @Bhoj Sancheti 

You rightly said that it is not mandatory for UI policy to have the field on the form to work.

Can you help me with the exact requirement? May be for that criteria, there's something conflicting on the UI policy level itself while it is working for others. 

Regards,

Amit

[Bhoj Sancheti]

Some fields have to hidden based on the date created lets says records created before a certain date should show old fields and records created post this date should show new fields. Thus created UI policies accordingly. Now in case for new record creation the created date is empty thus triggering the old fields UI policy showing old fields and once record is saved the created date gets a value and thus triggers the new fields UI policy, but for new records the new fields policy should trigger, to solve this added a condition along with existing condition that if created is empty (or logic with other condition on created date) then also trigger this. But this fails to trigger the policy. Only when the created field is brought to the form layout the UI policy triggers. This is the whole scenario.