Field Activity Type Profile - Template

Description of Page

The information in the Field Activity Profile Template collection defines the field activity request(s) created for each situation identified by the Customer Event. The possible customer events are Cut for Non-payment, Disconnect Warning, Reconnect for Payment, Reread, Stop Service, Start Service, and Start/Stop.

Note: Field activity requests do not need to be defined for Reread when Service Order Management is being used.

Other customer events can be defined on the Look Up page (search for the CUST_​EVT_​FLG field name). Refer to the following sections for more detail about customer events included with the base product.

The fields defined for each event are common. You define the field activity request(s) to be generated given the condition of the service point. The following fields display:

SP Field Condition Define the condition of the service point associated with the field activity. Define External Fieldwork Orchestration when Service Order Management is being used.

Sequence You will typically have a single field activity request for any specific combination of SP Field Condition and Disconnect Location. Therefore you'll just have a single sequence (say 10) for each combination. If you need to generate multiple field activities based on a given combination, use a unique sequence number for each activity.

No Activity Turn on this switch if no field activity should be generated for the condition.

Disconnect Location this is not applicable when Service Order Management is being used.

Activity Type Define the type of field activity request to be generated. You should take care to ensure that the activity type is defined as valid for the SP type (on the last page).

Where Used

Refer to the following sections for information about where each template is used.