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

Town of Cary- Rate issue (PROD)

    Details

    • Type: Bug
    • Status: Production Complete
    • Priority: High
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Environment:
      Production
    • Bug Severity:
      Medium
    • Module:
      BenAdmin - EDS
    • Reported by:
      Support
    • Company:
      Town of Cary
    • Item State:
      Production Complete - Closed
    • Sprint:
      WT Sprint 38 - Bugs, WT Sprint 40 - Bugs

      Description

      Per the CS :
      Hello,
      The EE cost isn't showing up on the Confirmation Statement for the "Retiree Health Plan." There should be a premium cost of $718.14. I checked the rates on the Y drive and it reflects the same EE cost. The cost is showing in WT in the "2017 Retiree Health 0" rate. I waived and saved the plan and it didn't update. Please advise...
      Thanks!
      CT:
      We have pulled a report to show an example. See below.

      For Bobby Hunter, His rates are not coming down on the conformation statement.

      The pull down on the Demographic page does not have a (select button)

      For Dawn Cronin, She also has the zero selected but her conformation shows an amount.

      Can you please let us know what is going on were some of the EE's are getting rates and some are not?

      Thank you,
      Yashau
      Please ref: CT-2699

        Attachments

          Issue Links

            Activity

            Hide
            priya.dhamande Priya Dhamande (Inactive) added a comment -

            Environment: Stage
            Company: Town of Cary for Hspl
            Login: partner

            Unable to get the correct Employee cost for below scenario.

            • Add Employee > Default Retiree Subsidy value is always set to 0 > Enroll Retiree health Plan > Cost = 0
            • Demographic page > change Retiree Subsidy > 55(or any value in drop down) > Save
            • Enroll Now Page > Cost is displayed as expected.

            Means for the default value zero cost is not changing, later after demographics change it is displayed as expected.

            So, re-opening the jira on Stage.

            As mentioned, this scenario was not tested on LB, because in newer component 0 value couldn't be saved.

            Hrishikesh Deshpande

            Show
            priya.dhamande Priya Dhamande (Inactive) added a comment - Environment: Stage Company: Town of Cary for Hspl Login: partner Unable to get the correct Employee cost for below scenario. Add Employee > Default Retiree Subsidy value is always set to 0 > Enroll Retiree health Plan > Cost = 0 Demographic page > change Retiree Subsidy > 55(or any value in drop down) > Save Enroll Now Page > Cost is displayed as expected. Means for the default value zero cost is not changing, later after demographics change it is displayed as expected. So, re-opening the jira on Stage. As mentioned, this scenario was not tested on LB, because in newer component 0 value couldn't be saved. Hrishikesh Deshpande
            Hide
            jyotibala Jyotibala Pardeshi (Inactive) added a comment -

            Hi Priya Dhamande,

            Please find below comments,

            • Add Employee > Default Retiree Subsidy value is always set to 0 > Enroll Retiree health Plan > Cost = 0 (System behavior)
            • If we set default value as 0 in form builder > page field configuration, then > Add Employee > Default Retiree Subsidy value is always set to 0 > Enroll Retiree health Plan > Cost = Rate value

            If you set a default value as 0 then employee will get rates, but if you didn't set any default value, then it won't calculate the rate, this is System Behavior (as default constraint is not set)

            Kindly check with default value condition once and update JIRA accordingly.

            Thanks and Regards,
            Jyotibala P.

            CC: Satya, Swapnil Pandhare, Sheetal Bodhale

            Show
            jyotibala Jyotibala Pardeshi (Inactive) added a comment - Hi Priya Dhamande , Please find below comments, Add Employee > Default Retiree Subsidy value is always set to 0 > Enroll Retiree health Plan > Cost = 0 (System behavior) If we set default value as 0 in form builder > page field configuration, then > Add Employee > Default Retiree Subsidy value is always set to 0 > Enroll Retiree health Plan > Cost = Rate value If you set a default value as 0 then employee will get rates, but if you didn't set any default value, then it won't calculate the rate, this is System Behavior (as default constraint is not set) Kindly check with default value condition once and update JIRA accordingly. Thanks and Regards, Jyotibala P. CC: Satya , Swapnil Pandhare , Sheetal Bodhale
            Hide
            jyotibala Jyotibala Pardeshi (Inactive) added a comment -

            By mistaken changed status

            Show
            jyotibala Jyotibala Pardeshi (Inactive) added a comment - By mistaken changed status
            Hide
            priya.dhamande Priya Dhamande (Inactive) added a comment -

            Environment: Stage
            Company: Town of Cary for Hspl
            Login: Partner

            Now, 0 value is not saving as null in DB and hence cost is displayed as expected.

            But as mentioned in above comment, the issue of default value as 0 didn't display correct cost still exists. This issue is also existing on other companies and client has reported the same.

            As null issue is resolved so moving jira on production and separate jira is created for the issue with ID: WT-11872.

            Jyotibala Pardeshi Hrishikesh Deshpande Rashmita Dudhe Rakesh Roy

            Show
            priya.dhamande Priya Dhamande (Inactive) added a comment - Environment: Stage Company: Town of Cary for Hspl Login: Partner Now, 0 value is not saving as null in DB and hence cost is displayed as expected. But as mentioned in above comment, the issue of default value as 0 didn't display correct cost still exists. This issue is also existing on other companies and client has reported the same. As null issue is resolved so moving jira on production and separate jira is created for the issue with ID: WT-11872 . Jyotibala Pardeshi Hrishikesh Deshpande Rashmita Dudhe Rakesh Roy
            Hide
            rakeshr Rakesh Roy (Inactive) added a comment -

            Yashau MacShate This is deployed on production, please verify and confirm.

            Show
            rakeshr Rakesh Roy (Inactive) added a comment - Yashau MacShate This is deployed on production, please verify and confirm.

              People

              Assignee:
              Yashau.Macshate Yashau MacShate (Inactive)
              Reporter:
              Yashau.Macshate Yashau MacShate (Inactive)
              Developer:
              Jyotibala Pardeshi (Inactive)
              QA:
              Priya Dhamande (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

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

                  Time Tracking

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