Working with Tickler Events (WTEV)
Purpose: Use this menu option to set up each system delivered tickler event, including:
• tickler event settings at the event level
• tickler event settings at the event rule level
• event rule criteria for each rule you create
• event rule procedures for each rule you create
In this chapter:
• Defining Tickler Events and Event Rules
- Active Tickler Events and Rules
- Event Rule Processing Sequence
• Work with Tickler Event Screen
• Work with Tickler Event Rule Screen
• Create Tickler Event Rule Screen
• 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
• VP (Voided Pick Tickets) Event Processing
• WF (Remote Workflow) Event Processing
- Generic Workflow XML Message (CWWorkflow)
- WF Event Example: Sample XML
• Work with Tickler Event Rule Procedure Screen
For more information: See Workflow Management Overview and Setup for an overview on workflow management.
Defining Tickler Events and Event Rules
To create a tickler, you must define:
• the tickler events that can create a tickler. There are system actions that can create ticklers. You cannot create other tickler events for the system to evaluate for tickler creation. Also, each tickler event is delivered as not active.
- BO: backorders
- CO: cancelled orders
- HO: held orders
- MN: manually created ticklers
- NO: new orders
- OO: aged open orders
- SD: stored value card activation decline
- SO: soldout orders
- SV: stored value card number assignment
- UP: unconfirmed pick tickets
- VP: voided pick tickets
- WF: ticklers received from a remote system
• tickler event settings that define how the system creates ticklers for each event; see Tickler Event Settings.
• event rule settings that override the settings defined at the event level and determine how the event rule is processed; see Event Rule Settings.
• event rule criteria that define the criteria the system action must meet to create a tickler; see Event Rule Criteria.
• event rule procedures that define the instructions a user should follow to work with and resolve a tickler created by the event rule; see Event Rule Procedures.
Tickler event hierarchy: For each tickler event, you can define multiple event rules. For each event rule, you can define procedures to resolve the tickler.
