Work.com Developer Guide

Clouds with binary code floating aboveCloud with binary code floating above

No Results

Search Tips:

  • Please consider misspellings
  • Try different search keywords
Extend Work.com with Custom Solutions
Set Up Your Work.com Development Org
Develop a Workplace Command Center Solution
Package and License a Workplace Command Center Component
Understand the Work.com Data Model
Work with Employee Data
Link Employee with Other Objects
Synchronize Work.com Data Between Orgs
Authenticate Between Work.com and Other Orgs
Understand Location Data
Command Center Data Triggers
Understand Logging
Standard Objects Used by Work.com
Custom Objects and Fields Used by Work.com
Custom Metadata Types Used by Work.com
Model Workplace Reopening with Shift Management
Evaluate When to Open or Close Locations with Workplace Strategy Planner
Add a Support App to Employee Workspace with Employee Concierge
Implement a Queue Management Visitor Experience
PDF

Link Employee with Other Objects

Connect the Employee object to other objects.

Employee has an Employee.UserId lookup field to the User object. Also, the Employee object is linked to Individual. PersonAccount, for example, is sometimes used to represent employees. PersonAccount could be linked to an Employee via Individual.

Other examples for utilizing Individual’s connection to Work.com include:

  • Solutions leveraging Contact can tie back via Contact > Individual < Employee.
  • Solutions leveraging PersonAccount can tie back via PersonAccount > Individual < Employee.
  • Solutions leveraging custom Employee objects can tie back via Employee > Individual < Custom employee object.

Data synchronization is still required, depending on your own data model. The Command Center package ships with triggers that are designed to populate Individuals based on Employees, and associate Individuals to Users based on the Employee Number field.