Defining Characteristic Types For FA Integration
The following characteristic types must be defined to facilitate FA integration.
External System Task Characteristic Type
If you have decided to map the tasks on your external system to the Oracle Utilities Customer Care and Billing field activity types, then you need to define the characteristic types based on your decisions. It is possible to map a combination of fields from the external system to a field activity type in Oracle Utilities Customer Care and Billing.
- Refer to the following topics in the documentation on integration
for more information about how you should define characteristics in
product integrations:
- Oracle Utilities Mobile Workforce Management Characteristic Types
- Oracle Utilities Work and Asset Management Characteristic Types
- Include Field Activity Type in the characteristic entity collection
Forced Appointments Characteristic Type
If your implementation supports forced appointments, the appointment booking logic attempts to store a characteristic on a field activity with a forced appointment.
- Create an ad hoc characteristic type.
- Include Field Activity in the characteristic entity collection
Reservation Characteristic Type
If your external system defines a separate reservation ID for appointments, the appointment booking logic attempts to store a characteristic on a field activity with the appointment reservation number.
- Create an ad hoc characteristic type.
- Include Field Activity in the characteristic entity collection
Override Phone Characteristic Type
Create a characteristic type for override phone if your implementation supports capturing a contact phone number on the field activity.
- Create an ad hoc characteristic type.
- Include Field Activity in the characteristic entity collection
Field Activity ID Characteristic Type
The sample FA integration algorithm may be configured to populate the field activity ID as a characteristic on any NDS records it creates. This facilitate in drilling down from the NDS record to the field activity. To support this logic,
- Create a foreign key characteristic type (if you don't already have one defined for Field Activity Id).
- Include Notification Download Staging in the characteristic entity collection