WORKTERRAProject Type: software

WORKTERRA

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

Process Beneficiary added on Selerix Portal to Workterra

    Details

    • Type: Enhancement
    • Status: Production Complete
    • Priority: High
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Module:
      BenAdmin
    • Reported by:
      Client
    • Item State:
      Production Complete
    • Severity:
      Simple

      Description

      As per our initial requirement we had decided to process only enrollment data from Selerix to Workterra.
      But, later on, at last moment , CHUBB told us to process Beneficiary data as well in Workterra.
      So , as per this new requirement, if any beneficiary get added on Selerix portal, we have to add/update same beneficiary into Workterra as well, and we should also add that beneficiary under dependent(Spouse/Child) tables if it is not present already.

      Cc: Debbie Kulling, Jaideep Vinchurkar, Satya, Samir

        Attachments

          Issue Links

          relates to

          Enhancement - An improvement or enhancement to an existing feature or task. WT-9614 Nexion-Selerix Enrollment Service Integration for CHUBB through SSO

          • Medium - Has the potential to affect progress.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. WT-11080 SSO>Chubb Selerix>Functional>Beneficiary data from Selerix is not reflecting in Workterra

          • High - Serious problem that could block progress.
          • Rejected

          Bug - A problem which impairs or prevents the functions of the product. WT-11084 {Selerix-SSO} Employee beneficiaries added in Selerix SSO are not displayed on Employee Beneficiary page of Workterra.

          • High - Serious problem that could block progress.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. WT-11150 SSO>Chubb Selerix>Functional>Server error displaying for Beneficiary and Confirmation Statement

          • Critical - This problem will block progress.
          • Resolution Setting

          Bug - A problem which impairs or prevents the functions of the product. WT-11155 SSO>Chubb Selerix>Functional>"Estate" is no longer remains as beneficiary for first plan after adding it as beneficiary for second

          • High - Serious problem that could block progress.
          • Rejected

          Bug - A problem which impairs or prevents the functions of the product. WT-11156 SSO>Chubb Selerix>Functional>Spouse's relationship is not displaying in Beneficiary report.

          • High - Serious problem that could block progress.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. WT-11178 View enrollment summary is not displaying the Beneficiary details as it displays on Confirmation Statement.

          • Medium - Has the potential to affect progress.
          • Closed

          Change Request - Change Request 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.

          • Medium - Has the potential to affect progress.
          • Closed

            Activity

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

            Hello Prasad Pise and Kunal Kedari,

            Log you time for Beneficiary testing of Nexion Client to this jira.
            Also relate all the beneficiary related tickets to this jira.

            This requirement was out of scope for us, so I have created separate jira to track it.

            Regards,
            Santosh

            Show
            santosh.balid Santosh Balid (Inactive) added a comment - Hello Prasad Pise and Kunal Kedari , Log you time for Beneficiary testing of Nexion Client to this jira. Also relate all the beneficiary related tickets to this jira. This requirement was out of scope for us, so I have created separate jira to track it. Regards, Santosh

              People

              Assignee:
              santosh.balid Santosh Balid (Inactive)
              Reporter:
              santosh.balid Santosh Balid (Inactive)
              Account Executive:
              Debbie Kulling
              Developer:
              Santosh Balid (Inactive)
              QA:
              Prasad Pise (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Production Due Date:

                  Time Tracking

                  Estimated:
                  Original Estimate - 40h
                  40h
                  Remaining:
                  Time Spent - 22h Remaining Estimate - 18h
                  18h
                  Logged:
                  Time Spent - 22h Remaining Estimate - 18h
                  22h