WORKTERRAProject Type: software

WORKTERRA

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

CCSF - Payroll - Critical Illness change

    Details

    • Type: Bug
    • Status: Closed
    • Priority: High
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: BenAdmin
    • Labels:
      None
    • Environment:
      Production
    • Bug Severity:
      Medium
    • Module:
      BenAdmin - Export
    • Reported by:
      EDI
    • Company:
      CCSF
    • Item State:
      Production Complete
    • Issue Importance:
      Must Have
    • Sprint:
      WT- Sprint 43

      Description

      Hi Vinayak Kulkarni,

      I don't know if I need to update my company level templates, but for some reason, the child critical illness change should have appeared on the payroll file. The Critical Illness plans have 1 combined deduction code and amount.

      Can you check to see how I can get this change to appear on the payroll file?

      Employee: Rafael Catapang

      Company template name: Payroll_Critical Illness
      Filename: EBS_BA0517_VOL_BEN_DED_CCSF_20180111.TXT1029_50040737336

      Company template name: Audit Payroll_Critical Illness
      Filename: CCSF_Audit_Payroll_201801111204__41266762839.xls

      Company template name: Payroll_Supp Life EE SP CH
      Company template name: Audit Payroll_Supp life EE SP CH

        Attachments

        1. AffectedFiles.txt
          1 kB
        2. Enrollment Change Type For Multiple Benefit(s).doc
          145 kB
        3. template_structure.PNG
          template_structure.PNG
          40 kB
        4. template.PNG
          template.PNG
          43 kB
        5. TemplateListWithSameCustomization.xls
          11 kB
        6. TestCases_WT-13082.xls
          16 kB
        7. WT-13087_WBS.xls
          22 kB

          Issue Links

          is cloned by

          Bug - A problem which impairs or prevents the functions of the product. NF-5892 UI Refresh - CCSF - Payroll - Critical Illness change

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

            Activity

            Ascending order - Click to sort in descending order
            15 older comments
            Hide
            Permalink
            swapnil.eksambekar Swapnil Eksambekar (Inactive) added a comment - - edited

            Verified following scenarios on Columnswise(Changes Only File) template :-

            1.Selected Benefits enrollments are Terminated
            2.Benefits enrollments are Added by raising qualifying event
            3.Benefits enrollments are Added by New Hire mode
            4.Only one enrollment is terminated after last exported Date
            5.Enrollments are terminated by Terminate as never effective(Dead Enrollment)
            6.Spouse or Child benefits enrollments are added after last exported date.

            Observation - For Full file All records will be termed as CHANGE

            Testing is in process for other scenarios .

            CC-Hrishikesh DeshpandeVinayak KulkarniRakesh Roy

            Show
            swapnil.eksambekar Swapnil Eksambekar (Inactive) added a comment - - edited Verified following scenarios on Columnswise(Changes Only File) template :- 1.Selected Benefits enrollments are Terminated 2.Benefits enrollments are Added by raising qualifying event 3.Benefits enrollments are Added by New Hire mode 4.Only one enrollment is terminated after last exported Date 5.Enrollments are terminated by Terminate as never effective(Dead Enrollment) 6.Spouse or Child benefits enrollments are added after last exported date. Observation - For Full file All records will be termed as CHANGE Testing is in process for other scenarios . CC- Hrishikesh Deshpande Vinayak Kulkarni Rakesh Roy
            Hide
            Permalink
            swapnil.eksambekar Swapnil Eksambekar (Inactive) added a comment -

            Verified all scenarios mentioned in TestCases_WT-13082.xls , It is working as expected.
            Ready for stage deployment.

            CC-Hrishikesh DeshpandeRakesh RoyVinayak Kulkarni

            Show
            swapnil.eksambekar Swapnil Eksambekar (Inactive) added a comment - Verified all scenarios mentioned in TestCases_WT-13082.xls , It is working as expected. Ready for stage deployment. CC- Hrishikesh Deshpande Rakesh Roy Vinayak Kulkarni
            Hide
            Permalink
            swapnil.eksambekar Swapnil Eksambekar (Inactive) added a comment - - edited

            Verified all following scenarios on Stage
            1.Selected Benefits enrollments are Terminated - Pass
            2.Benefits enrollments are Added by raising qualifying event - Pass
            3.Benefits enrollments are Added by New Hire mode - Pass
            4.Only one enrollment is terminated after last exported Date - Pass
            5.Enrollments are terminated by Terminate as never effective(Dead Enrollment) - Pass
            6.Spouse or Child benefits enrollments are added after last exported date. - Pass
            7.Employee,Spouse,Child termination. - Pass
            8.Spouse and child terminated by terminate dependent benefits - Pass
            9.New Benefits Enrollment added in OE - Pass

            It is working as expected.Ready for production deployment.

            CC-Hrishikesh DeshpandeRakesh RoyVinayak Kulkarni

            Show
            swapnil.eksambekar Swapnil Eksambekar (Inactive) added a comment - - edited Verified all following scenarios on Stage 1.Selected Benefits enrollments are Terminated - Pass 2.Benefits enrollments are Added by raising qualifying event - Pass 3.Benefits enrollments are Added by New Hire mode - Pass 4.Only one enrollment is terminated after last exported Date - Pass 5.Enrollments are terminated by Terminate as never effective(Dead Enrollment) - Pass 6.Spouse or Child benefits enrollments are added after last exported date. - Pass 7.Employee,Spouse,Child termination. - Pass 8.Spouse and child terminated by terminate dependent benefits - Pass 9.New Benefits Enrollment added in OE - Pass It is working as expected.Ready for production deployment. CC- Hrishikesh Deshpande Rakesh Roy Vinayak Kulkarni
            Hide
            Permalink
            swapnil.eksambekar Swapnil Eksambekar (Inactive) added a comment -

            Hi Van Nguyen,

            This is deployed and verified on production with all scenarios.
            It is wokring as expected,please verify at your end and confirm it.
            and let me know,if there is any query.

            Thanks,
            Swapnil Eksambekar

            CC-Hrishikesh DeshpandeRakesh Roy

            Show
            swapnil.eksambekar Swapnil Eksambekar (Inactive) added a comment - Hi Van Nguyen , This is deployed and verified on production with all scenarios. It is wokring as expected,please verify at your end and confirm it. and let me know,if there is any query. Thanks, Swapnil Eksambekar CC- Hrishikesh Deshpande Rakesh Roy
            Hide
            Permalink
            Vinayak.Kulkarni Vinayak Kulkarni (Inactive) added a comment -

            Hi Van,

            We have introduced new mapping field "Enrollment transaction type for multiple Benefit" to get correction transaction type on column-wise file in case we are sending multiple WT benefits into one row in file.

            Please go through analysis doc Enrollment Change Type For Multiple Benefit(s).doc
            You can map this new field on file and test it, if it goes fine then we have to replace existing mapping with new mapping on production for attached template list. TemplateListWithSameCustomization.xls

            Let us know if you have any questions on this. Thanks.

            Show
            Vinayak.Kulkarni Vinayak Kulkarni (Inactive) added a comment - Hi Van, We have introduced new mapping field "Enrollment transaction type for multiple Benefit" to get correction transaction type on column-wise file in case we are sending multiple WT benefits into one row in file. Please go through analysis doc Enrollment Change Type For Multiple Benefit(s).doc You can map this new field on file and test it, if it goes fine then we have to replace existing mapping with new mapping on production for attached template list. TemplateListWithSameCustomization.xls Let us know if you have any questions on this. Thanks.

              People

              Assignee:
              Van.Nguyen Van Nguyen (Inactive)
              Reporter:
              Van.Nguyen Van Nguyen (Inactive)
              EDI Analyst 1:
              Van Nguyen (Inactive)
              Developer:
              Rakesh Shahane (Inactive)
              QA:
              Swapnil Eksambekar (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

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

                  Time Tracking

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