Event

A code that determines the system action for which the system may create a tickler.

There are 11 system actions that can create ticklers. You cannot create other tickler events for the system to evaluate for tickler creation.

BO: backorders; see BO (Backorders) Event Processing

CO: cancelled orders; see CO (Cancelled Orders) Event Processing

HO: held orders; see HO (Held Orders) Event Processing

MN: manually created; see MN (Manually Created) Event Processing

NO: new orders; see NO (New Orders) Event Processing

OO: aged open orders; see OO (Aged Open Orders) Event Processing

SD: stored value card activation decline; see SD (SVC Activation Decline) Event Processing

SO: soldout orders; see SO (Soldout Orders) Event Processing

SV: stored value card number assignment; see SV (SVC Number Assignment) Event Processing

UP: unconfirmed pick tickets; see UP (Unconfirmed Pick Tickets) Event Processing

VP: voided pick tickets; see VP (Voided Pick Tickets) Event Processing

WF: remote workflow; see WF (Remote Workflow) Event Processing

Alphanumeric, 2 positions; display-only.

Description

A description of the tickler event.

Alphanumeric, 40 positions; required.

Category (Tickler category)

A code for the tickler category assigned to the tickler event. Tickler categories are used to group ticklers.

You can also define a tickler category for each event rule; the tickler category defined at the event rule level overrides the tickler category defined at the event level.

Tickler categories are defined in and validated against the Tickler Category table; see Working with Tickler Category (WTCT).

Alphanumeric, 3 positions; optional.

Resolution reason

A code for the reason why a tickler for this event is resolved. Tickler resolution reason codes are assigned to a tickler once the tickler has been resolved.

You can also define a resolution reason for each event rule; the resolution reason defined at the event rule level overrides the resolution reason defined at the event level.

You must define a tickler resolution reason for all tickler events except for the MN (manually created) tickler event.

Tickler resolution reasons are defined in and validated against the Tickler Resolution Reason table; see Working with Tickler Resolution Reasons (WTRR).

Alphanumeric, 3 positions; required except for MN tickler event.

Priority

The priority assigned to the tickler event, used to determine the importance of ticklers created for this event.

You can assign a tickler event priority between 1-9, where 1 is the lowest priority and 9 is the highest priority.

You can also define a tickler priority for each event rule; the tickler priority defined at the event rule level overrides the tickler priority defined at the event level.

Numeric, 1 position; required.

Active

Indicates whether the tickler event is active.

selected = The tickler event is currently active; the system creates a tickler if the system action qualifies for an event rule.

unselected = The tickler event and its event rules are not currently active; the system does not create a tickler, regardless of whether the system action qualifies for an event rule.

See Active Tickler Events and Rules.

Allow mult ticklers

Indicates if the system creates multiple ticklers for this tickler event if the system action qualifies for more than one event rule.

selected = The system creates a tickler for each event rule whose criteria are met by the system action.

unselected (default) = The system creates one tickler for the first event rule, in processing sequence order, whose criteria are met by the system action. The system does not create more than one tickler for the tickler event, regardless of whether the system action meets the criteria of more than one event rule.

Multiple ticklers are not allowed for tickler events OO (aged open orders) or UP (unconfirmed pick tickets).

See Allowing Multiple Ticklers.

Assign to orig user

Indicates if ticklers created for this tickler event are assigned to the user that entered the order associated with the tickler.

selected = Assign ticklers created for this tickler event to the user that entered the associated order. If this field is selected, you must also enter a user ID in the Assign to user field.

unselected (default) = Do not assign ticklers created for this tickler event to the user that entered the associated order; instead, assign the tickler to the specified user or tickler user group.

You must also define tickler assignment for each event rule; the tickler assignment defined at the event rule level overrides the tickler assignment defined at the event level.

Note: This field defaults to selected for MN (manually created) ticklers.

See Tickler Assignment.

Notify user/group

