Difference between revisions of "Module:ExitInterviews"
From MintHCM Wiki
(Created page with "{{Module-infobox |Module-name=Exit Interviews |Module-tech-name=ExitInterviews |Module-class=ExitInterviews |Module-type=Standard |Module-template=security_groups,employee_rel...") |
Kurkiewiczk (talk | contribs) |
||
| Line 10: | Line 10: | ||
|Module-reportable=Yes | |Module-reportable=Yes | ||
|Module-hidden=No | |Module-hidden=No | ||
| − | |Short Description= | + | |Short Description=Exit Interviews are conducted during an offboarding process. In the system they are available as records in Exit Interviews module. |
}} | }} | ||
| − | |||
=={{int:ev-business_description}}== | =={{int:ev-business_description}}== | ||
| − | + | Exit Interview records can be created form two places: in Exit Interviews module or as a result of [[Action:OffboardingTemplates - Generate new Offboarding|Generate new Offboarding]] | |
| − | + | action invoked in [[Module:OffboardingTemplates|Offboarding Templates module]], as long as, there is an [[Module:OnboardingOffboardingElements|onboarding/offboarding element]] of this type related to given template. | |
| − | [[ | + | While in first case, Exit Interview does not have to be related to any employee or offboarding, in second case this relations are created automatically. |
| − | |||
{{Module-links}} | {{Module-links}} | ||
| − | + | {{technical-description}} | |
{{DevNotes}} | {{DevNotes}} | ||
Revision as of 16:23, 22 January 2020
| Exit Interviews | |
|---|---|
| Name: | Exit Interviews |
| Tech Name: | ExitInterviews |
| Class Name: | ExitInterviews |
| Type: | Standard |
| Template: | Security_groups, Employee_related, Assignable, Basic |
| Custom Module: | No |
| Auditable: | Yes |
| Importable: | No |
| Reportable: | Yes |
| Hide module on Main Page: | No |
Contents
Short Description
Exit Interviews are conducted during an offboarding process. In the system they are available as records in Exit Interviews module.
Business Description
Exit Interview records can be created form two places: in Exit Interviews module or as a result of Generate new Offboarding action invoked in Offboarding Templates module, as long as, there is an onboarding/offboarding element of this type related to given template. While in first case, Exit Interview does not have to be related to any employee or offboarding, in second case this relations are created automatically.
Custom Actions
Processes
Related Processes
| Process | Short Description |
|---|---|
| Offboarding | How to start and conduct an offboarding process |
Related Process Steps
Related Features
Affected by
Initiating
| Name | Type | Short Description | Initiating Fields | Affected Fields | Affected Modules |
|---|---|---|---|---|---|
| Feature:Close Onboarding/Offboarding if all other elements are closed | Automation | On save, if status of Exit Interview/Task/Training is equal to 'Held' or 'Completed' and record is an element of Onboarding or Offboarding, system checks if all other elements related to Onboarding/Offboarding are closed (Held or Completed). If so, status of Onboarding/Offboarding also changes to 'Held'. | Status, Status, Status | Status, Status | Offboardings, Onboardings |
| Feature:ExitInterviews - date start - Validation IsBefore | Validation | End Date | Start Date | Exit Interviews |
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 | |
| Description | text | No | Yes | Yes | |
| Employee | relate | No | Yes | Yes | |
| Employee ID | relate | No | Yes | Yes | |
| End Date | datetimecombo | No | Yes | Yes | |
| Modified by Name | relate | No | Yes | No | |
| Name | name | Yes | Yes | Yes | |
| Start Date | datetimecombo | No | Yes | Yes | |
| Status | enum | No | Yes | Yes |
Relationships
| Laft | Type | Right | Short Description | Relationship |
|---|---|---|---|---|
| Employees | one-to-many | Exit Interviews | One Employees record can have many related Exit Interviews records, but a specific Exit Interviews record can be related to only one Employees record. | Relationship: Employees - ExitInterviews |
| Users | one-to-many | Exit Interviews | Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user. | Relationship: Users - ExitInterviews |
| Users | one-to-many | Exit Interviews | Specific Sugar user can create many account records, but specific account record can be created by only one user. | Relationship: Users - ExitInterviews |
| Users | one-to-many | Exit Interviews | Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned. | Relationship: Users - ExitInterviews |