A service-interval definition for an item, optionally per SKU: when the service falls due (in days, usage hours or a usage reading), the from/to duration and usage window it covers, its position in the sequence of services, and up to five reminder day-offsets. Service campaigns pick an active campaign's schedule and stamp it onto the records they generate, and leads carry the schedule that prompted them. Once any transaction exists against the schedule's item, the handler locks dueInDays against edits and blocks deletion of the schedule.
Fields
| Field | Label | Type | Required | What it does |
|---|
CreatedById | Created By | Lookup → UserAccount | Yes | |
CreatedDateTime | Created Date | DateAndTime | Yes | |
DueInDays | Due In Days | Number | | How many days after the reference point the service falls due. Once any transaction exists for the schedule's item this field is locked against edits, so change it only on unused schedules. |
DueInUsageHours | Due In Usage (Hours) | Number | | Usage-hours alternative to the days-based due point, for equipment metered in running hours. |
DueOnUsage | DueOnUsage | Number | | Usage-reading alternative to the days-based due point, for equipment metered by an odometer or counter rather than by hours. |
ExternalId | External | Text | | |
FifthReminderDayOffset | 5th Reminder Day Offset | Number | | |
FirstReminderDayOffset | 1st Reminder Day Offset | Number | | |
FourthReminderDayOffset | 4th Reminder Day Offset | Number | | |
FromDurationDays | From Duration (Days) | Number | | Start of the age window in days this schedule covers; together with the to-duration value it bounds which units the schedule applies to, so a service programme can be split into successive intervals. |
FromUsageHours | From Usage Hours | Number | | |
FromUsageReading | From Usage Reading | Number | | |
Id | Id | Guid | Yes | |
ItemId | Item | Lookup → Item | | |
ItemSKUId | Item SKU | Lookup → SKU | | |
ModifiedById | Modified By | Lookup → UserAccount | Yes | |
Name | Name | Text | Yes | |
NumberOfReminder | Number Of Reminder | Number | | How many of the five reminder day-offsets on this schedule are in use; each offset is expressed relative to the due point. |
OwnerId | Owner | Lookup → UserAccount | Yes | |
RecordTypeId | Record Type | Guid, hidden | | |
SecondReminderDayOffset | 2nd Reminder Day Offset | Number | | |
Sequence | Sequence | Number | | Position of this service in the item's ordered programme of services, so successive intervals can be told apart. |
ThirdReminderDayOffset | 3rd Reminder Day Offset | Number | | |
ToDurationDays | To Duration (Days) | Number | | |
ToUsageHours | To Usage Hours | Number | | |
ToUsageReading | To Usage Reading | Number | | |
UIProps | UI Props | Text | | |
UpdatedDateTime | Modified Date | DateAndTime | Yes | |
Actions
| Action | Label | Type | What it does |
|---|
Clone | Clone | ServerAction (Clone) | Create a copy of this record |
Delete | Delete | Delete | Delete |
DeleteListHeader | Delete | Delete | Delete |
DeleteListRow | Delete | Delete | Delete |
Edit | Edit | Edit | Edit |
EditInLine | Edit | EditInline | EditInLine |
EditListHeader | Edit | Edit | EditListHeader |
EditListRow | Edit | Edit | EditListRow |
New | New | New | New |
Validations
| Validation | Applies to | Error message | Notes |
|---|
| To Usage Reading Validation | ToUsageReading, Error | To Usage reading cannot be less than zero. | Ensures To Usage Reading is greater than From Usage Reading. |
- UserAccount — looks up via
OwnerId - SKU — looks up via
ItemSKUId - UserAccount — looks up via
CreatedById - UserAccount — looks up via
ModifiedById - Item — looks up via
ItemId - ServiceCampaign — referenced by via
ItemMaintenanceScheduleId - Item — referenced by via
ItemMaintenanceScheduleId - Lead — referenced by via
ItemMaintenanceScheduleId
