Field Activity - Characteristics/Remarks

Use this page to link additional information to the field activity. Open this page using Menu > Field Order > Activity > Search and navigate to the Characteristics/Remarks page.

Description of Page

Summary information about the Service Point at which the activity will occur is displayed, as well as the service point's system-generated Service Point ID.

The Characteristics collection contains information that describes miscellaneous information about the field activity.

To modify a characteristic, simply move to a field and change its value. To add a new characteristic, click the + button to insert a row, then fill in the information for each field. The following fields display:

Characteristic Type Indicate the type of characteristic.

Characteristic Value Indicate the value of the characteristic.

Note:

Default Note. A field activity's characteristics default from the field activity type.

The Remarks grid is used to define anomalies associated with the field activity. For example, you can indicate performing the required task wasn't possible because there was a dangerous situation at the premise.

The Field Activity Remark Status is only relevant if a Field Activity Remark code has algorithms associated with it. The execution of the algorithm is performed by the field activity remark activation a background process (FACT).
  • When you add a remark that has an algorithm, the status is Pending . It remains in this state until the FACT process next runs.
  • When the FACT process next runs, if the system is successful in executing the algorithm, the status of the field activity remark may become Complete. If the system is not successful in executing the algorithm, the status becomes Error.
Note:

Algorithm may control status. By default, the field activity remark activation process assumes that if the algorithm does not detect an error, the status of the FA remark should be complete. However, in some cases, the algorithm may not find an error but may also want the status of the FA remark to remain pending. Refer to FACT-CMPOTG for an example of such an algorithm.

Remarks that are in error. Field activity remarks whose algorithms could not be successfully executed by the FACT background process result in the creation of a Field Activity Remark Exception record. To correct errors, you may have to delete and re-add the field activity's remark code if the error is impossible to fix (e.g., if the remark causes a customer contact to be generated and there is no customer at the field activity's premise).

Fastpath:

Refer to Setting Up Field Activity Remarks for more information.