20
1 Description of Change / New Functionality / Business Requirement
1.1 Detailed Requirement
When a leave request has been created and approved, of a type of leave that requires a reason code to be associated, there are numerous screens in which that reason code is not visible. Those screens are:
Request time off screen/dates grid
Approved time off screen
Update time off screen/Dates grid
Update time off amend details section
1.2 Business Case
Numerous Rotork users have had issues understanding what leave had been booked either in the booking process, viewing it after approval or in trying to amend it, which is causing numerous questions to the core HR team and internal Rotork helpdesk tickets being raised
1.3 Benefits / Improvements
Reduction in confusion with what the system is booking/displaying when booking leave types that require reason codes, as the code will be displayed where being entered/having been entered/being altered.
1.4 Current Solution
Currently the reason code associated with leave types that require it is not displayed in the screens mentioned in 5.1:
Request time off screen/dates grid
Approved time off screen
Update time off screen/Dates grid
Update time off details
1.5 Proposed Solution
To add the reason code as a column into all of the above screenshots as a header and populated values associated with the leave line/s where applicable.
In the case of the amend time off screen, the reason code selected at the time of creation should be displayed to be amended if required.
1.1 Detailed Requirement
When a leave request has been created and approved, of a type of leave that requires a reason code to be associated, there are numerous screens in which that reason code is not visible. Those screens are:
Request time off screen/dates grid
Approved time off screen
Update time off screen/Dates grid
Update time off amend details section
1.2 Business Case
Numerous Rotork users have had issues understanding what leave had been booked either in the booking process, viewing it after approval or in trying to amend it, which is causing numerous questions to the core HR team and internal Rotork helpdesk tickets being raised
1.3 Benefits / Improvements
Reduction in confusion with what the system is booking/displaying when booking leave types that require reason codes, as the code will be displayed where being entered/having been entered/being altered.
1.4 Current Solution
Currently the reason code associated with leave types that require it is not displayed in the screens mentioned in 5.1:
Request time off screen/dates grid
Approved time off screen
Update time off screen/Dates grid
Update time off details
1.5 Proposed Solution
To add the reason code as a column into all of the above screenshots as a header and populated values associated with the leave line/s where applicable.
In the case of the amend time off screen, the reason code selected at the time of creation should be displayed to be amended if required.
STATUS DETAILS
Needs Votes
Comments
this would be a great addition for both back office and MSS to ensure that managers have the most accurate information to manager their team effectively
Category: Leave and Absence
Administrator on 8/14/2020 8:04:15 PM
Thank you for your suggestion. To help us in our review process, we’re requesting votes from the community to help us understand the importance of this functionality. This posting is provided “as is” with no warranties, and confers no rights.