Indicates whether the system sends a Tickler Notification email to the assigned user or to all of the users in the assigned tickler user group when a tickler is created for this tickler event.

selected = Notify the assigned user/user group when a tickler is created; use the email address defined for the user in the User Extended table. If the tickler is assigned to a user group, send a notification to each user in the group, using the email address defined for each user in the User Extended table.

unselected (default) = Do not notify the assigned user/user group when a tickler is created; the user can review the ticklers in his queue at the Work with Tickler Screen (user/group view).

You must also define the Notify user/group setting for each event rule; the notify user/group setting at the event rule level overrides the notify user/group setting defined at the event level.

See Tickler Notification for a sample Tickler Notification email.

Assign to user

The user ID of the user the system assigns ticklers to for this tickler event.

You must also define the Assign to setting for each event rule; the assign to setting at the event rule level overrides the assign to setting defined at the event level.

You can define either an assign to user or assign to user group for each event, but not both.

Users are defined in and validated against the User table; see Working with User Records (WUSR).

See Tickler Assignment.

Alphanumeric, 10 positions; optional.

Assign to group

The tickler user group the system assigns ticklers to for this tickler event.

You must also define the Assign to setting for each event rule; the assign to setting at the event rule level overrides the assign to setting defined at the event level.

You can define either an assign to user or assign to user group for each event, but not both.

The tickler user group you enter must be defined as a user type and not a supervisor type.

Tickler user groups are defined in and validated against the Tickler User Group table; see Working with Tickler User Groups (WTUG).

See Tickler Assignment.

Alphanumeric, 10 positions; optional.

Supervisor group

The tickler supervisor group the system assigns ticklers to for this tickler event.

You can also define the Supervisor group for each event rule; the supervisor group at the event rule level overrides the supervisor group defined at the event level.

The tickler user group you enter must be defined as a supervisor type and not a user type.

Tickler groups are defined in and validated against the Tickler User Group table; see Working with Tickler User Groups (WTUG).

See Tickler Assignment.

Alphanumeric, 10 positions; optional.

Notify supervisor

Indicates when a Supervisor Notification Count email is sent to the supervisor based on the number of days since a tickler was created.

The system uses this calculation to determine the next notification date when a tickler is first created: tickler creation date + value in Number of days to notify supervisor field for the event/rule that created the tickler = next notification date. The system does not update the next notification date after a tickler is created.

The system sends the email to the email address defined for the supervisor user group in the Tickler User Group table.

The system continues sending an email to the supervisor group as long as a tickler assigned to the supervisor group is in an open or in process status and the Next notification date in the Tickler table is equal to or past the current date. If the next notification date is a future date, the system does not send an email until the next notification date is reached. If all ticklers assigned to the supervisor are resolved, the system no longer sends a Supervisor Notification Count email.

Leave this field blank if you do not want to notify the supervisor about aging ticklers; the supervisor can review ticklers using the Workflow Management (WWFM) menu option.

You can also define the Notify supervisor setting for each event rule; the notify supervisor setting at the event rule level overrides the notify supervisor setting defined at the event level.

If you define a number of days in this field, you must also define the supervisor group.

See Tickler Notification for a sample Supervisor Notification Count email.

Numeric, 3 positions; optional.

Note type

Indicates the type of notes you enter for ticklers created for this tickler event.

A = Action notes; you use the Edit Customer Actions Window to enter tickler notes.

B = Bill to notes; you use the Work with Bill To Notes Screen to enter tickler notes.

O = Order notes; you use the Work with Order Messages Screen to enter tickler notes.

S = Sold to notes; you use the Edit Customer Notes Screen to enter tickler notes.

T = Tickler notes; you use the Work with Tickler Notes Screen to enter tickler notes.

You can only define the tickler work notes setting at the event level.

If you change the note type for a tickler event, the system does not change the note type for previous ticklers.

Alphanumeric, 1 position; required.