Severance Event Dependencies and Trigger Date

When a severance event is created by the system, its trigger date cannot be set. This is because, unlike collection events, the trigger date on severance events can only be set when ALL of the preceding severance events on which it depends are complete. An example will help explain why this design is necessary. Consider the following example that shows a standard severance process and its events:

This severance process is meant to execute as follows:

• On the first day, generate a 48-hour warning of impending disconnection. This is a field event as most organizations deliver this warning in person.
• After 2 days (i.e., 48 hours) have passed, create a field activity to disconnect for non-payment.
• When this is completed, generate a To Do entry to let a CSR know about the cutoff. Also, send a letter to the customer.
• If after 10 days from the cutoff, we still don't have payment, expire the service agreement.

As can be seen from the above example, the later events are dependent on the completion of the field activities in the earlier events. This means that when you set up a severance event, you must indicate the events on which it depends (and the number of days after their completion that the event should be triggered).