Newer Version Available
SkillRequirement
Supported Calls
create(), delete(), describeLayout(), getDeleted(), getUpdated(), query(), retrieve(), search(), update(), upsert()
Special Access Rules
If you want to use SkillRequirement for Field Service use cases, then Field Service Lightning must be enabled.
If you want to use SkillRequirement only for Omni-Channel skills-based routing use cases, then you don't need Field Service Lightning to be enabled.
Fields
| Field Name | Details |
|---|---|
| LastReferencedDate |
|
| LastViewedDate |
|
| RelatedRecordId |
|
| SkillId |
|
| SkillLevel |
|
| SkillNumber |
|
Usage
Skill requirements help dispatchers assign work orders to service resources with the proper expertise. You can still assign a work order, work order line item, or related service appointment to a service resource that does not possess the specified skills, so skill requirements serve more as a suggestion than a rule.
If many of your work orders require the same skills, add skill requirements to work types to save time and keep your processes consistent. When you add a skill requirement to a work type, work orders and work order line items that use that type automatically inherit the skill requirement. For example, if all annual maintenance visits for your Classic Refrigerator product require a Refrigerator Maintenance skill level of at least 50, add that skill requirement to the Annual Maintenance Visit work type. When you create a work order for a customer’s annual fridge maintenance, applying that work type adds the skill requirement as well.