Difference between revisions of "Module:Applications"
From MintHCM Wiki
Line 29: | Line 29: | ||
* '''Accepted''' : this is the status that the decision-maker sets after positively verifying the application | * '''Accepted''' : this is the status that the decision-maker sets after positively verifying the application | ||
* '''Rejected''' : this is the status that the decision-maker sets after negative verification of the application | * '''Rejected''' : this is the status that the decision-maker sets after negative verification of the application | ||
+ | |||
+ | When user creating the application, has several types to choose from: | ||
+ | *'''Leave''' : creating this type of application, the user can inform the supervisor about the planned vacation. The decision-maker may grant or refuse such leave | ||
+ | *'''Event''': this type informs interested persons about the possibility of organizing or going to an employee event | ||
+ | *'''Training''' | ||
{{Module-links}} | {{Module-links}} | ||
{{technical-description}} | {{technical-description}} | ||
{{DevNotes}} | {{DevNotes}} |
Revision as of 12:24, 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
- Status : this field is a drop-down list in which you can see the current statuses of the Application, such as : New, In progress, Accepted, Rejected. In particular, the last two statuses are important because they indicate whether the decision-making person has accepted or rejected the application
- Decision Maker : it is a field related to the users module in which a decision-making person regarding a specific application is selected
- Description : a field where the authoring user can enter a more detailed description of a given application
- Applicant : it is the same relational field as the "Decision Maker" field, so to the users module in which the person who submitted the application is selected
In the status field, the following values are possible which indicate the current status of the Application:
- New : this status tells the user that a new application has been created and has not yet been processed, accepted or rejected
- In progress : this status tells the user that his application is being processed by a decision-maker
- Accepted : this is the status that the decision-maker sets after positively verifying the application
- Rejected : this is the status that the decision-maker sets after negative verification of the application
When user creating the application, has several types to choose from:
- Leave : creating this type of application, the user can inform the supervisor about the planned vacation. The decision-maker may grant or refuse such leave
- Event: this type informs interested persons about the possibility of organizing or going to an employee event
- Training
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 |