Uploaded image for project: 'WORKTERRA'
  1. WORKTERRA
  2. WT-13231

LB | Partner | Change Status | Server Error

    Details

    • Type: Bug
    • Status: In Development
    • Priority: Critical
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: BenAdmin
    • Labels:
      None
    • Environment:
      QA
    • Bug Type:
      Functional
    • Bug Severity:
      Medium
    • Level:
      Partner
    • Module:
      BenAdmin - EDS
    • Reported by:
      Harbinger
    • Company:
      All Clients/Multiple Clients

      Description

      Environment: LB
      Company: For Qa FDU for hspl, For QA Caso for hspl, For Qa ILG for hspl, All companies
      Login: Partner

      Issue: getting Server error on Changing Status

      Steps:
      Partner login > Employee Home > Change Status Page > Change Status > Reason > Add Date > Save > Server error

      Screen capture and Error log attached with jira.

      Hrishikesh Deshpande

        Attachments

          Issue Links

            Activity

            priya.dhamande Priya Dhamande (Inactive) created issue -
            hrishikesh.deshpande Hrishikesh Deshpande (Inactive) made changes -
            Field Original Value New Value
            Priority Medium [ 3 ] Highest [ 1 ]
            priya.dhamande Priya Dhamande (Inactive) made changes -
            Link This issue blocks WT-12894 [ WT-12894 ]
            swapnil.pandhare Swapnil Pandhare (Inactive) made changes -
            Assignee Swapnil Pandhare [ swapnil.pandhare ] Niteen Surwase [ niteen.surwase ]
            niteen.surwase Niteen Surwase (Inactive) made changes -
            Status Open [ 1 ] In Development [ 10007 ]
            niteen.surwase Niteen Surwase (Inactive) made changes -
            Remaining Estimate 0h [ 0 ]
            Original Estimate 0h [ 0 ]
            niteen.surwase Niteen Surwase (Inactive) made changes -
            Original Estimate 0h [ 0 ] 1h [ 3600 ]
            niteen.surwase Niteen Surwase (Inactive) made changes -
            Time Spent 7h [ 25200 ]
            Worklog Id 103583 [ 103583 ]
            Hide
            niteen.surwase Niteen Surwase (Inactive) added a comment -

            We have started Analysis on this issue, This issue is caused by WT-10837 ticket fix. So, first we'll do analysis on WT-10837 and we'll share the ETA.

            CC: Swapnil Pandhare

            Show
            niteen.surwase Niteen Surwase (Inactive) added a comment - We have started Analysis on this issue, This issue is caused by WT-10837 ticket fix. So, first we'll do analysis on WT-10837 and we'll share the ETA. CC: Swapnil Pandhare
            niteen.surwase Niteen Surwase (Inactive) logged work - 06/Feb/18 05:00 PM
            • Time Spent:
              7h
               

              Analysis of the issue on Local
              System Debugging to reproduce and check issue
              Reverted and Testing this issue.
              Analysis for WT-10837 issue
              Discussion with Komal

            niteen.surwase Niteen Surwase (Inactive) made changes -
            Time Spent 7h [ 25200 ] 9.25h [ 33300 ]
            Worklog Id 103878 [ 103878 ]
            niteen.surwase Niteen Surwase (Inactive) logged work - 08/Feb/18 05:00 PM
            • Time Spent:
              2.25h
               

              Analysis and Debugging for issue
              Reproducing WT-10837 by reverting changes

            Hide
            niteen.surwase Niteen Surwase (Inactive) added a comment - - edited

            We are analyzing the WT-10837 and WT-13231 as well to avoid contradiction to each other.
            We need to either re-fix WT- 10837 or fix WT- 13231 such way that it'll not contradict other one.

            SP : dbo.OES_SP_GENERIC_EFFECTIVEDATE_CALCULATION.StoredProcedure

            CC: Swapnil Pandhare

            Show
            niteen.surwase Niteen Surwase (Inactive) added a comment - - edited We are analyzing the WT-10837 and WT-13231 as well to avoid contradiction to each other. We need to either re-fix WT- 10837 or fix WT- 13231 such way that it'll not contradict other one. SP : dbo.OES_SP_GENERIC_EFFECTIVEDATE_CALCULATION.StoredProcedure CC: Swapnil Pandhare
            niteen.surwase Niteen Surwase (Inactive) made changes -
            Time Spent 9.25h [ 33300 ] 16.25h [ 58500 ]
            Worklog Id 104043 [ 104043 ]
            niteen.surwase Niteen Surwase (Inactive) logged work - 09/Feb/18 05:00 PM
            • Time Spent:
              7h
               

              Full analysis of WT- 10837 and this ticket
              Reverting WT- 10837 and checking original issue.
              Debug to resolve contadiction

            swapnil.pandhare Swapnil Pandhare (Inactive) logged work - 09/Feb/18 07:25 PM
            • Time Spent:
              0.5h
               

              Discussion with Niteen

            swapnil.pandhare Swapnil Pandhare (Inactive) made changes -
            Time Spent 16.25h [ 58500 ] 16.75h [ 60300 ]
            Worklog Id 104108 [ 104108 ]
            niteen.surwase Niteen Surwase (Inactive) logged work - 13/Feb/18 02:16 PM
            • Time Spent:
              6h
               

              Analysis and debugging for NH issue
              Checking issue with WT-10837
              Analysis on conflict.

            Hide
            niteen.surwase Niteen Surwase (Inactive) added a comment -

            Analysis:

            WT-13231 Issue :
            Shows server error on Change Status page because OES_SP_GENERIC_EFFECTIVEDATE_CALCULATION return NULL value as Hire Date/Employment Date. And this issue occurred due to WT-10837 changes.

            Scenario :
            If Today's Date - 02/13/2018
            Employment Date - 20/02/2018
            Effective Date - 20/02/2018

            Then OES_SP_GENERIC_EFFECTIVEDATE_CALCULATION
            return NULL DB value and Exception thrown at Business Logic cause NULL result not handled at BL.

            WT-10837 Issue :
            If we set future Hire Date/Employment Date then it allow employees to use New Hire mode to make changes which should not do.

            Scenario:
            If we'll revert WT-10837 changes from OES_SP_GENERIC_EFFECTIVEDATE_CALCULATION
            then it'll return Hire Date as Effective Date and WT-13231 will works as expected
            BUT, as we reverted WT-10837, then issue of Future New Hire remain exists.

            Enroll Now : If it is the case of Future New Hire it does not check either employee is eligible for Demographics Criteria or Not
            Workflow : Future Effective Date returns and starts work-flow. Not checked either Employee is eligible or not.
            Demographics criteria not checked in dbo.OES_SP_Get_EnrollmentModesForEmployee.StoredProcedure (if reverted WT-10837)

            Temporary Solution : We can handle DB NULL value exception at BL.
            We have to fix Employee's Future New Hire mode from Enroll Now screen and Workflow screen.

            We'll share the ETAs after discussion in design meeting.

            Thanks,
            Niteen

            Show
            niteen.surwase Niteen Surwase (Inactive) added a comment - Analysis: WT-13231 Issue : Shows server error on Change Status page because OES_SP_GENERIC_EFFECTIVEDATE_CALCULATION return NULL value as Hire Date/Employment Date. And this issue occurred due to WT-10837 changes. Scenario : If Today's Date - 02/13/2018 Employment Date - 20/02/2018 Effective Date - 20/02/2018 Then OES_SP_GENERIC_EFFECTIVEDATE_CALCULATION return NULL DB value and Exception thrown at Business Logic cause NULL result not handled at BL. WT-10837 Issue : If we set future Hire Date/Employment Date then it allow employees to use New Hire mode to make changes which should not do. Scenario: If we'll revert WT-10837 changes from OES_SP_GENERIC_EFFECTIVEDATE_CALCULATION then it'll return Hire Date as Effective Date and WT-13231 will works as expected BUT, as we reverted WT-10837 , then issue of Future New Hire remain exists. Enroll Now : If it is the case of Future New Hire it does not check either employee is eligible for Demographics Criteria or Not Workflow : Future Effective Date returns and starts work-flow. Not checked either Employee is eligible or not. Demographics criteria not checked in dbo.OES_SP_Get_EnrollmentModesForEmployee.StoredProcedure (if reverted WT-10837 ) Temporary Solution : We can handle DB NULL value exception at BL. We have to fix Employee's Future New Hire mode from Enroll Now screen and Workflow screen. We'll share the ETAs after discussion in design meeting. Thanks, Niteen
            niteen.surwase Niteen Surwase (Inactive) made changes -
            Time Spent 16.75h [ 60300 ] 22.75h [ 81900 ]
            Worklog Id 104428 [ 104428 ]
            Hide
            niteen.surwase Niteen Surwase (Inactive) added a comment -

            Scenarios:
            Toggle : System Settings >> Allow Changes without Qualifying Event (For Demographics, Child, Spouse and Emergency)
            Unit Testing required through SA/P/CA/EE Login

            Today's Date - 02/15/2018 and Mode - 31 Days

            Employee is Eligible with demographics criteria:

            Employment Date NH Time
            02/10/2018 Current NH
            02/20/2018 Future NH
            01/10/2018 Past NH

            Employee is not Eligible with demographics criteria:

            Employment Date NH Time
            02/10/2018 Current NH
            02/20/2018 Future NH
            01/10/2018 Past NH

            ETAs and Pages to make NH changes:

            Sr. No Screen ETA in Hrs
            1 Enroll Now 4 Hrs Development (BL)
            - - 4 Hrs Unit Testing with all above scenarios
            2 Employee NH Work-flow 4 Hrs Development (SP)
            - - 4 Hrs Unit Testing with all above scenarios
            3 Demogra., Child, Spouse & Add. Form Load & Save 4 Hrs Development(Debug)
            - - 4 Hrs Unit Testing with all above scenarios
            - Total Hrs 24 Hrs

            CC: Swapnil Pandhare Satya

            Show
            niteen.surwase Niteen Surwase (Inactive) added a comment - Scenarios: Toggle : System Settings >> Allow Changes without Qualifying Event (For Demographics, Child, Spouse and Emergency) Unit Testing required through SA/P/CA/EE Login Today's Date - 02/15/2018 and Mode - 31 Days Employee is Eligible with demographics criteria: Employment Date NH Time 02/10/2018 Current NH 02/20/2018 Future NH 01/10/2018 Past NH Employee is not Eligible with demographics criteria: Employment Date NH Time 02/10/2018 Current NH 02/20/2018 Future NH 01/10/2018 Past NH ETAs and Pages to make NH changes : Sr. No Screen ETA in Hrs 1 Enroll Now 4 Hrs Development (BL) - - 4 Hrs Unit Testing with all above scenarios 2 Employee NH Work-flow 4 Hrs Development (SP) - - 4 Hrs Unit Testing with all above scenarios 3 Demogra., Child, Spouse & Add. Form Load & Save 4 Hrs Development(Debug) - - 4 Hrs Unit Testing with all above scenarios - Total Hrs 24 Hrs CC: Swapnil Pandhare Satya
            niteen.surwase Niteen Surwase (Inactive) logged work - 14/Feb/18 01:23 PM
            • Time Spent:
              5.5h
               

              Analysis and Debugging
              Code Changes and Unit testing
              Discussion with Swapnil

            niteen.surwase Niteen Surwase (Inactive) made changes -
            Time Spent 22.75h [ 81900 ] 28.25h [ 101700 ]
            Worklog Id 104581 [ 104581 ]
            swapnil.pandhare Swapnil Pandhare (Inactive) logged work - 14/Feb/18 07:16 PM
            • Time Spent:
              1.5h
               

              Analysis & Discussion with Niteen

            swapnil.pandhare Swapnil Pandhare (Inactive) made changes -
            Time Spent 28.25h [ 101700 ] 29.75h [ 107100 ]
            Worklog Id 104979 [ 104979 ]
            Transition Time In Source Status Execution Times
            Niteen Surwase (Inactive) made transition -
            Open In Development
            6d 2h 52m 1

              People

              Assignee:
              niteen.surwase Niteen Surwase (Inactive)
              Reporter:
              priya.dhamande Priya Dhamande (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:

                  Time Tracking

                  Estimated:
                  Original Estimate - 1h Original Estimate - 1h
                  1h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 29.75h
                  29.75h