Create Tickler Event Rule Screen
Purpose: Use this screen to create an event rule for a specific tickler event.
This screen is divided into 2 areas:
• The top half of the screen displays the event rule settings, such as who to notify, the tickler category, resolution reason, and processing sequence number; see Event Rule Settings.
• The bottom half of the screen displays the event rule options, or criteria, that must be met by the system action in order for the system to create a tickler. The event rule options are different for each tickler event.
For each event rule you create, you must define at least one event rule option, or criterion, the system uses to determine if a tickler should be created. If you define more than one rule criterion, the system action must meet all of the options defined for the event rule to create a tickler.
Note: You cannot create a duplicate event rule, meaning, you cannot create 2 rules that have the same criteria or an error message indicates: Duplicate rule exists.
The Processing sequence number defined for each event rule determines the sequence in which the system validates each event rule to determine if a tickler should be created, 1 being the first priority. You should assign the most important event rules a lower sequence number.
Important: If you create or change an event rule, you must restart the async jobs in the Background Job Control menu option before your updates are applied to new ticklers.
How to display this screen: Select Create at the Work with Tickler Event Rule Screen.
Field |
Description |
Event |
The code and description for the tickler event associated with the event rule. Code: Alphanumeric, 2 positions; display-only. Description: Alphanumeric, 40 positions; display-only. |
Rule description |
A description of the event rule, usually indicating the criteria defined for the rule. Alphanumeric, 40 positions; required. |
Category |
A code for the tickler category assigned to the event rule. Tickler categories are used to group ticklers. The tickler category at the event level defaults, but you can override it. 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 rule is resolved. Tickler resolution reason codes are assigned to a tickler once the tickler has been resolved. The resolution reason at the event level defaults, but you can override it. 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. |
Active |
Indicates whether the event rule is active. selected = The event rule is currently active; the system creates a tickler for the event rule if its criteria are met by the system action. Remember, to create a tickler for the event rule, the Active flag at the event level must also be selected. unselected = The event rule is not currently active; the system does not create a tickler, regardless of whether the system action qualifies for the event rule. |
Processing seq |
The processing sequence number for the event rule. The processing sequence number defines the order in which the system evaluates the rules to determine if a tickler is created, from lowest sequence number to highest. Note: The first tickler event rule that meets the criteria creates a tickler. It is important that you assign the most important event rule the lowest processing sequence number. If you do not define a processing sequence number for an event rule, the system assigns the event rule a processing sequence number of 0. If all of the rules have the same processing sequence number, the system evaluates the rules in rule sequence number. See Event Rule Processing Sequence. Numeric, 3 positions; optional. |
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 event rule. 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 = 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). The notify user/group setting at the event level defaults, but you can override it. 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 orig user |
Indicates if ticklers created for this event rule are assigned to the user that entered the order associated with the tickler. selected = Assign ticklers created for this event rule 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 = Do not assign ticklers created for this event rule to the user that entered the associated order; instead, assign the tickler to the specified user or tickler user group. The assign to original user setting at the event level defaults, but you can override it. The tickler assignment defined at the event rule level overrides the tickler assignment defined at the event level. Note: See Tickler Assignment. |
Assign to user |
The user ID of the user the system assigns to ticklers for this event rule. The assign to user setting at the event level defaults, but you can override it. 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 the event rule, 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 user group |
The tickler user group the system assigns to ticklers for this event rule. The assign to user group setting at the event level defaults, but you can override it. 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 to ticklers for this event rule. The supervisor group setting at the event level defaults, but you can override it. 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 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. |
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 for this event rule; the supervisor can review ticklers using the Workflow Management (WWFM) menu option. The notify supervisor setting at the event level defaults, but you can override it. 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. |
Event rule options: For each event rule, you must define the options, or criteria, that must be met by the system action in order for the system to create a tickler. The event rule options are different for each tickler event. You must define at least one option, or criterion, for each tickler event rule. For more information on defining event rule options, see: • AR (Accounts Receivable) Event Processing • BO (Backorders) Event Processing • CO (Cancelled Orders) Event Processing • HO (Held Orders) Event Processing • MN (Manually Created) Event Processing • NO (New Orders) Event Processing • OO (Aged Open Orders) Event Processing • SD (SVC Activation Decline) Event Processing • SO (Soldout Orders) Event Processing • SV (SVC Number Assignment) Event Processing • UP (Unconfirmed Pick Tickets) Event Processing |
|
