4

Currently, if a leave request is cancelled, it results in creating a second leave request that reverses the first leave request (which is put into Completed state). The problem is that neither the new leave request (cancellation request) nor the old leave request (approved leave) has links to each other in the LeaveRequestHeader or LeaveRequestV2 entities. This behavior complicates the integration scenarios and leave request transaction analysis.

It would be good to add new parameter “Add cancellation line/s on original request”, if enabled to allow additional leave request lines of type cancelled in the original leave request ID. On disabled state, one to many relations available separately to trace back (both direction) to original leaves at line level.

STATUS DETAILS
Needs Votes
Ideas Administrator

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.

Comments

R

It would be good to add new parameter “Add cancellation line/s on original request”, if enabled to allow additional leave request lines of type cancelled in the original leave request ID. On disabled state, one to many relations available separately to trace back (both direction) to original leaves at line level.

Category: Leave and Absence