Onboarding/Offboarding Elements
| Onboarding/Offboarding Elements | |
|---|---|
| Name: | Onboarding/Offboarding Elements |
| Tech Name: | OnboardingOffboardingElements |
| Class Name: | OnboardingOffboardingElements |
| Type: | Standard |
| Template: | Security_groups, Assignable, Basic |
| Custom Module: | No |
| Auditable: | Yes |
| Importable: | Yes |
| Reportable: | Yes |
| Hide module on Main Page: | No |
Contents
Short Description
Contains elements that can be used while creating Onboarding Templates or Offboarding Templates
Business Description
The Onboarding/Offboarding Elements module is accessible through subpanel in Onboarding Templates and Offboarding Templates modules. They are also available from the subpanel in the Organizational Units module.
Its records can be of three types: Task, Training, Exit Interview.
First two types can be used for Onboarding Templates. All three types can be used for Offboarding Templates.
You can also choose a user who has to perform a specific Task, Training or Exit interview. It can be: the onboarding/offboarding employee (Self), Specific User, Employee Manager or Organizational Unit Manager. However, the Self value applies only to Task, in the case of Training and Exit interview it is not possible to select this option.
All onboarding/offboarding element records related to an onboarding/offboarding template are affected by Generate Offboarding or Generate Onboarding actions. By invoking them all elements will be converted to records in Tasks, Trainings, Exit Interviews modules and related to generated Onboarding/Offboarding.
Custom Actions
Processes
Related Processes
| Process | Short Description |
|---|---|
| Offboarding | How to start and conduct an offboarding process |
| Onboarding | How to start and conduct an onboarding process |
Related Process Steps
Related Features
Affected by
Initiating
| Name | Type | Short Description | Initiating Fields | Affected Fields | Affected Modules |
|---|---|---|---|---|---|
| Feature:Days From Start | Automation | When Days From Start is filled, its value affects Start Date of Onboarding/Offboarding Elements | Days From Start | Start Date, Start Date, Start Date |
Related Integrations
Structure
Fields
| Name | Type | Required | Validations | Visible | Editable |
|---|---|---|---|---|---|
| Assigned to | relate | No | Yes | Yes | |
| Created by | relate | No | Yes | No | |
| Date Created | datetime | No | Yes | No | |
| Date Modified | datetime | No | Yes | No | |
| Days From Start | int | Yes | Yes | Yes | |
| Description | text | No | Yes | Yes | |
| Element Type | enum | Yes | Yes | Yes | |
| Modified by Name | relate | No | Yes | No | |
| Name | name | Yes | Yes | Yes | |
| Organizational Unit | relate | Yes | Depends | Yes | |
| Own Task | bool | No | Yes | Yes | |
| Related User | username | Yes | Yes | Yes | |
| Task Duration (h) | float | Yes | Yes | Yes | |
| Type | enum | Yes | Yes | Yes |
Relationships
| Laft | Type | Right | Short Description | Relationship |
|---|---|---|---|---|
| Users | one-to-many | Onboarding/Offboarding Elements | Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user. | Relationship: Users - OnboardingOffboardingElements |
| Users | one-to-many | Onboarding/Offboarding Elements | Specific Sugar user can create many account records, but specific account record can be created by only one user. | Relationship: Users - OnboardingOffboardingElements |
| Users | one-to-many | Onboarding/Offboarding Elements | Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned. | Relationship: Users - OnboardingOffboardingElements |
| Users | one-to-many | Onboarding/Offboarding Elements | One User record can have many related Onboarding/Offboarding Elements records, but a specific Onboarding/Offboarding Elements record can be related to only one User record. | Relationship: Users - OnboardingOffboardingElements |