Automate vacation
When the company’s staff grows more than 3 times in less than a year and the number of projects increases approximately in the same proportion, it seems that a not very critical, but rather unpleasant problem is brewing: how to coordinate vacations and time off of employees participating in several projects simultaneously? Thus was born a small project to automate applications for vacation.
The objectives of the project were as follows:
For implementation, it was decided to use the following software products:
Interface Design
The application form was designed using the capabilities of the DocTrix platform (a platform that extends the capabilities of SharePoint). It allows you to directly track the application tasks set by the workflow directly from the application form, has a built-in form designer, the ability to customize the display parameters of columns, dynamic display of columns and a bunch of other nice features.
As a result, the application form began to look like this:
Workflow Design
Workflows were decided to be designed using the Nintex workflow designer. Nintex has a wider range of features than the standard SharePoint designer. Moreover, in typical tasks of Nintex coordination there is an interesting Lazy Approval function, which allows to solve one of the project objectives, namely, the coordination of applications from the mail without using the SharePoint interface.
Thus, the approval of applications by the head was reduced to a simple response to the letter. This immediately solved the problem of coordination when the manager is on a business trip or departure (which is quite often in our business).
Another “trick” of Nintex is that the user who has the appropriate permissions has the ability to view the processing history of his application in a more visual, graphical form. Nintex highlights the passed process fragments in green, not started - gray, current - yellow.
After approval by all managers, the status of the application changes, and notifications about the results of its processing are sent to the responsible persons.
When the applications were already implemented, the largest response was the function of reminding the managers about the release of their employee from vacation.
With seemingly minimal costs and relatively small functionality, only the automation of vacations can save companies a rather large amount (the time for approval of applications decreases several times, the motivation of employees does not decrease from walking around the offices and so on - and this, ultimately, is a reduction in direct costs and loss of profit).
The objectives of the project were as follows:
- Reduce the total time to approve applications for holidays and time off;
- Obtain a mechanism for monitoring compliance with the Labor Code;
- Create a single point of registration of applications for vacation;
- Make transparent the process of approval of applications for vacation;
- Make it possible to coordinate vacations with mobile managers who do not have access to the interface;
- Make a system without the involvement of programmers, without a single line of code.
For implementation, it was decided to use the following software products:
- SharePoint Foundation 2010;
- DocTrix Platorm 2010;
- Nintex Workflow 2010.
Stages of implementation
Interface Design
The application form was designed using the capabilities of the DocTrix platform (a platform that extends the capabilities of SharePoint). It allows you to directly track the application tasks set by the workflow directly from the application form, has a built-in form designer, the ability to customize the display parameters of columns, dynamic display of columns and a bunch of other nice features.
As a result, the application form began to look like this:
Workflow Design
Workflows were decided to be designed using the Nintex workflow designer. Nintex has a wider range of features than the standard SharePoint designer. Moreover, in typical tasks of Nintex coordination there is an interesting Lazy Approval function, which allows to solve one of the project objectives, namely, the coordination of applications from the mail without using the SharePoint interface.
Thus, the approval of applications by the head was reduced to a simple response to the letter. This immediately solved the problem of coordination when the manager is on a business trip or departure (which is quite often in our business).
Another “trick” of Nintex is that the user who has the appropriate permissions has the ability to view the processing history of his application in a more visual, graphical form. Nintex highlights the passed process fragments in green, not started - gray, current - yellow.
After approval by all managers, the status of the application changes, and notifications about the results of its processing are sent to the responsible persons.
When the applications were already implemented, the largest response was the function of reminding the managers about the release of their employee from vacation.
With seemingly minimal costs and relatively small functionality, only the automation of vacations can save companies a rather large amount (the time for approval of applications decreases several times, the motivation of employees does not decrease from walking around the offices and so on - and this, ultimately, is a reduction in direct costs and loss of profit).
')
Source: https://habr.com/ru/post/138145/
All Articles