Approaching Asset Date

The Approaching Asset Date series selects assets by comparing an asset date field with the time at which the task is executed. The selected jobs and actions then run once for every matching asset. Any asset field with a date or date-time type can be used.

Task execution means the moment the scheduled or manually started task runs. It is only the reference point for calculating the configured date boundary; it does not mean that the event represented by the asset date is executed at that time.

The following settings are available:

• Which field: the asset date field on which the series is based.
• Matching dates:
  • Latest matching date: the configured date is the last date that matches. All earlier dates also match. This is one upper boundary, not a closed interval.
  • Earliest matching date: the configured date is the first date that matches. All later dates also match. This is one lower boundary, not a closed interval.
  • Matching date range: dates from the first boundary through the second boundary match. Both boundary dates are included; only this choice creates a closed interval.
• Boundary / range start and Range end: choose a positive whole number of days, weeks, or calendar months before or after task execution. At task execution defines a zero-offset boundary without requiring a number.
• Asset Type: optionally restrict the series to one asset type.

Note: Each asset is only considered once in the series as long as its selected date and the task definition remain unchanged.

Create or select an asset field such as Contract end date. Use Matching date range, from At task execution through 3 months after task execution, and run the task regularly. This selects contracts whose end date lies within the next three calendar months without requiring an additional "latest cancellation date" field.

Use Earliest matching date, for example 2 weeks before task execution, when recent past dates and all later dates should match. The configuration summary reads: Earliest matching Warranty date: 2 weeks before task execution.

Use Latest matching date, for example 1 month before task execution, when that date and all earlier dates should match. The configuration summary reads: Latest matching Warranty date: 1 month before task execution.

As a job, for example, create a Quickticket for the responsible department and pass the asset name and selected date as parameters.