Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Enabling the Pega Field Service job schedulers

Updated on May 18, 2021

A job scheduler is an internal background process operating on a server that performs activities on a periodic basis. To use the Pega Field Service application, configure the LoadScheduleData, DeleteScheduleData, FSMPurgeHistoryRecords, and OptimizeTrip job schedulers.

The LoadScheduleData job scheduler maintains availability data for field workers for the configured number of days. Run this job scheduler daily so that the application always maintains field worker availability data for the configured number of days. This availability data is used for scheduling.

The DeleteScheduleData job scheduler removes the old availability data from the system and it deletes availability data for the field workers who were deleted from the system.

The FSMPurgeHistoryRecords job scheduler deletes the history data of the following table and logs data based on the configured number of days:

  • History-PegaFSM-Data-Calendar
  • History-PegaFSM-Data-AppointmentExt
  • History-PegaFSM-Data-Appointment
  • PegaFSM-Data-Log

The OptimizeTrip job scheduler runs every five minutes and route optimizes the undispatched trip schedules.

For more information on job schedulers, refer Managing agents.

To enable the Pega Field Service job schedulers, perform the following steps:

  1. In the navigation pane of Admin Studio, click Resources Jobs.

  2. Open the following job schedulers and turn on the Enable job scheduler switch.

    • LoadScheduleData
    • DeleteScheduleData
    • FSMPurgeHistoryRecords
    • OptimizeTrip
  3. Click Save as.

    Note: In a multi-node environment, by default these job schedulers run on one node at a time. Do not change this default setting.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us