Filtering on dates within bulk tasks is useful as the population can change daily. For example, an object filter that searches for users whose expiration date has passed can change every day.
Important! If objects are in an LDAP user store, date searches may cause a significant performance reduction due to the dates being represented as regular strings.
The following fields make up the date filter:
Defines an attribute in the object that contains a date. All attributes for the object are available. If the filter uses an attribute, the system assumes the attribute contains a date.
Attribute values must match the date format set in the population tab. Objects that have an invalid date format will be ignored.
Refers to past or future dates compared to today.
Defines a lag time from today. For example, if you want to send an email to all users whose profile expires in the next week, the operator is 'Today or earlier' and the offset is 7, indicating 7 days from today. If you set the offset to -7, however, the email is sent to all users expired for more than a week. The following table outlines the behavior of the offset:
Today's Date |
Operator |
Day Offset |
Result |
1/10/2010 |
Today or Earlier |
7 |
Any date on or before 1/17/2010 |
1/10/2010 |
Today or Earlier |
-7 |
Any date on or before 1/3/2010 |
1/10/2010 |
Today or Later |
7 |
Any date on or after 1/17/2010 |
1/10/2010 |
Today or Later |
-7 |
Any date on or after 1/3/2010 |
Copyright © 2013 CA.
All rights reserved.
|
|