Jobs and resources can both use tags (formerly known as attributes in Skedulo).
In a job context, tags can be used to define industry-specific requirements. For example, tags such as "Electrical" or "CAD Design" can be assigned directly to a job using job attributes.
In a resource context, a tag may represent a particular skill or competency that the resource has attained, such as "Occupational Therapy."
Tags help filter available resources when applied to jobs, i.e., In addition to other criteria (e.g., availability), only resources that have the required set of tags (or attributes) will be displayed in the initial job allocation list.
Tags on resources also have an expiry date; this means that those tags will only be active up until the date set.
Tags affect vehicle route planning (VRP) and optimization. The results that come from auto-scheduling take into account job tags.
Hard Versus Soft Tags
Job tags can be either hard (required) or soft. A hard tag indicates that a resource cannot be allocated unless they have the tag. Soft tagging enables a priority to be added to the tag (high to low). Skedulo resource allocation will then use the relevant score to determine which resource(s) are best suited for the job.
Resource Tag Expiry
Resource tags (which are added to resource records) can be set to expire. This is a useful feature when tracking resource licensing or registrations that may expire. If a tag has expired (e.g., the current date is past the expiry date), Skedulo will exclude the resource from the allocation list. This rule is applied regardless of whether the resource has other tags that meet the requirements of the job.
The weighting of job tags (attributes) is used to resolve which resource is best suited for a job. Typically we categorize tags into four priorities:
- 0 = Required (the highest priority).
- 1 = Low.
- 2 = Medium.
- 3 = High.
A "Required" flag set on a tag will make it the highest priority regardless of the weighting given to it. If a tag is set to "Required," then the resource availability list in job details view will only show resources that have that tag.
Note! In Salesforce, you never enter a value of zero, it is determined by selecting the checkbox named "Required."
The weighting of tags comes into play when there are multiple tags on the job.
Say we have a job and it has three attributes:
- Tag (A) weighted at 3.
- Tag (B) weighted at 1.
- Tag (C) weighted at 2.
Then we have two resources (X) and (Y):
- Resource (X) has tag (A) and (B) assigned to them.
- Resource (Y) has tag (B) and (C).
The priorities for each resource are calculated to present the most suitable candidate for the job.
When we view the job details view for that job, resource (X) will be first on the list, as he has a tag with a higher weighting than resource (Y).
If there is also a "Required" attribute set in the job tags, then before weightings are calculated, all resources will be checked to make sure they have that requisite tag. They will need to have that tag to be considered in the first place.
Creating a New Tag
- Open the data tables attribute list via "Manage" in the navigation menus.
- Click the "Create new" button (top right).
- Fill in the attribute details (name and type).
- Click "Create."
Also, see Data Tables: Tags.
- Log in to Salesforce.
- Click Tags > New.
- Enter the Tag name (required field).
- Select Type.
- Select Classification. Classification options include global, human, and asset.
- Click "Save."
The new tag is now ready to be associated with Jobs and Resources.
Figure 1. A new tag in Salesforce Classic.
- Log in to Salesforce.
- Click App Launcher > Tags > New.
- Continue as for Classic (in step 3 above).
Figure 2. An example of Salesforce Lightning showing the location of tags in the app launcher.
Figure 3. A new tag in Salesforce Lightning.