Field Service Developer Guide
jNote: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.
RecurringPattern Class
Namespace
Usage
Example
This example shows code for RecurringPattern and its properties.
1global class RecurringPattern {
2 global enum DaysOfWeek {Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday}
3 global enum FrequencyType {DAILY, WEEKLY, MONTHLY}
4 global Set<DaysOfWeek> DaysOfWeek { get; set; }
5 global FrequencyType FrequencyType { get; set; }
6 global Integer Frequency { get; set; }
7 global Integer NumberOfVisits { get; set; }
8}Recurring Pattern Properties
RecurringPattern contains the following properties.
DaysOfWeek
Signature
global Set<DaysOfWeek> DaysOfWeek { get; set; }
global enum<FSL.RecurringPattern> DaysOfWeek {Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday}
Property Value
Type: Set<enum>
Usage
You can set DaysofWeek manually. Alternately, you can derive the days the customer is available from the visiting hours record associated with the work order that is associated with the service appointment passed into the API.
Only one visit should be scheduled per day. For example, if you are scheduling a total of six visits and set DaysOfWeek to Monday and Wednesday, the API doesn’t provide a response with more than one visit scheduled for Monday and one visit scheduled for Wednesday.