Expand my Community achievements bar.

Learn about Edge Delivery Services in upcoming GEM session

Asset expiry schedular AEM

Avatar

Employee

Hi Team,

 

I am using Asset Expire Scheduler to send out the notifications for the up loaders when any asset is set to expire.

I did try to debug the query is something like this 

03.04.2024 01:35:13.524 *DEBUG* [8.29.230.18 [1712079313521] GET /libs/cq/search/content/querydebug.html HTTP/1.1] com.day.cq.search.impl.builder.QueryImpl xpath query: /jcr:root/content/dam//element(*, dam:Asset)[((jcr:content/metadata/@prism:expirationDate >= xs:dateTime('2024-04-03T17:10:00.000.000Z') and jcr:content/metadata/@prism:expirationDate <= xs:dateTime('2024-04-03T17:20:00.000.000Z')))]

when I execute the same in the query builder it is not returning the results . and when I use the below, it works 

 

path =/content/dam
type = dam:Asset
daterange.property = jcr:content/metadata/@prism:expirationDate
daterange.lowerBound = 2024-04-03T17:10:00+5:30
daterange.upperBound = 2024-04-03T17:20:00+5:30
daterange.lowerOperation >=
daterange.upperOperation <=

 

Now, my question is what makes the difference in +5:30 and .000Z, How to overcome this ? 

2 Replies

Avatar

Community Advisor

@SateeshRe  Check in which date format these dates are getting saved as properties in JCR. is it UTC format or is it a timezone offset format.

+5:30 is a time zone offset that is added when someone updated these date properties from India (as India is 5 hours 30 minutes ahead of GMT ). 

Avatar

Community Advisor

Hi @SateeshRe 

Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.



Arun Patidar