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

OED | Invalid OE effective date

    Details

    • Environment:
      Production
    • Bug Type:
      Functional
    • Bug Severity:
      Medium
    • Module:
      BenAdmin - Export
    • Reported by:
      Client
    • Item State:
      Production QA - Production Deployed
    • Sprint:
      WT Sprint 38 - Bugs

      Description

      Hi Punam Satpute,

      OE effective date of OED is not in valid format.

      Please find attached screen shot for the reference.

      Please let me know if anything else needed.

      Thanks,
      Pallavi Kulkarni

      CC-Amit Thorve,Vinayak Kulkarni,Ganesh Sadawarte

        Attachments

          Issue Links

            Activity

            Hide
            punam.satpute Punam Satpute (Inactive) added a comment -

            Cause : WT-11261 OED | Invalid OE effective date.
            Concern : Null is not checked for OE Effective date.
            Correction: Handled null value
            Affected Areas : Home--->Open Enrollment Dashboard.

            Show
            punam.satpute Punam Satpute (Inactive) added a comment - Cause : WT-11261 OED | Invalid OE effective date. Concern : Null is not checked for OE Effective date. Correction: Handled null value Affected Areas : Home--->Open Enrollment Dashboard.
            Hide
            abhay.patil Abhay Patil (Inactive) added a comment - - edited

            Punam Satpute - for some companies the OE Effective date is populated correctly and for some it is not. Point is, for Berryessa Union School District, Yuba City and UND, the OE effective date is set up as follows. But, on the OE dashboard, Yuba City and Berryessa Union School District have bad OE effective date while that of UND is right. Why is this happening? In other words - why is it NULL for Berryessa and Yuba City, and a valid date for UND? (Curious - after the fix, when you handle null, what date will be shown for Berryessa Union School District on the OE dashboard?)

            CC Vinayak Kulkarni Amit Thorve

            Show
            abhay.patil Abhay Patil (Inactive) added a comment - - edited Punam Satpute - for some companies the OE Effective date is populated correctly and for some it is not. Point is, for Berryessa Union School District, Yuba City and UND, the OE effective date is set up as follows. But, on the OE dashboard, Yuba City and Berryessa Union School District have bad OE effective date while that of UND is right. Why is this happening? In other words - why is it NULL for Berryessa and Yuba City, and a valid date for UND? (Curious - after the fix, when you handle null, what date will be shown for Berryessa Union School District on the OE dashboard?) CC Vinayak Kulkarni Amit Thorve
            Hide
            Vinayak.Kulkarni Vinayak Kulkarni (Inactive) added a comment -

            Hi Abhay,

            If we notice OE start and OE end date in these companies then only UND has OE dates added and for Yuba City and Berryessa Union School District they are blank.

            To calculate OE effective date, we get year from OE start date which is properly configured on UND which is why it is showing proper in dashboard and for Yuba city and Berryessa Union School District as date is blank ,wrong OE effective date is calculated and stored into dashboard.

            After this fix, if OE start and OE end date is blank then we will show blank OE effective date by handling null values. Thanks.

            Show
            Vinayak.Kulkarni Vinayak Kulkarni (Inactive) added a comment - Hi Abhay, If we notice OE start and OE end date in these companies then only UND has OE dates added and for Yuba City and Berryessa Union School District they are blank. To calculate OE effective date, we get year from OE start date which is properly configured on UND which is why it is showing proper in dashboard and for Yuba city and Berryessa Union School District as date is blank ,wrong OE effective date is calculated and stored into dashboard. After this fix, if OE start and OE end date is blank then we will show blank OE effective date by handling null values. Thanks.
            Hide
            abhay.patil Abhay Patil (Inactive) added a comment - - edited

            Thanks for explanation Vinayak Kulkarni. This raises another question.

            The OE effective date is specified as month/day/NEXT YEAR in the UI. Here NEXT YEAR is next financial year per the company setting. Simply, put, it should always be the NEXT (forthcoming) month and day in the future. It should not consult the OE start date. Thus for all calendar financial year companies that are going into open enrollment now, it should be 01/01/2018. Can we do this? Are there any side effects that could hurt if this is implemented? CC Amit Thorve Van Nguyen

            Show
            abhay.patil Abhay Patil (Inactive) added a comment - - edited Thanks for explanation Vinayak Kulkarni . This raises another question. The OE effective date is specified as month/day/NEXT YEAR in the UI. Here NEXT YEAR is next financial year per the company setting. Simply, put, it should always be the NEXT (forthcoming) month and day in the future. It should not consult the OE start date. Thus for all calendar financial year companies that are going into open enrollment now, it should be 01/01/2018. Can we do this? Are there any side effects that could hurt if this is implemented? CC Amit Thorve Van Nguyen
            Hide
            swapnil.eksambekar Swapnil Eksambekar (Inactive) added a comment -

            Verified this issue on Stage,It is working as expected,ready for production deployment.

            CC-Aniruddha DevRakesh RoyHrishikesh Deshpande

            Show
            swapnil.eksambekar Swapnil Eksambekar (Inactive) added a comment - Verified this issue on Stage,It is working as expected,ready for production deployment. CC- Aniruddha Dev Rakesh Roy Hrishikesh Deshpande
            Hide
            Ganesh.sadawarte Ganesh Sadawarte (Inactive) added a comment -

            HI Abhay Patil,

            Thus for all calendar financial year companies that are going into open enrollment now, it should be 01/01/2018. Can we do this? Are there any side effects that could hurt if this is implemented?
            We will analysis above changes and update you on this.

            CC-Vinayak Kulkarni

            Thanks,
            Ganesh

            Show
            Ganesh.sadawarte Ganesh Sadawarte (Inactive) added a comment - HI Abhay Patil , Thus for all calendar financial year companies that are going into open enrollment now, it should be 01/01/2018. Can we do this? Are there any side effects that could hurt if this is implemented? We will analysis above changes and update you on this. CC- Vinayak Kulkarni Thanks, Ganesh
            Hide
            aniruddha.dev Aniruddha Dev (Inactive) added a comment -

            Hi Abhay Patil,

            We have deployed and verified this fix today on Production . Can you please check this at your end and close this JIRA ?

            Please let us know in case of any queries/issues .

            Thanks & Regards,
            Aniruddha Dev

            Show
            aniruddha.dev Aniruddha Dev (Inactive) added a comment - Hi Abhay Patil , We have deployed and verified this fix today on Production . Can you please check this at your end and close this JIRA ? Please let us know in case of any queries/issues . Thanks & Regards, Aniruddha Dev
            Hide
            abhay.patil Abhay Patil (Inactive) added a comment -

            Damion M Velasquez - can you please confirm that the malformed OE effective date (Showing year as 0001) has been fixed? Thanks. CC Chris Ellenberger Van Nguyen

            Show
            abhay.patil Abhay Patil (Inactive) added a comment - Damion M Velasquez - can you please confirm that the malformed OE effective date (Showing year as 0001) has been fixed? Thanks. CC Chris Ellenberger Van Nguyen
            Hide
            abhay.patil Abhay Patil (Inactive) added a comment -

            Looks like it is working fine!

            Show
            abhay.patil Abhay Patil (Inactive) added a comment - Looks like it is working fine!

              People

              Assignee:
              Damion.Velasquez Damion M Velasquez
              Reporter:
              Pallavi.kulkarni Pallavi Kulkarni (Inactive)
              Account Executive:
              Amit Thorve (Inactive)
              Developer:
              Punam Satpute (Inactive)
              QA:
              Swapnil Eksambekar (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Dev Due Date:
                Pre-Prod Due Date:
                Production Due Date:
                Code Review Date:

                  Time Tracking

                  Estimated:
                  Original Estimate - 0h
                  0h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 6h 20m
                  6h 20m