To my knowledge, the best way to do this would be to create another field that doesn't show up on the form called something like u_eta_timestamp, that's a calculated field based on u_eta. In the calculated value, set it to midnight either UTC or local time depending on your needs.
Alternatively, you could set up a u_eta_timestamp field and create a business rule to update it whenever the value of u_eta is changed.
Once you have that field defined, you can use the field comparison operators to create your queries. In this case, you'd use something like u_eta_timestamp "is more than" closed to form the comparison.
EDIT: I just worked this up in my personal instance.
I created a new ETA [u_eta] field on the incident table that is of type Date.
Your table might be different, but this should have me in a state that represents what you have now.
Next I created a Date/Time field on the Incident table called Committed SLA Timestamp [u_eta_ts]. On the Dictionary Entry page, I clicked the link to see the Advanced view of the form. After that, I clicked the Calculated Value tab and used the following script for the Calculation:
new GlideDateTime(gs.dateGenerate(current.u_eta, 'u_eta_ts'));
Here's a screenshot of the relevant part of the Dictionary Entry page:
I moved the field on the form so that it's just below the Committed SLA field so you can see its value in the screenshot below. Note that calculated value fields are read-only. In your case, you'll probably want to just remove the timestamp field from the form completely so that the user doesn't even know it's there.
Also note that the timestamp is the start of the Committed SLA [u_eta] date in local time, which in the screenshot above is PDT (UTC -7). If you want it to be UTC instead, just use the following calculation formula instead:
new GlideDateTime(current.u_eta);
In either case, you can now get the records you're looking for by querying for Committed SLA Timestamp is more than 0 Days after Closed, as shown in the following:
Hope this helps,
--Dennis R
To my knowledge, the best way to do this would be to create another field that doesn't show up on the form called something like u_eta_timestamp, that's a calculated field based on u_eta. In the calculated value, set it to midnight either UTC or local time depending on your needs.
Alternatively, you could set up a u_eta_timestamp field and create a business rule to update it whenever the value of u_eta is changed.
Once you have that field defined, you can use the field comparison operators to create your queries. In this case, you'd use something like u_eta_timestamp "is more than" closed to form the comparison.
EDIT: I just worked this up in my personal instance.
I created a new ETA [u_eta] field on the incident table that is of type Date.
Your table might be different, but this should have me in a state that represents what you have now.
Next I created a Date/Time field on the Incident table called Committed SLA Timestamp [u_eta_ts]. On the Dictionary Entry page, I clicked the link to see the Advanced view of the form. After that, I clicked the Calculated Value tab and used the following script for the Calculation:
new GlideDateTime(gs.dateGenerate(current.u_eta, 'u_eta_ts'));
Here's a screenshot of the relevant part of the Dictionary Entry page:
I moved the field on the form so that it's just below the Committed SLA field so you can see its value in the screenshot below. Note that calculated value fields are read-only. In your case, you'll probably want to just remove the timestamp field from the form completely so that the user doesn't even know it's there.
Also note that the timestamp is the start of the Committed SLA [u_eta] date in local time, which in the screenshot above is PDT (UTC -7). If you want it to be UTC instead, just use the following calculation formula instead:
new GlideDateTime(current.u_eta);
In either case, you can now get the records you're looking for by querying for Committed SLA Timestamp is more than 0 Days after Closed, as shown in the following:
Hope this helps,
--Dennis R
