Saving Catalogue UI Policy for date/time
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2024 01:36 AM
Hi everyone.
I'm quite fresh to ServiceNow, still in training.
I want to create the Catalog UI Policy for a date/time field, but I'm having an issue saving it.
I create the condition:
Save the form, and this happens:
Am I doing something wrong here?
I've searched around and one solution would be an extra space at the end of the field. However it is a drop-down menu and I can't exactly edit it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2024 01:40 AM - edited 07-12-2024 01:42 AM
This looks quite weird
If you create condition as below and save, it should stick to that,
Also, the condition should be movie_date is not empty & movie date is before today.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2024 03:14 AM
Yeah, that was just me going panic trying everything. I just need the movie_date | before | today.
The is, or is not, even after conditions work.
The before and at_or_before don't save.
I'm using the following build:
Build tag: glide-washingtondc-12-20-2023__patch4-hotfix1-06-10-2024
It's the instance that I have available on the https://developer.servicenow.com/

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2024 03:52 AM
What are you trying to achieve ?
Regards,
Musab
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-13-2024 01:28 AM
Hi Musab, it is very simple.
A no code solution to do an action if the date/time field is before tomorrow. Just that.
As you can see I create the variable date/time field on the desired catalogue item. I create a catalogue UI policy, save it, and every time I try to create a condition for an action if the date/time field if before today (or even at and before yesterday, in fact any before operator), when I save the condition simply... well... doesn't save.
The pictures on the first post is literally what happens. I create a catalogue UI policy condition on a date/time variable with the operator before, save the UI Policy, and after the screen is refreshed due to the save the condition is not as I set it.
Might it be a bug? Does this happens to anyone else with an instance with the Build tag I referenced before?