Timer Settings

There are four possible timer settings: No Timer, Notification Timer, Three-Day-Doc Timer (paper out) and Flexible Timer (paper out). The last two (paper out) timers are mutually exclusive.

No Timer

The default setting for any QuickSkin client is to have no timers, which means that all packages are defined as stand-alone transactions. A package is created and the recipient receives the email notifications relating to the creation of that package. There are no reminders, and the package is not auto-forwarded at any time.

Email Notification Timer

This setting enables SDX to send email reminders to the sender and recipient for any enhanced package. The reminder text can be edited on the QuickSkin configuration screens.

Note: Holidays and weekends are not included, so email notifications are not sent at these times.

This timer enables reminders to be sent out for enhanced packages to both the sender and/or the recipient of a package.

Enable this option by selecting the Run Notification Timers checkbox in the Admin site on the Timer Configuration page. Reminders can be sent either once per day or hourly. The hours are configurable, and you can create as many reminder times as needed.

Paper Out Timers

Three-Day-Doc Paper Out Timer

This timer enables SDX to auto-forward enhanced packages to a specific alternate account. This timer is typically used to auto-forward to the paper out account for paper out processing, and this docment presumes this is the default configuration.

The time at which auto-forwarding occurs is calculated from the package's application date, although if no application date is set, SDX uses the time and date the package was received by SDX.

A package is always due to auto-forward 72 hours from the application date (if it has not been viewed during that time). Due to printing and mailing schedules for printed packages, an SDX package will get auto-forwarded early if the expected time to auto-forward is between 14:00 Eastern time and midnight of that day. Packages falling within this time range will auto-forward at 06:00 that morning. This time is referred to as the same day 'zero hour' time, and is configurable at the skin level.

This timer will not auto-forward packages on weekends or holidays. Additionally, SDX does not count weekends and holidays as business days, unless the application date is a weekend or holiday day.

Business Day Application Date Examples

Application Date/Time Business Day 72 Hour Mark Auto-Forward Time
Tuesday 15:00 Friday 15:00

(note this is after 14:00)

Friday 06:00

(same day zero hour)

Monday 01:00 Thursday 01:00

(note this is between 00:00 and same day zero hour)

Thursday 01:00

Formula to determine when a package will paper out:

If ((App DateTime + 72 business hours) > same day zero hour) & ((App DateTime + 72 business hours) > 14:00)
      then paper-out @ same day zero hour
else paper-out @ App DateTime + 72 business hours

Weekend/Holiday Application Date Examples

Application Date/Time Calendar Day 72 Hour Mark Package Paper Out Queue
Saturday 15:00 Tuesday 15:00

(note this is after 14:00)

Tuesday 06:00
Saturday 01:00 Tuesday 01:00

(note this is between 00:00 and same day zero hour)

Tuesday 01:00

Formula to determine when a package will paper out:

If ((App DateTime + 72 calendar hours) > same day zero hour) & ((App DateTime + 72 calendar hours) > 14:00)
     then paper-out @ same day zero hour
else paper-out @ App DateTime + 72 calendar hours

Flexible Timer

This timer enables SDX to auto-forward both enhanced and standard packages to an alternative account (typically for paper-out processing) using settings obtained from the package itself. Metadata is sent in the package’s subject line and controls whether or not the package will auto-forward. If the package will auto-forward, the metadata also defines the amount of time to elapse after the application date before the package auto-forwards.

Note: The application date is not retrieved from the package metadata. It is sent through the webservice call when submitting the package into SDX.
The metadata sent with a package that uses the flexible time is defined below:
  • PaperOut:
    • Y or True indicates the package is subject to paper-out processing.
    • N or False indicates paper-out processing is disabled for this package. (This setting is the default).
  • PaperOut Count: The number of days from the application date that need to elapse before the package is sent to paper. A value of 0 sends the package straight to paper. The default value is 3; therefore, a package with Paper Out = Y, but with no Paper Out Count in the metadata will be sent to paper after 3 days.
  • Weekends:
    • True indicates weekends are factored into the count.
    • False indicates weekends are not factored into the count. (This setting is the default).
  • Holidays:
    • True indicates holidays are factored into the count.
    • False indicates holidays are not factored into the count. (This setting is the default).

Examples

The following examples show some of the flexibility available with the use of metadata on flexible paper out timers. (Metadata is NOT case sensitive.)

  • PAPEROUT = Y:PAPEROUT COUNT=10:WEEKENDS=TRUE:HOLIDAYS=TRUE means send to Paper Out after 10 days from application date (creation date if application date is not set) including both weekends and holidays.
  • PAPEROUT = Y:PAPEROUT COUNT=0 means send to Paper Out when the Timer next triggers (runs hourly).
  • PAPEROUT = Y means send to Paper Out after 3 days (default) from application date, excluding weekends and holidays.
  • PAPEROUT = N means this document never gets sent to Paper Out. This is the default setting, so leaving this setting out is the same.

Examples of Weekends True/False

Table 1. Examples of Weekends True/False
Weekends Application Date/Time Paperout Count Paper Out Result
True Friday 16:00 Paperout count = 3 Monday 16:00
False Friday 16:00 Paperout count = 3 Wednesday 16:00

Formula for determining when a package will paper out:

If (weekends=true) 
     then expiration date/time = application date + paper out count
else If (weekends = false)
     then expiration date/time = application date + paper out count + number of non business days after application date.

Notes

Three Day Doc and Flexible Timers

Packages are sent to paper out on an hourly basis. For example, if a package's application date is Tuesday 1st June at 13:15 and the PAPEROUT COUNT is 3 days, then the paper out date is Friday 4th June at 13:15. When the Timer triggers during the hour of 13:00 on Friday 4th, then any packages (including this one) with a paper out time between 13:00 and 13:59 will get sent to the paper out account. If any packages are sent that have a paper out date set prior to the next trigger date and time, then these will paper out on the next run.

Three Day Doc

When a package is auto-forwarded, a submission email notification is sent to the original sender if the account is configured to receive package submission email notifications.

Flexible Timers

When a package expires to paper and the checkbox Send Expiry Email is checked in the Admin site on the Timer Configuration page, both the sender and recipient receive an email notification that the package has expired.

Configuration

The Run Timers at Weekends and Run Timers during Holidays configuration items in the Admin site do not control which days count as business days. They control whether auto-forwarding occurs if a package is due to auto-forward on one of those days (a weekend or holiday).