An easyemployer user is only created as a Skedulo resource when a group they are a member of (within easyemployer) is identified as a "field resource operations" group—and needs to be synced and cached within Skedulo. At the point of group record syncing, all related users will be queried, and a resource record will be created for each.
The following records are to be created within easyemployer to enable resource syncing:
Abilities.
User.
User Abilities.
Group.
User Group.
When a group is created in easyemployer, system administrators (within the Salesforce environment) are sent an email notification, alerting them that a new record requires approval (for syncing), or rejection.
If approved, the following data is queried from easyemployer:
The user group records related to the group.
The user record related to user groups.
The user-ability records related to the user.
The user group records related to the user.
The leave records related to the user.
Note
Skedulo resource records are created using information from easyemployer. However, the resource records require manual data input to finalize their setup.
The following table shows the data mapping between easyemployer users and Skedulo resources.
Table 10. User mappings and translations.
Skedulo Field |
easyemployer Field |
Mappings/Translations |
|---|---|---|
Name |
given_names + surname |
--- |
Employee ID |
user_id |
--- |
Country Code |
--- |
The default value of "AU" will be populated. |
--- |
||
Home_Address |
address + suburb + city + state + post_code + country |
--- |
Is Active |
active |
EE translation:
|
Mobile Phone |
mobile |
--- |
Notes |
comments |
--- |
Notification Type |
communication_sms |
EE translation:
|
Resource Type |
--- |
The default value of "Person" will be populated. |
Once created, the resource record can then be accessed within the Skedulo web app. The following information needs to be entered manually:
The "Primary Region" (related to resource record).
The resource "Category."
The "Employment Type."
Refer to
Accessing and updating the Skedulo resource record (within the Skedulo web app) will also trigger the geolocation to be populated against their record.
For resources who will be operating outside of a regular roster of shifts, their availability will need to be defined using either availability templates or individual availability records.
Refer to
To finalize the resource setup, their Salesforce user needs to be related to the resource record. If the Salesforce user has not been created, the normal business process for setting up a user is to be followed.
Refer to
The point of entry for a resource's leave is within easyemployer, where all leave balances are managed. On creation of a leave record, the data is passed from easyemployer to Skedulo, where the "Sked easyemployer integration settings" custom setting field "EE Leave Sync" is checked:
If the value is "All," a corresponding availability record is created to show the resource's unavailability for that period.
If the value is "Approved," a record is not created and the leave is not reflected within the resource's schedule until it is approved within easyemployer.
Note
Updates to the leave record are to be performed within easyemployer. The amendments will be synced to Skedulo.
The point of entry for tags is within easyemployer, as an "Ability." On the creation of an ability record (in easyemployer), it is passed to Skedulo and cached as a tag. Skedulo then queries if there are any user ability records for existing resources related to the ability in easyemployer, if so they are created as resource tags.
Note
Updates to the ability record are to be performed within easyemployer. The amendments will be synced to the tag record in Skedulo.
The point of entry for resource tags is within easyemployer, as a "User Ability." On creation of a user ability record (in easyemployer) it is passed to Skedulo and if there is an existing resource for the related user record, a resource tag is created. If the ability related to the user ability does not have a corresponding tag record, this information is queried and the tag is created.
Warning
Updates to the user ability record are to be performed within easyemployer. The amendments will be synced to the resource tag record, in Skedulo.
Comments
0 comments
Article is closed for comments.