Details

    • Type: Bug
    • Status: Closed
    • Priority: High
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: BenAdmin
    • Labels:
      None
    • Environment:
      Production
    • Module:
      BenAdmin - Enrollment
    • Reported by:
      Harbinger
    • Item State:
      Production QA - Production Deployed
    • Issue Importance:
      Must Have

      Description

      UND FOR HSPL - Production

      1. employee raised Divorce QE
      2. Removed a coverage member from his existing enrollment (or make any changes in election)
      3. this election change request went for admin approval
      4. admin accepted it
      5. see this employee's view history

      Actual Result : earlier election termination record is shown without a QE name

      refer attached screen shot

        Attachments

        1. #1.png
          #1.png
          293 kB
        2. #2.png
          #2.png
          290 kB
        3. #3.png
          #3.png
          275 kB
        4. #4.png
          #4.png
          280 kB
        5. #5.png
          #5.png
          293 kB
        6. NO QE.png
          NO QE.png
          233 kB
        7. Production Screen Shots - Enrollments QE NULL ID.zip
          2.24 MB
        8. QE Scenarios.ods
          15 kB

          Issue Links

            Activity

            Hide
            sheetal.bodhale Sheetal Bodhale (Inactive) added a comment - - edited

            Alankar Chavan SatyaSwapnil Pandhare
            Hi Alankar,
            As discussed with Satya,as this is enrollment related issue.So please assign to enrollment team.
            And create separate JIRA ticket for employee data change i.e for change of spouse to ex-spouse.(this scenario is discussed with you.)

            Show
            sheetal.bodhale Sheetal Bodhale (Inactive) added a comment - - edited Alankar Chavan Satya Swapnil Pandhare Hi Alankar, As discussed with Satya,as this is enrollment related issue.So please assign to enrollment team. And create separate JIRA ticket for employee data change i.e for change of spouse to ex-spouse.(this scenario is discussed with you.)
            Hide
            alankar.chavan Alankar Chavan (Inactive) added a comment -

            Hello Amnesh Goel ,

            As per the above comment - assigning this to you.
            Whenever any changes are done on Enrollments - Requests goes for Admin Verification - Admin accepts the same request -> New enrollment is seen with a QE name on view History. Whereas the older Termination record shown without a QE name on View History. As per the discussions with developer - Passing QE id as NULL is causing this.

            Show
            alankar.chavan Alankar Chavan (Inactive) added a comment - Hello Amnesh Goel , As per the above comment - assigning this to you. Whenever any changes are done on Enrollments - Requests goes for Admin Verification - Admin accepts the same request -> New enrollment is seen with a QE name on view History. Whereas the older Termination record shown without a QE name on View History. As per the discussions with developer - Passing QE id as NULL is causing this.
            Hide
            sam.lindberg@ebsbenefits.com sam lindberg (Inactive) added a comment -

            Once the code in stage is user tested, can you send the ticket to Damion Valesquiz to test?

            Happy coding .

            Thank you,
            Sam

            Show
            sam.lindberg@ebsbenefits.com sam lindberg (Inactive) added a comment - Once the code in stage is user tested, can you send the ticket to Damion Valesquiz to test? Happy coding . Thank you, Sam
            Hide
            sam.lindberg@ebsbenefits.com sam lindberg (Inactive) added a comment -

            Whats the time line for this to be finished? We have a WEDS client deadline to be delivered to the client in stage.

            Show
            sam.lindberg@ebsbenefits.com sam lindberg (Inactive) added a comment - Whats the time line for this to be finished? We have a WEDS client deadline to be delivered to the client in stage.
            Hide
            girija.potdar Girija Potdar (Inactive) added a comment -

            Hi sam lindberg,

            We will deploy it on local environment today. After the QA testing is completed we will deploy it on Stage by tomorrow.
            Please let us know if you need more information.

            Thanks.

            Show
            girija.potdar Girija Potdar (Inactive) added a comment - Hi sam lindberg , We will deploy it on local environment today. After the QA testing is completed we will deploy it on Stage by tomorrow. Please let us know if you need more information. Thanks.
            Hide
            sam.lindberg@ebsbenefits.com sam lindberg (Inactive) added a comment -

            Can you put it in the UND For Banner Payroll Testing in prod too?

            Show
            sam.lindberg@ebsbenefits.com sam lindberg (Inactive) added a comment - Can you put it in the UND For Banner Payroll Testing in prod too?
            Hide
            alankar.chavan Alankar Chavan (Inactive) added a comment - - edited

            FYI Rakesh Roy Deepali Tidke Girija Potdar Sheetal Bodhale Satya

            This is verified on Stage - UND for HSPL

            Working well

            Please find the attached scenario list and screen shots - Testing in progress

            Show
            alankar.chavan Alankar Chavan (Inactive) added a comment - - edited FYI Rakesh Roy Deepali Tidke Girija Potdar Sheetal Bodhale Satya This is verified on Stage - UND for HSPL Working well Please find the attached scenario list and screen shots - Testing in progress
            Hide
            girija.potdar Girija Potdar (Inactive) added a comment -

            Concern:
            Whenever any changes are done on Enrollments - Requests goes for Admin Verification - Admin accepts the same request -> New enrollment is seen with a QE name on view History. Whereas the older Termination record shown without a QE name on View History

            Cause:
            Whenever the Admin accepts the same request, new enrollment is done where EnrollmentModeID and QualifyingeventID was getting updated correctly. But for the previous enrollment the QualifyingeventID was not getting updated. Thus on View History, The QE name was not getting shown for the previous recod.

            Correction:
            We have added the QualifyingeventID to the update query for old enrollment. This will now update QE id and display it on View History as well as Review Changes.

            Show
            girija.potdar Girija Potdar (Inactive) added a comment - Concern: Whenever any changes are done on Enrollments - Requests goes for Admin Verification - Admin accepts the same request -> New enrollment is seen with a QE name on view History. Whereas the older Termination record shown without a QE name on View History Cause: Whenever the Admin accepts the same request, new enrollment is done where EnrollmentModeID and QualifyingeventID was getting updated correctly. But for the previous enrollment the QualifyingeventID was not getting updated. Thus on View History, The QE name was not getting shown for the previous recod. Correction: We have added the QualifyingeventID to the update query for old enrollment. This will now update QE id and display it on View History as well as Review Changes.
            Hide
            alankar.chavan Alankar Chavan (Inactive) added a comment -

            This is tested on Stage - UND for HSPL - 21st April 2016
            QE name is shown on View History as well as on Pending Queue / Review Changes in case of any enrollment changes

            Show
            alankar.chavan Alankar Chavan (Inactive) added a comment - This is tested on Stage - UND for HSPL - 21st April 2016 QE name is shown on View History as well as on Pending Queue / Review Changes in case of any enrollment changes
            Hide
            sam.lindberg@ebsbenefits.com sam lindberg (Inactive) added a comment -

            When will this code be deployed in prod. As we have a client that urgently needs?

            Our testing in stage did not give the correct functionality based on preliminary test on UND.

            Show
            sam.lindberg@ebsbenefits.com sam lindberg (Inactive) added a comment - When will this code be deployed in prod. As we have a client that urgently needs? Our testing in stage did not give the correct functionality based on preliminary test on UND.
            Hide
            alankar.chavan Alankar Chavan (Inactive) added a comment -

            FYI Deepali Tidke Rakesh Roy Satya Sheetal Bodhale Girija Potdar

            Hello sam lindberg ,

            We tested the mentioned scenarios on Production - UND for HSPL. It worked well.

            Can you review this and let us know is there any scenario left where system is passing the QE ID as NULL ?

            In all the scenarios we tested - View History and Pending Queue requests showed us the QE name (which means QE ID was not NULL)

            Show
            alankar.chavan Alankar Chavan (Inactive) added a comment - FYI Deepali Tidke Rakesh Roy Satya Sheetal Bodhale Girija Potdar Hello sam lindberg , We tested the mentioned scenarios on Production - UND for HSPL. It worked well. Can you review this and let us know is there any scenario left where system is passing the QE ID as NULL ? In all the scenarios we tested - View History and Pending Queue requests showed us the QE name (which means QE ID was not NULL)
            Hide
            rakeshr Rakesh Roy (Inactive) added a comment -

            sam lindberg Please update for next action, if any.

            Show
            rakeshr Rakesh Roy (Inactive) added a comment - sam lindberg Please update for next action, if any.
            Hide
            sam.lindberg@ebsbenefits.com sam lindberg (Inactive) added a comment -

            No action needed

            Damion can you run the test payrol file again and capture the scenarios from the last run?

            Thank you,
            Sam

            Show
            sam.lindberg@ebsbenefits.com sam lindberg (Inactive) added a comment - No action needed Damion can you run the test payrol file again and capture the scenarios from the last run? Thank you, Sam

              People

              Assignee:
              Damion.Velasquez Damion M Velasquez
              Reporter:
              alankar.chavan Alankar Chavan (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: