WORKTERRAProject Type: software

WORKTERRA

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

Charleys: Auto Enroll plans are not enrolling automatically

    Details

    • Type: Bug
    • Status: Closed
    • Priority: High
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: BenAdmin
    • Labels:
      None
    • Environment:
      Stage
    • Bug Type:
      Functional
    • Bug Severity:
      Medium
    • Level:
      Employee
    • Module:
      BenAdmin - Enrollment
    • Reported by:
      Client
    • Company:
      Charleys Concrete
    • Item State:
      Production Complete - Closed
    • Sprint:
      WT Sprint 37 - Bugs

      Description

      Hi,
      we experienced an issue while testing. Subscriber entered manually are not getting auto enroll in the auto enroll plan(Basic life and Basic ADD) unless the record is imported or if we save a change on the demographic Page.

      For Instance:

      See screen shot
      Highlighted records were entered manually and didnt get auto enrolled.
      Panda test had demographic page updated and did get auto enrolled.
      Auto test is an example of imported record that was given benefit correctly.

      Could you please let us know 3cs?
      Thank you!
      Monika

      CC Robyn Adkison Jennifer Johnson Amanda Hagan Amannda Johnson Michelle Parker

        Attachments

        1. Add EE pop up.png
          Add EE pop up.png
          59 kB
        2. CS after changes.png
          CS after changes.png
          41 kB
        3. CS before changes.png
          CS before changes.png
          42 kB
        4. Enroll now.png
          Enroll now.png
          65 kB
        5. image-2017-09-12-17-35-06-835.png
          image-2017-09-12-17-35-06-835.png
          105 kB
        6. screenshot-1.png
          screenshot-1.png
          25 kB
        7. Server error.png
          Server error.png
          75 kB

          Activity

          Ascending order - Click to sort in descending order
          10 older comments
          Hide
          Permalink
          rashmita.dudhe Rashmita Dudhe (Inactive) added a comment -

          Verified on LB Environment consider scenarios for core plan:

          1] Core plan A with effective date 11/01/2017
          2]Core plan B effective date 01/01/2018
          3]Core plan C with effective date 07/15/2018
          4]Core plan D with effective date 01/01/2017

          Scenario #1
          Add an employee with effective date 01/01/2017

          Actual result: Employee enrolled in all core plan A, B, C, D with plan effective date

          Scenario #2
          Add an employee with effective date 09/01/2017

          Actual result: Employee enrolled in all core plan B, C with plan effective date

          Scenario #3
          Add an employee with effective date 01/01/2018

          Actual result: Employee enrolled in all core plan A, B, C with plan effective date

          Scenario #4
          import 10 records with different Date of employment.
          cross verified on confirmation statement employee enrolled in core plan with plan effective date

          Scenario #5
          Verified through core plan allocation service
          cross verified on confirmation statement employee enrolled in core plan with plan effective date

          Scenario #6
          Verified through SA utility
          cross verified on confirmation statement employee enrolled in core plan with plan effective date

          Scenario #7
          Verified by adding termination date.
          cross verified on confirmation statement employee enrolled in core plan with plan effective date and termination date is also set.

          working fine as expected

          Show
          rashmita.dudhe Rashmita Dudhe (Inactive) added a comment - Verified on LB Environment consider scenarios for core plan: 1] Core plan A with effective date 11/01/2017 2]Core plan B effective date 01/01/2018 3]Core plan C with effective date 07/15/2018 4]Core plan D with effective date 01/01/2017 Scenario #1 Add an employee with effective date 01/01/2017 Actual result: Employee enrolled in all core plan A, B, C, D with plan effective date Scenario #2 Add an employee with effective date 09/01/2017 Actual result: Employee enrolled in all core plan B, C with plan effective date Scenario #3 Add an employee with effective date 01/01/2018 Actual result: Employee enrolled in all core plan A, B, C with plan effective date Scenario #4 import 10 records with different Date of employment. cross verified on confirmation statement employee enrolled in core plan with plan effective date Scenario #5 Verified through core plan allocation service cross verified on confirmation statement employee enrolled in core plan with plan effective date Scenario #6 Verified through SA utility cross verified on confirmation statement employee enrolled in core plan with plan effective date Scenario #7 Verified by adding termination date. cross verified on confirmation statement employee enrolled in core plan with plan effective date and termination date is also set. working fine as expected
          Hide
          Permalink
          rashmita.dudhe Rashmita Dudhe (Inactive) added a comment -

          Verified on Stage Environment consider scenarios for core plan:
          1] Core plan A with effective date 11/01/2017
          2]Core plan B effective date 01/01/2018
          3]Core plan C with effective date 07/15/2018
          4]Core plan D with effective date 01/01/2017
          Scenario #1
          Add an employee with effective date 01/01/2017
          Actual result: Employee enrolled in all core plan A, B, C, D with plan effective date
          Scenario #2
          Add an employee with effective date 09/01/2017
          Actual result: Employee enrolled in all core plan B, C with plan effective date
          Scenario #3
          Add an employee with effective date 01/01/2018
          Actual result: Employee enrolled in all core plan A, B, C with plan effective date
          Scenario #4
          import 10 records with different Date of employment.
          cross verified on confirmation statement employee enrolled in core plan with plan effective date
          Scenario #5
          Verified through core plan allocation service
          cross verified on confirmation statement employee enrolled in core plan with plan effective date
          Scenario #6
          Verified through SA utility
          cross verified on confirmation statement employee enrolled in core plan with plan effective date
          Scenario #7
          Verified by adding termination date.
          cross verified on confirmation statement employee enrolled in core plan with plan effective date and termination date is also set.
          working fine as expected

          Show
          rashmita.dudhe Rashmita Dudhe (Inactive) added a comment - Verified on Stage Environment consider scenarios for core plan: 1] Core plan A with effective date 11/01/2017 2]Core plan B effective date 01/01/2018 3]Core plan C with effective date 07/15/2018 4]Core plan D with effective date 01/01/2017 Scenario #1 Add an employee with effective date 01/01/2017 Actual result: Employee enrolled in all core plan A, B, C, D with plan effective date Scenario #2 Add an employee with effective date 09/01/2017 Actual result: Employee enrolled in all core plan B, C with plan effective date Scenario #3 Add an employee with effective date 01/01/2018 Actual result: Employee enrolled in all core plan A, B, C with plan effective date Scenario #4 import 10 records with different Date of employment. cross verified on confirmation statement employee enrolled in core plan with plan effective date Scenario #5 Verified through core plan allocation service cross verified on confirmation statement employee enrolled in core plan with plan effective date Scenario #6 Verified through SA utility cross verified on confirmation statement employee enrolled in core plan with plan effective date Scenario #7 Verified by adding termination date. cross verified on confirmation statement employee enrolled in core plan with plan effective date and termination date is also set. working fine as expected
          Hide
          Permalink
          Monika.Demla Monika Demla (Inactive) added a comment -

          Great! Thanks for updated.

          Show
          Monika.Demla Monika Demla (Inactive) added a comment - Great! Thanks for updated.
          Hide
          Permalink
          rashmita.dudhe Rashmita Dudhe (Inactive) added a comment -

          Verified on Production Environment consider scenarios for core plan:
          1] Core plan A with effective date 11/01/2017
          2]Core plan B effective date 01/01/2018
          3]Core plan C with effective date 07/15/2018
          4]Core plan D with effective date 01/01/2017
          Scenario #1
          Add an employee with effective date 01/01/2017
          Actual result: Employee enrolled in all core plan A, B, C, D with plan effective date
          Scenario #2
          Add an employee with effective date 09/01/2017
          Actual result: Employee enrolled in all core plan B, C with plan effective date
          Scenario #3
          Add an employee with effective date 01/01/2018
          Actual result: Employee enrolled in all core plan A, B, C with plan effective date
          Scenario #4
          import 10 records with different Date of employment.
          cross verified on confirmation statement employee enrolled in core plan with plan effective date
          Scenario #5
          Verified through core plan allocation service
          cross verified on confirmation statement employee enrolled in core plan with plan effective date
          Scenario #6
          Verified through SA utility
          cross verified on confirmation statement employee enrolled in core plan with plan effective date
          Scenario #7
          Verified by adding termination date.
          cross verified on confirmation statement employee enrolled in core plan with plan effective date and termination date is also set.
          working fine as expected

          Show
          rashmita.dudhe Rashmita Dudhe (Inactive) added a comment - Verified on Production Environment consider scenarios for core plan: 1] Core plan A with effective date 11/01/2017 2]Core plan B effective date 01/01/2018 3]Core plan C with effective date 07/15/2018 4]Core plan D with effective date 01/01/2017 Scenario #1 Add an employee with effective date 01/01/2017 Actual result: Employee enrolled in all core plan A, B, C, D with plan effective date Scenario #2 Add an employee with effective date 09/01/2017 Actual result: Employee enrolled in all core plan B, C with plan effective date Scenario #3 Add an employee with effective date 01/01/2018 Actual result: Employee enrolled in all core plan A, B, C with plan effective date Scenario #4 import 10 records with different Date of employment. cross verified on confirmation statement employee enrolled in core plan with plan effective date Scenario #5 Verified through core plan allocation service cross verified on confirmation statement employee enrolled in core plan with plan effective date Scenario #6 Verified through SA utility cross verified on confirmation statement employee enrolled in core plan with plan effective date Scenario #7 Verified by adding termination date. cross verified on confirmation statement employee enrolled in core plan with plan effective date and termination date is also set. working fine as expected
          Hide
          Permalink
          rashmita.dudhe Rashmita Dudhe (Inactive) added a comment -

          Hi Monika Demla,

          This is deployed and verified on Production.
          Kindly, update Jira accordingly.

          Thanks,
          Rashmita

          Show
          rashmita.dudhe Rashmita Dudhe (Inactive) added a comment - Hi Monika Demla , This is deployed and verified on Production. Kindly, update Jira accordingly. Thanks, Rashmita

            People

            Assignee:
            Monika.Demla Monika Demla (Inactive)
            Reporter:
            Monika.Demla Monika Demla (Inactive)
            Developer:
            Snehal Shabade (Inactive)
            QA:
            Rashmita Dudhe (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Dev Due Date:
              Code Review Date:

                Time Tracking

                Estimated:
                Original Estimate - 0h
                0h
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 33h
                33h