Service templates describe elements that make up the services and their dependencies. They enable quick and repeatable creation of service elements in the following scenarios:
- Automatically: when a service is created as a result of order processing through the quote-to-cash process, and the price book entry for a line item has an associated service template
- Manually: via Create Elements From Template service action
Template elements are slightly different than service elements and come in two flavors:
- New — a brand-new element is created upon service creation from template
- Existing — an existing element is added to the service
Templates are stored in Service_Template__c object:
| Field | Meaning |
|---|---|
| Element Count | Auto-calculated, total number of elements in the template |
| MRC | An auto-calculated Monthly Recurring Cost (MRC) of a service built using this template, based on a sum of individual element MRCs. This value may be pushed as booked MRC to price book entries that reference this service template |
| Own MRC | Auto-calculated Monthly Recurring Cost (MRC) of own elements, i.e., ones that do not have a provider specified (MRC = Own MRC + Providers’ MRC) |
| Providers’ MRC | Auto-calculated Monthly Recurring Cost (MRC) of providers’ elements, i.e., ones that do not have a provider specified (MRC = Own MRC + Providers’ MRC) |
| Description | Optional, user-provided description of the template |
| Element Structure Definition | XML definition of service element structure |
| Is Valid | Auto-calculated flag checked if the template is valid: not empty and with valid XML. Attempts to create services from invalid templates (either from order line items or directly) always fail |
| Important | Element Count, MRC, Own MRC and Providers’ MRC are recalculated after template validation and after editing the template XML. |
