Module:ExitInterviews

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

Short Description

Exit Interviews are conducted during an offboarding process

Business Description

In the system Exit Interviews are available as records in Exit Interviews module. The records contains information about date, who is interviewed and an offboarding related. A course of a interview can be included in Description field.

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.

Collapse

Custom Actions

Collapse

Processes

Related Processes

Process	Short Description
Offboarding	How to start and conduct an offboarding process

Collapse

Related Process Steps

Related Features

Collapse

Affected by

Name	Type	Short Description	Affected Fields	Initiating Fields	Initiating Modules
Feature:ExitInterviews - date start - Validation IsBefore	Validation		Start Date	End Date	Exit Interviews

Collapse

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

Collapse

Related Integrations

Structure

Collapse

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	ExitInterviews - date_start - Validation IsBefore	Yes	Yes
Status	enum	No		Yes	Yes

Collapse

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