Work History Entities
This topic describes the six different entity types in Work History and offers suggestions on how to select entities
An entity is a category in a form, an asset, site, project, customer, person, or product, that identifies who or what a form is about. for a given form.
Available on the Elite tier:
Contents
Work History features
| Feature | Historical content displayed |
|---|---|
| Record History |
Complete records from submissions that share matching mapped entity |
| Data History |
Data from submissions of the same form that share matching mapped entity values. |
Entity types
Work History is based on entities. An entity is a mapped category in a form and is represented by one of the following six entity types: Asset, Site, Project, Customer, Person, or Product—that identify who or what a form is about. The value entered for the mapped entity question specifies what Work History matches for that submission. For each form, you can map up to two entities. Record History Complete records from submissions across forms that share matching mapped entity values. includes all mapped entities, while Data History Data from submissions of the same form that share matching mapped entity values. requires selecting a single entity.
Entity type descriptions
- Asset: An object that receives recurring work or inspections.
- Common uses: Installation, Preventative or Corrective Maintenance, Vehicle Inspections, Compliance Inspections, Quality Inspections
- Site: A physical location where recurring work takes place.
- Common uses: Site Inspections, Site Assessments, Health and Safety checks, Permits, Toolbox talks
- Project: A temporary job with a defined start and end.
- Common uses: Work Orders, Invoices
- Customer: An account used for tracking submissions.
- Common uses: Proposals, Invoices, Work Orders
- Person: An individual who is the focus of recurring data collection.
- Common uses: Employee Evaluation, Disciplinary Management, Training, Patient Reports
- Product: An item or service that is ordered, tracked, or delivered.
- Common uses: Purchase Orders, Inventory Management, Sales Quotes
How to select entities
Select entities that match the form's primary focus and help users retrieve relevant historical data. Tailor your selection to the form's use case—this maximizes the value of Work History.
Examples:
- Preventative Maintenance forms:
- Use Asset as the main entity.
- Add Site as secondary if work involves multiple assets at one location.
- Use Project if the work is part of a larger project.
- Safety forms: Select the two most relevant entities: Site, Person, Asset, or Customer.
Note:Map questions to an entity only when that entity is the main focus of the form. For example, only map a Customer Contact Name question to the Customer entity type if the focus of the form is to evaluate that person.