Using Project Manager as step type for approval routes
Introduction
You should be aware of the outcomes when you use Project Manager as step type for an approval route. Below is a summary of some scenarios and what the outcome would be when you use Project Manager as step type for your approval routes:
Sample Scenarios
- Employee X is working on two projects as the same time:
- Project A is managed by manager A
- Project B is managed by manager B
- The system will split the time sheet into two time sheets (behind the scene):
- Sub-time sheet A will go to manager A
- Sub-time sheet B will go to manager B
- If manager A approves it during the first day, the employee's time sheet will show as "Submitted."
- The next day manager B can approve or reject.
- Note that if manager B rejects it, the employee will get an email stating that his time sheet was "Partially Rejected," so they will need to fix this and submit it again.
- Employee X is working on two projects as the same time:
- Project A is managed by manager A.
- Project B is managed by manager B.
- Employee is logging time against tickets.
- Project A has approval route 1.
- Tickets under Company Setting has approval route.
- The system will split the time sheet into two time sheets:
- Sub-timesheet (time entries for project A)
- Sub-timesheet (time entries for project B)
- Sub-timesheet A will go to manager A.
- Sub-timesheet B will go to manager B.
- If manager A approves it during the first day, the employee's time sheet will show as "Submitted."
- The next day manager B can approve or reject.
- Recursive example - Approvals are forwarded from one supervisor to the next, ascending the levels of the organizational chart, for the number of levels you specify.
- Employee works from 8:00 AM until 6:00 PM.
- Ticket's last activity time was 5:00 PM.
- If the ticket is attached to an service-level agreement (SLA) business hours.
- The workflow will not trigger at 8:00 PM.
- The workflow will run at 10:00 AM on the second day.
Applies to: BMS email parser
