Difference between revisions of "Module:Applications"
From MintHCM Wiki
| Line 16: | Line 16: | ||
It is a module in which employees can submit applications to their superiors for vacation, event, training, purchase, benefits or other. when creating the Application, there are three required and non-required fields, such as: | It is a module in which employees can submit applications to their superiors for vacation, event, training, purchase, benefits or other. when creating the Application, there are three required and non-required fields, such as: | ||
| − | * '''Name''' | + | * '''Name''' : this field provides the general name of the application to which it relates |
| + | * '''Type''' : it is a field with a drop-down list in which we choose the type of application, whether it is a leave, event, training, purchase, benefits or other | ||
{{Module-links}} | {{Module-links}} | ||
{{technical-description}} | {{technical-description}} | ||
{{DevNotes}} | {{DevNotes}} | ||
Revision as of 10:12, 14 September 2021
| Applications | |
|---|---|
| Name: | Applications |
| Tech Name: | Applications |
| Class Name: | Applications |
| Type: | Standard |
| Template: | Employee_related, Security_groups, Assignable, Basic |
| Custom Module: | No |
| Auditable: | Yes |
| Importable: | No |
| Reportable: | Yes |
| Hide module on Main Page: | No |
Contents
Short Description
The Applications module is used to transfer various requests, eg leave requests and many others, to the superiors.
Business Description
It is a module in which employees can submit applications to their superiors for vacation, event, training, purchase, benefits or other. when creating the Application, there are three required and non-required fields, such as:
- Name : this field provides the general name of the application to which it relates
- Type : it is a field with a drop-down list in which we choose the type of application, whether it is a leave, event, training, purchase, benefits or other
Custom Actions
Processes
Related Processes
Related Process Steps
Related Features
Affected by
Initiating
Related Integrations
Structure
Fields
| Name | Type | Required | Validations | Visible | Editable |
|---|---|---|---|---|---|
| Created By | relate | No | Yes | No | |
| Date Created | datetime | No | Yes | No | |
| Date Modified | datetime | No | Yes | No | |
| Decision Maker | relate | No | Yes | Yes | |
| Description | text | No | Yes | Yes | |
| Employee | relate | No | Yes | Yes | |
| Employee ID | relate | No | Yes | Yes | |
| Modified By Name | relate | No | Yes | No | |
| Name | name | Yes | Yes | Yes | |
| Status | enum | Yes | Yes | Yes | |
| Type | enum | Yes | Yes | Yes |
Relationships
| Laft | Type | Right | Short Description | Relationship |
|---|---|---|---|---|
| Employees | one-to-many | Applications | One Employees record can have many related Applications records, but a specific Applications record can be related to only one Employees record. | Relationship: Employees - Applications |
| Users | one-to-many | Applications | Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user. | Relationship: Users - Applications |
| Users | one-to-many | Applications | Specific Sugar user can create many account records, but specific account record can be created by only one user. | Relationship: Users - Applications |
| Users | one-to-many | Applications | Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned. | Relationship: Users - Applications |