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

In Chubb Life Time Benefits Plan, when "All Living Children" is selected as beneficiary its respective mapping needs to be done with Workterra beneficiary field.

    Details

    • Type: Change Request
    • Status: Closed
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Module:
      BenAdmin - SSO
    • Reported by:
      Harbinger
    • Item State:
      Production Complete - Closed
    • Severity:
      Simple

      Description

      In Chubb Life Time Benefits Plan, when "All Living Children" is selected as beneficiary its respective mapping needs to be done with Workterra beneficiary field.

      Currently, "All Living Children" beneficiary is not getting mapped in workterra with beneficiary.
      Please refer attached screenshots for more details.

      CC: Jaideep VinchurkarSamirAditya VishwakarmaRakesh RoySaurabh SablakaHrishikesh DeshpandeKunal Kedari

        Attachments

        1. 09_25_2017_00_26_19_802_2666_13586.txt
          88 kB
          Santosh Balid
        2. Beneficiary.jpg
          34 kB
          Santosh Balid
        3. LTB-19Sept.jpg
          305 kB
          Prasad Pise
        4. RE Need feedback for All Living Children and Estate beneficiary Processing -Done.msg
          362 kB
          Santosh Balid

          Issue Links

            Activity

            Hide
            santosh.balid Santosh Balid (Inactive) added a comment -

            Hi Prasad Pise,

            We need to discuss this with CHUBB/Selerix team , after that only we can take decision on what to do in this case.

            If you have any suggestions , then please mention those in this jira.

            Regards,
            Santosh

            Cc: Samir, Satya, Jaideep Vinchurkar, Kunal Kedari,Aditya Vishwakarma

            Show
            santosh.balid Santosh Balid (Inactive) added a comment - Hi Prasad Pise , We need to discuss this with CHUBB/Selerix team , after that only we can take decision on what to do in this case. If you have any suggestions , then please mention those in this jira. Regards, Santosh Cc: Samir , Satya , Jaideep Vinchurkar , Kunal Kedari , Aditya Vishwakarma
            Hide
            santosh.balid Santosh Balid (Inactive) added a comment -

            Hello Prasad Pise,

            Mentioning my observation below:

            Currently Our System is processing the "All Living Children" beneficiary in "Trust" criteria same like "Estate". But as we are filtering the existence of beneficiary in our system based upon below criteria.
            1)EmployeeID
            2)FirstName
            3)LastName
            4)SSN
            4)PlanDesignID
            5)EffectiveDate

            So , Once we added "Estate" in our system , for every new Trust type, we get record with above criteria and we update the same "Trust/Estate" record with new "Trust" name.
            i.e Currently we are keeping only one "Trust" record against single employee with same plan.
            Please see below screen for reference.

            The above issue will get resolved by adding "OrganizationName" as an additional criteria to allow multiple "Trust" entries in our system against single employee with same plan.

            But, still , we need to handle "All Living Children" beneficiary with different logic, by communicating with Selerix/CHUBB team.

            Regards,
            Santosh

            Cc: Kunal Kedari, Aditya Vishwakarma,Jaideep Vinchurkar, Samir

            Show
            santosh.balid Santosh Balid (Inactive) added a comment - Hello Prasad Pise , Mentioning my observation below: Currently Our System is processing the "All Living Children" beneficiary in "Trust" criteria same like "Estate". But as we are filtering the existence of beneficiary in our system based upon below criteria. 1)EmployeeID 2)FirstName 3)LastName 4)SSN 4)PlanDesignID 5)EffectiveDate So , Once we added "Estate" in our system , for every new Trust type, we get record with above criteria and we update the same "Trust/Estate" record with new "Trust" name. i.e Currently we are keeping only one "Trust" record against single employee with same plan. Please see below screen for reference. The above issue will get resolved by adding "OrganizationName" as an additional criteria to allow multiple "Trust" entries in our system against single employee with same plan. But, still , we need to handle "All Living Children" beneficiary with different logic, by communicating with Selerix/CHUBB team. Regards, Santosh Cc: Kunal Kedari , Aditya Vishwakarma , Jaideep Vinchurkar , Samir
            Hide
            santosh.balid Santosh Balid (Inactive) added a comment -

            Please start QA once patch deployed on Stage and Prod.

            Show
            santosh.balid Santosh Balid (Inactive) added a comment - Please start QA once patch deployed on Stage and Prod.
            Hide
            kunal.kedari Kunal Kedari (Inactive) added a comment -

            We have verified this change on Production, now the different beneficiary assigned to plan while enrolling at Chubb side is displaying as below in WorkTerra:

            SpouseFirstName SpouseLastName [Other]
            ChildFirstName ChildLastName [Other]
            Trust [Other]
            All Living Children [Other]

            Closing this change request.

            Show
            kunal.kedari Kunal Kedari (Inactive) added a comment - We have verified this change on Production, now the different beneficiary assigned to plan while enrolling at Chubb side is displaying as below in WorkTerra: SpouseFirstName SpouseLastName [Other] ChildFirstName ChildLastName [Other] Trust [Other] All Living Children [Other] Closing this change request.

              People

              Assignee:
              kunal.kedari Kunal Kedari (Inactive)
              Reporter:
              prasadp Prasad Pise (Inactive)
              Developer:
              Santosh Balid (Inactive)
              QA:
              Kunal Kedari (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 16h
                  16h
                  Remaining:
                  Time Spent - 10h Remaining Estimate - 0.5h
                  0.5h
                  Logged:
                  Time Spent - 10h Remaining Estimate - 0.5h Time Not Required
                  10h