Creating an HRD module

Simple CRM makes it very easy to create custom business modules.

Here we will create a small HRD module.

Each company having a different organization, we will imagine a simple organization that you will, of course, have to adapt and modify according to your real needs.

We will not cover all the needs of a human resources management, because it would be long and anyway, once the two examples are developed and assimilated, it will be very simple for you to implement all the HR processes you want.

For this case study we will work on two key examples :

Vacation management
Expense report management


Basic introduction: the general configuration

The first step is to enter your employees in Simple CRM.

To do this, first, create the company master record for your company.

Then enter your employees and link them to your company master record.

Finally, for each employee, create a PROJECT, whose name will be: HRD / NAME FIRST NAME / FUNCTION

In this project, of course, link your company and the employee.

In this project, you will store all documents related to this employee: CV, employment contract, pay slip, expense reports, etc.

Vacation management

The process

Vacation management in our example will follow the following process:

Request by employee
Study of the request by the HRD
Validation by the HRD or Refusal by the HRD
Vacation benefits


The configuration

To do this, we will create the type: " DRH - VAC ".

Whose steps will be:

HRD - CAV - 01 - Request
HRD - CAV - 02 - Study
HRD - CAV - 03 - Refusal
HRD - CAV - 04 - On Leave


(to do this, you must be Administrator, then go to Admin -> Types of interactions)

Once this is done, go to Admin -> Interaction Templates and we will create an Interaction:

Model Name: Vacation Leave Request
Subject: Vacation Leave
Interaction: Check the TACHE box
Related company: your company
From TYPE: HRD - CAV - 01 - Request
User: your HRD manager
Priority: 1
Media: Email
In the memo, the following explanation is added: "Please enter the start and end dates of your leave (= date of your absence and actual return from the office)".


Filing an application

When an employee wants to apply for leave, he will:

Go to his contact form (therefore his contact form linked to the company)
Launch the template: "Vacation Leave Request".
It completes and records

This interaction will then appear in the personnel manager's work item list.

The employee will study the possibility of this leave, then refuse or validate.

If it validates, it will change the owner of the Interaction by choosing the employee and it will place the right dates, as well as the right TYPE and will link to the employee's PROJECT :

Expense report management

The process

Expense claim management in our example will follow the following process:

Seizure by employee
Study of the request by the HRD
Validation by the HRD or Refusal by the HRD
Reimbursement of expenses.


The configuration

You will immediately see that the implementation follows exactly the same logic as for the first example.

To do this, we will create the type: "DRH - FRAIS".

Whose steps will be:

HRD - CHARGES - 01 - Introduction
HRD - EXPENSES - 02 - Study
HRD - EXPENSES - 03 - Refusal
HRD - EXPENSES - 04 - Refund

(to do this, you must be Administrator, then go to Admin -> Types of interactions)

Once this is done, go to Admin -> Interaction Templates and we will create an Interaction:

Model Name: Expense Claim Form
Subject: Expense report
Interaction: Check the TACHE box
Related company: your company
From TYPE: HRD - COST - 01 - Introduction
User: your HRD manager
Priority: 1
Media: Email
In the memo, we add the explanation: "Please enter the date of payment, the frame (for which assignment and which customer) and attach an image of the document proving the fee (either a scan or a photo taken with your mobile phone)".


Filing an application

When an employee wants to apply for leave, he will:

Go to his contact form (therefore his contact form linked to the company)
Launch template: "Expense claim".
It shall complete, link the supporting document(s) and record
This interaction will then appear in the personnel manager's work item list.
The latter will study the possibility of reimbursement, they will refuse or validate.
If valid, it will change the owner of the Interaction by selecting the employee, select the TYPE "HRD - COST - 04 - Refund" and link to the employee's PROJECT.
He can then duplicate this interaction in order to make it an interaction of TYPE "purchase".


The DUPLICATE button is located in Interaction, to the right of the table :

Conclusion

So you have understood the principle: Creation of a dedicated interaction TYPE, then a dedicated INTERACTION MODEL.

This logic can be applied to any need, so you are free to create your own custom modules.