Contents
Workflow Approval
The workflow approval is a unique centralizing system connecting the modules in the ERP. The purpose is to know whether the approval from the authorized person is under what stage of approval, for whatever the request posted. The purpose is to check the approval status from the authorized person (accepted/rejected/pending) for the request already sent for approval. Let’s understand it further.
As we can see two tabs -
Request To Me -
In this tab, an employee who sends a request for approval can find the task created by an employee who under and to the specific person who is given permission to approve. In this tab, the employee finds the list of tasks that are to be approved by him. In other words, he finds the list of tasks created by others ( usually his subordinates/juniors) & sent to him for approval. For example, Department head, Project lead, or Team Lead, a senior profile to sanction can find the request sent by an employee.
On approval, the task turns out to be an approved task for the person who has sent the request. The request that is sent turns to be a task for the Authorized person.
As we can see the highlighted portions, the Approval for a task for the Correction in ESS screen. This task was initiated by an employee to the Authorized person who has to rectify the issue. The task was created on a specific date and it is Waiting for Approval and also if the task is still in pending, the employee can use the “Ask” option as a reminder
Request By Me -
‘Request by Me’ falls in the same category, as the same as ‘Request to Me’. In this, whatever the request created by a concerned person can view the details here,
Here the employee can find the status of the request, whether the approval has been accepted, rejected, or not yet taken any action. The Remarks are made available on this screen because the employee can convey the nature of the request. Why Casual leave is requested, and whether the request is accepted or pending, or due to lack of leaves the leave has been rejected.
- Accept - Accept button is used by both the employee and the sanctioning authority. If the Sanctioning authority declines the request, the employee can read the cause why it is declined and then he/she has to accept it.
- Resend - Resend button is used when the request didn't reach the concerned person.
- Reject - Reject button as said earlier for both the employee and the sanctioning person.
- Who has applied it and who will be the Point of Approval for the request.
- On Date, the request was sent for approval
- Day the person has applied
- Purpose of the approval
Leave Request Application
Task type - 1
Task type – 2
After creating the request, an email confirmation will be sent to the employee who has requested for approval of leave, with the specific details as the picture above. If any correction needed the employee can rectify the request.
Task type – 3
The leave has been approved by the authorized person, but the leave approved is being Loss of Pay for the employee.
Note: So here, Mr. XYZ has applied for a casual leave to Mr. XYZ on the date and the complete process can be seen. The application will be shown in this format.
All these concepts are subject to change as per company policy.Revisions
- June 15, 2020 @ 11:13:10 [Current Revision] by admin
- June 15, 2020 @ 11:13:17 [Autosave] by admin
- June 15, 2020 @ 11:13:10 by admin
- May 21, 2020 @ 06:02:53 by admin
- May 18, 2020 @ 05:55:00 by admin
- April 20, 2020 @ 07:12:48 by admin
- April 20, 2020 @ 06:48:45 by admin
- April 11, 2020 @ 10:52:32 by admin
- April 11, 2020 @ 10:50:49 by admin
- April 11, 2020 @ 08:14:49 by admin
- April 11, 2020 @ 08:14:31 by admin
- April 9, 2020 @ 07:53:41 by admin
Revision Differences
| April 20, 2020 @ 07:12:48 | Current Revision | ||
|---|---|---|---|
| Content | |||
| Unchanged: <h1><strong>Workflow Approval</strong></h1> | Unchanged: <h1><strong>Workflow Approval</strong></h1> | ||
| Deleted: The workflow approval is a unique centralizing system connecting the modules in the ERP. The purpose is to | Added: The workflow approval is a unique centralizing system connecting the modules in the ERP. The purpose is to know whether the approval from the authorized person is under what stage of approval, for whatever the request posted. <span style="font-weight: 400;">The purpose is to check the approval status from the authorized person (accepted/rejected/pending) for the request already sent for approval.</span> | ||
| Added: Let’s understand it further. | |||
| Deleted: <a href="https:/ /help.goodbookserp.com/wp- content/uploads/2020/04/WA- 1- | Added: <a href="https:/ /help.goodbookserp.com/wp- content/uploads/2020/04/WA- 1-3.png"><img class="size-full wp-image-12799 alignnone" src="https:// help.goodbookserp.com/wp- content/uploads/ 2020/04/WA-1-3.png" alt="" width="576" height="203" /></a> | ||
| Deleted: | |||
| Deleted: | |||
| Deleted: | |||
| Deleted: | |||
| Deleted: | |||
| Deleted: | |||
| Unchanged: As we can see two tabs - | Unchanged: As we can see two tabs - | ||
| Unchanged: <strong>Request To Me - </strong> | Unchanged: <strong>Request To Me - </strong> | ||
| Deleted: <a href="https:/ /help.goodbookserp.com/wp- content/uploads/2020/04/WA- 2- | Added: <a href="https:/ /help.goodbookserp.com/wp- content/uploads/2020/04/WA- 2-4.png"><img class="size-full wp-image-12805 alignnone" src="https:// help.goodbookserp.com/wp- content/uploads/ 2020/04/WA-2-4.png" alt="" width="780" height="222" /></a> | ||
| Deleted: | |||
| Added: <span style="font-weight: 400;">In this tab, an employee who sends a request for approval can find the task created by an employee who under and to the specific person who is given permission to approve. </span><span style="font-weight: 400;">In this tab, the employee finds the list of tasks that are to be approved by him. In other words, he finds the list of tasks created by others ( usually his subordinates/juniors) & sent to him for approval. </span><span style="font-weight: 400;">For example, Department head, Project lead, or Team Lead, a senior profile to sanction can find the request sent by an employee.</span> | |||
| Deleted: In this tab, an employee who sends a request for approval can find the task created and to the specific person who is given permission to approve. For example, Department head, Project lead or Team lead, a senior profile to sanction can find the request sent by an employee. | Added: <span style="font-weight: 400;">On approval, the task turns out to be an approved task for the person who has sent the request. </span><span style="font-weight: 400;">The request that is sent turns to be a task for the Authorized person. </span> | ||
| Deleted: The request that is sent turns to be a task for the Authorized person. | |||
| Deleted: Here the employee can find the status of the request, | |||
| Unchanged: As we can see the highlighted portions, the <strong>Approval for a task</strong> for the <strong>Correction in ESS screen</strong>. This task was initiated by an employee to the Authorized person who has to rectify the issue. The task was created on a specific date and it is Waiting for Approval and also if the task is still in pending, the employee can use the “Ask” option as a reminder | Unchanged: As we can see the highlighted portions, the <strong>Approval for a task</strong> for the <strong>Correction in ESS screen</strong>. This task was initiated by an employee to the Authorized person who has to rectify the issue. The task was created on a specific date and it is Waiting for Approval and also if the task is still in pending, the employee can use the “Ask” option as a reminder | ||
| Unchanged: <strong>Request By Me - </strong> | Unchanged: <strong>Request By Me - </strong> | ||
| Deleted: | Added: ‘Request by Me’ falls in the same category, as the same as ‘Request to Me’. In this, whatever the request created by a concerned person can view the details here, | ||
| Added: <a href="https:/ /help.goodbookserp.com/wp- content/uploads/ 2020/04/WA3.gif"><img class="size-full wp-image-12806 alignnone" src="https:// help.goodbookserp.com/wp- content/uploads/ 2020/04/WA3.gif" alt="" width="918" height="450" /></a> | |||
| Added: Here the employee can find the status of the request, whether the approval has been accepted, rejected, or not yet taken any action. The Remarks are made available on this screen because the employee can convey the nature of the request. <span style="font-weight: 400;">Why Casual leave is requested, and whether the request is accepted or pending, or due to lack of leaves the leave has been rejected. </span> | |||
| Deleted: <a href="https:/ /help.goodbookserp.com/wp- content/uploads/2020/04/WA- | Added: <a href="https:/ /help.goodbookserp.com/wp- content/uploads/2020/04/WA- 7-2.png"><img class="size-full wp-image-12807 alignnone" src="https:// help.goodbookserp.com/wp- content/uploads/ 2020/04/WA-7-2.png" alt="" width="379" height="66" /></a> | ||
| Deleted: Here the employee can find the status of the request, whether the approval has been accepted, rejected, or not yet taken any action. The Remarks are made available in this screen because the employee can convey the nature of the request. | |||
| Deleted: <a href="https:/ /help.goodbookserp.com/wp- content/uploads/2020/04/WA- 7-1.png"><img class="size-full wp-image-12431 alignnone" src="https:// help.goodbookserp.com/wp- content/uploads/ 2020/04/WA-7-1.png" alt="" width="383" height="73" /></a> | |||
| Unchanged: <ol> | Unchanged: <ol> | ||
| Unchanged: <li>Accept - Accept button is used by both the employee and the sanctioning authority. If the Sanctioning authority declines the request, the employee can read the cause why it is declined and then he/she has to accept it.</li> | Unchanged: <li>Accept - Accept button is used by both the employee and the sanctioning authority. If the Sanctioning authority declines the request, the employee can read the cause why it is declined and then he/she has to accept it.</li> | ||
| Unchanged: <li>Resend - Resend button is used when the request didn't reach the concerned person.</li> | Unchanged: <li>Resend - Resend button is used when the request didn't reach the concerned person.</li> | ||
| Unchanged: <li>Reject - Reject button as said earlier for both the employee and the sanctioning person.</li> | Unchanged: <li>Reject - Reject button as said earlier for both the employee and the sanctioning person.</li> | ||
| Unchanged: </ol> | Unchanged: </ol> | ||
| Unchanged: Both the request types are available in all the modules in the ERP tool. Kindly consider that this request may not be provided for all the employees, upon the request, Organizations can open for applying the request. | Unchanged: Both the request types are available in all the modules in the ERP tool. Kindly consider that this request may not be provided for all the employees, upon the request, Organizations can open for applying the request. | ||
| Unchanged: A sample screenshot has been attached for clear understanding, | Unchanged: A sample screenshot has been attached for clear understanding, | ||
| Unchanged: <ol> | Unchanged: <ol> | ||
| Unchanged: <li>Who has applied it and who will be the Point of Approval for the request.</li> | Unchanged: <li>Who has applied it and who will be the Point of Approval for the request.</li> | ||
| Unchanged: <li>On Date, the request was sent for approval</li> | Unchanged: <li>On Date, the request was sent for approval</li> | ||
| Unchanged: <li>Day the person has applied</li> | Unchanged: <li>Day the person has applied</li> | ||
| Unchanged: <li>Purpose of the approval</li> | Unchanged: <li>Purpose of the approval</li> | ||
| Unchanged: </ol> | Unchanged: </ol> | ||
| Unchanged: The employee who requested for the particular application can view it here, and the same for the person who has to sanction the approval | Unchanged: The employee who requested for the particular application can view it here, and the same for the person who has to sanction the approval | ||
| Unchanged: To understand further a sample request and the approval pages for leave requests are attached. When the application is sanctioned or rejected the request will be intimated in email and also on the workflow page. | Unchanged: To understand further a sample request and the approval pages for leave requests are attached. When the application is sanctioned or rejected the request will be intimated in email and also on the workflow page. | ||
| Unchanged: <h2><strong>Leave Request Application</ strong></h2> | Unchanged: <h2><strong>Leave Request Application</ strong></h2> | ||
| Unchanged: <strong> </strong> <strong>Task type - 1</strong> | Unchanged: <strong> </strong> <strong>Task type - 1</strong> | ||
| Unchanged: <a href="https:/ /help.goodbookserp.com/wp- content/uploads/ 2020/04/WA-4.png"><img class="size-full wp-image-12119 alignnone" src="https:// help.goodbookserp.com/wp- content/uploads/ 2020/04/WA-4.png" alt="" width="741" height="264" /></a> | Unchanged: <a href="https:/ /help.goodbookserp.com/wp- content/uploads/ 2020/04/WA-4.png"><img class="size-full wp-image-12119 alignnone" src="https:// help.goodbookserp.com/wp- content/uploads/ 2020/04/WA-4.png" alt="" width="741" height="264" /></a> | ||
| Unchanged: <strong>Task type – 2</strong> | Unchanged: <strong>Task type – 2</strong> | ||
| Unchanged: <strong> <a href="https:/ /help.goodbookserp.com/wp- content/uploads/ 2020/04/WA-5.png"><img class="size-full wp-image-12120 alignnone" src="https:// help.goodbookserp.com/wp- content/uploads/ 2020/04/WA-5.png" alt="" width="719" height="250" /></a></strong> | Unchanged: <strong> <a href="https:/ /help.goodbookserp.com/wp- content/uploads/ 2020/04/WA-5.png"><img class="size-full wp-image-12120 alignnone" src="https:// help.goodbookserp.com/wp- content/uploads/ 2020/04/WA-5.png" alt="" width="719" height="250" /></a></strong> | ||
| Deleted: After creating the request, an <strong>email confirmation</strong> will be sent to the employee who has requested for approval of leave, with the specific details as the picture above. If any correction needed the employee can rectify the request | Added: After creating the request, an <strong>email confirmation</strong> will be sent to the employee who has requested for approval of leave, with the specific details as the picture above. If any correction needed the employee can rectify the request. | ||
| Unchanged: <strong>Task type – 3</strong> | Unchanged: <strong>Task type – 3</strong> | ||
| Unchanged: <a href="https:/ /help.goodbookserp.com/wp- content/uploads/ 2020/04/WA-6.png"><img class="size-full wp-image-12121 alignnone" src="https:// help.goodbookserp.com/wp- content/uploads/ 2020/04/WA-6.png" alt="" width="701" height="234" /></a> | Unchanged: <a href="https:/ /help.goodbookserp.com/wp- content/uploads/ 2020/04/WA-6.png"><img class="size-full wp-image-12121 alignnone" src="https:// help.goodbookserp.com/wp- content/uploads/ 2020/04/WA-6.png" alt="" width="701" height="234" /></a> | ||
| Unchanged: The leave has been approved by the authorized person, but the leave approved is being Loss of Pay for the employee. | Unchanged: The leave has been approved by the authorized person, but the leave approved is being Loss of Pay for the employee. | ||
| Unchanged: <strong>Note:</strong> So here, <strong>Mr. XYZ </strong>has applied for a casual leave to <strong>Mr. XYZ </strong> on the date and the complete process can be seen. The application will be shown in this format. | Unchanged: <strong>Note:</strong> So here, <strong>Mr. XYZ </strong>has applied for a casual leave to <strong>Mr. XYZ </strong> on the date and the complete process can be seen. The application will be shown in this format. | ||
| Unchanged: All these concepts are subject to change as per company policy. | Unchanged: All these concepts are subject to change as per company policy. | ||
Note: Spaces may be added to comparison text to allow better line wrapping.
