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

City of Bellevue- System Calculating Wrong Rate

    Details

    • Type: Support Activity
    • Status: Resolved
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Support Task Type:
      Data Correction
    • Environment:
      Production
    • Reported by:
      Client
    • Company:
      City of Bellevue
    • Module:
      BenAdmin - Enrollment

      Description

      The system is calculating the smoker rate for spouse at $3.66. Should be $1.86 for $20,000 for age 36 spouse smoker.

      Employee Name: A. Kinney

        Attachments

          Activity

          Hide
          sheetal.bodhale Sheetal Bodhale (Inactive) added a comment -

          Hi Debbie Kulling,

          We are working on it.We will update you on this till Monday EOD.

          CC:Satya

          Thanks,
          Sheetal Bodhale

          Show
          sheetal.bodhale Sheetal Bodhale (Inactive) added a comment - Hi Debbie Kulling , We are working on it.We will update you on this till Monday EOD. CC: Satya Thanks, Sheetal Bodhale
          Hide
          sheetal.bodhale Sheetal Bodhale (Inactive) added a comment -

          Hi @suraj,

          We have verified data from back end for mentioned employee.Data for 'Does your spouse or your domestic partner use tobacco product' field is inserted through general mode irrespective of page id on which field is present.

          That is causing issue while calculating rates .Can you please look into this today as client is having call today?

          CC:SatyaJaideep VinchurkarUmesh KadamJyoti Mayne
          Thanks,
          Sheetal Bodhale

          Show
          sheetal.bodhale Sheetal Bodhale (Inactive) added a comment - Hi @suraj, We have verified data from back end for mentioned employee.Data for 'Does your spouse or your domestic partner use tobacco product' field is inserted through general mode irrespective of page id on which field is present. That is causing issue while calculating rates .Can you please look into this today as client is having call today? CC: Satya Jaideep Vinchurkar Umesh Kadam Jyoti Mayne Thanks, Sheetal Bodhale
          Hide
          sheetal.bodhale Sheetal Bodhale (Inactive) added a comment -

          Hi Debbie Kulling,

          We have corrected the affected employees data.

          Suraj Sokasane:Please share the root cause for the same.

          CC:Satya

          Thanks,
          Sheetal Bodhale

          Show
          sheetal.bodhale Sheetal Bodhale (Inactive) added a comment - Hi Debbie Kulling , We have corrected the affected employees data. Suraj Sokasane :Please share the root cause for the same. CC: Satya Thanks, Sheetal Bodhale
          Hide
          suraj.sokasane Suraj Sokasane (Inactive) added a comment -

          Hi Debbie Kulling,

          As per our primary analysis, the issue occurred during the correction under WT-5153.
          We are investigating more on this and let you know the final root cause tomorrow EOD.

          Show
          suraj.sokasane Suraj Sokasane (Inactive) added a comment - Hi Debbie Kulling , As per our primary analysis, the issue occurred during the correction under WT-5153 . We are investigating more on this and let you know the final root cause tomorrow EOD.
          Hide
          suraj.sokasane Suraj Sokasane (Inactive) added a comment -

          Hi Debbie Kulling

          As per comment above, this occurred due to correction under WT-5153.

          Show
          suraj.sokasane Suraj Sokasane (Inactive) added a comment - Hi Debbie Kulling As per comment above, this occurred due to correction under WT-5153 .

            People

            Assignee:
            dkulling Debbie Kulling
            Reporter:
            michelle.parker Michelle Parker (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Dates

              Due:
              Created:
              Updated:
              Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 3h Original Estimate - 3h
                3h
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 15h 43m
                15h 43m