Hi Sanjay,

There is a scenario at LTA where the user was allowed to apply for more days of leave despite having the leave check balance on.

Consider the following scenario:

Employee "alfred.wiliame" has Long Service Leave balance for  15 days. Refer to the followings steps, that allows him to make the transaction for 18 days despite having the check leave flag enabled for Long Service Leave.

1. Login into ESS by "alfred.wiliame", password "12"
2. Make a Long Service Leave transaction for the date 15/12/2016 - 16/12/2016.
3. Save the transaction.
4. Make another Long Service transaction for the date of 19/12/2016 - 23/12/2016.
5. Save the transaction.
6. Make another Long Service transaction for the date of 2812/2016 - 30/12/2016.
7. Save the transaction.
8. Make another Long Service transaction for the date of 02/01/2017 - 06/01/2017.
9. Save the transaction.
10. Make another Long Service transaction for the date of 09/01/2017 - 13/01/2017.
11. Upon saving, the system would prompt the user saying "Save unsuccessful. You have exceeded your leave balance. Available balance is 8.00".
12. The user then changes the Leave Type to "Annual Leave" and saves the transaction and closes the screen.
13. The user now edits this "Annual Leave" transaction and changes the Leave Type back to "Long Service" and saves.
14. The system allows the user to do this.

I have tested the same scenario on our demo database and the system does not allow this scenario to occur.

The LTA database is in QA4 as DB: CLIENT-LTA-LINKSOFT.

Please kindly look into this.

Regards
Aarti Gayaneshwar

Hi Aarti, 

there is insufficient information in this case for me to investigate.

Have you considered that the client may have turned off the "Check leave balance flag" before applying for leave, then turn the flag on.

Can you look at setting up "SQL Audit" to verify this?

regards
Alvis

Dear Alvis,

This case has been reproduced in the LTA database setup in QA4 as DB: CLIENT-LTA-LINKSOFT.

Regards
Aarti Gayaneshwar