Field Activities To Cut and Reconnect Service

A cut process that's created for a service agreement whose service can be severed will typically contain a cut event that creates field activity(s) to cut service. The base-package cut event activation algorithm will create field activities for the service points linked to the service agreement being cut. The type of activity is defined on the field activity type profile defined on each service point's SP type. Please see C1-CE-CR-FA for the exact details of the base-package algorithm.

If the cut process is canceled after field activity(s) are created and before the cut process completes, different activities can transpire. The specifics of what happens are controlled by a Cancel Logic algorithm plugged in on the cut process template. The following points summarize how a base-package algorithm (C1-CP-DWFA) works:

• It assembles all Pending, Held and Complete cut for nonpayment field activities (FA) created by the cut process (these are defined in the overdue process's log).
• Each FA is processed as follows:
  • If the FA is Pending or Held and it is not linked to a field order (i.e., it hasn't been dispatched):
    • The FA is cancelled
    • An entry is added to the overdue process log to indicate the cancellation
  • If the FA is Pending or Held and it is linked to a field order (i.e., it has been dispatched):
    • A To Do entry is created (the To Do Type is defined on the algorithm)
  • If the FA is Complete and the Cut Process's SA is pending start or active (i.e., it hasn't been expired yet):
    • Reconnect field activity(s) are created for every service point that had a cut for non-payment field activity. The type of activity is defined on the field activity type profile defined on each service point's SP type.