WORKTERRAProject Type: software

WORKTERRA

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

Server error in Prod - Utah Valley

    Details

    • Type: Support Activity
    • Status: Resolved
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Support Task Type:
      Query Resolution
    • Environment:
      Production
    • Reported by:
      White Label
    • Module:
      BenAdmin

      Description

      It is for Utah Valley in Prod for UHC. 
      Error is coming up with pulling EE David Prestriedge conf statement.  Checked a few other EEs and it seems isolated
      to him.

       

        Attachments

          Issue Links

          relates to

          Enhancement - An improvement or enhancement to an existing feature or task. WT-6478 Dependent SSN - consider Special character

          • High - Serious problem that could block progress.
          • Production Complete

            Activity

            Ascending order - Click to sort in descending order
            18 older comments
            Hide
            Permalink
            sheetal.bodhale Sheetal Bodhale (Inactive) added a comment - - edited

            Hi Rakesh Roy,

            Please re verify this issue through import.
            As per Rashmita's comment,it is allowing "^" character and said it is non repoducible.

            Also check for any other special character.
            CC:Hrishikesh DeshpandeSwapnil PandhareSatya
            Thanks,
            Sheetal Bodhale

            Show
            sheetal.bodhale Sheetal Bodhale (Inactive) added a comment - - edited Hi Rakesh Roy , Please re verify this issue through import. As per Rashmita's comment,it is allowing "^" character and said it is non repoducible. Also check for any other special character. CC: Hrishikesh Deshpande Swapnil Pandhare Satya Thanks, Sheetal Bodhale
            Hide
            Permalink
            sheetal.bodhale Sheetal Bodhale (Inactive) added a comment -

            Hi Jennifer Leugers,

            Please find attached corrected employee list. UtahValleyCorrectedEmployeeList.xls
            CC:SatyaSwapnil PandhareVijayendra ShindeRakesh Roy

            Thanks,
            Sheetal Bodhale

            Show
            sheetal.bodhale Sheetal Bodhale (Inactive) added a comment - Hi Jennifer Leugers , Please find attached corrected employee list. UtahValleyCorrectedEmployeeList.xls CC: Satya Swapnil Pandhare Vijayendra Shinde Rakesh Roy Thanks, Sheetal Bodhale
            Hide
            Permalink
            hrishikesh.deshpande Hrishikesh Deshpande (Inactive) added a comment -

            Hi Jennifer Leugers,

            We have done data correction of attached employees. Now there is no any error on confirmation statement.
            We are testing as possible as scenarios to reproduce this issue. We will get back to you with our testing status.

            Meantime you can check that Server error on confirmation is fixed.

            Let me know in case you need any information on this or also please share your input if any.

            Thanks,
            Hrishikesh.

            Show
            hrishikesh.deshpande Hrishikesh Deshpande (Inactive) added a comment - Hi Jennifer Leugers , We have done data correction of attached employees. Now there is no any error on confirmation statement. We are testing as possible as scenarios to reproduce this issue. We will get back to you with our testing status. Meantime you can check that Server error on confirmation is fixed. Let me know in case you need any information on this or also please share your input if any. Thanks, Hrishikesh.
            Hide
            Permalink
            hrishikesh.deshpande Hrishikesh Deshpande (Inactive) added a comment -

            Hi Satya,

            We have tried below scenarios to repro this issue but is is not reproducing and working as expected on our end.

            1. Tested through UI - Removed Beneficiary SSN and tried to add ^ - It throws validation and can not add ^ in SSN.
            2. Tested through Import.
            3. Tested various scenarios by removing and adding SSN in various mode, Partner or Employee can not enter ^ in SSN,
            4. Blank SSN can update but its not replace with ^
            5. EE or Partner can not add ssn with XX - like masking.

            Can you let me know if any additional scenarios needs to be add.

            Thanks,
            Hrishikesh.

            Show
            hrishikesh.deshpande Hrishikesh Deshpande (Inactive) added a comment - Hi Satya , We have tried below scenarios to repro this issue but is is not reproducing and working as expected on our end. Tested through UI - Removed Beneficiary SSN and tried to add ^ - It throws validation and can not add ^ in SSN. Tested through Import. Tested various scenarios by removing and adding SSN in various mode, Partner or Employee can not enter ^ in SSN, Blank SSN can update but its not replace with ^ EE or Partner can not add ssn with XX - like masking. Can you let me know if any additional scenarios needs to be add. Thanks, Hrishikesh.
            Hide
            Permalink
            satyap Satya added a comment -

            Hi Jennifer,

            Development has shared list of 17 employees for which correction was done. UtahValleyCorrectedEmployeeList.xls

            Also find mentioned details for scenarios tried out with QA team.

            Regards,
            Satya Prkash

            Show
            satyap Satya added a comment - Hi Jennifer, Development has shared list of 17 employees for which correction was done. UtahValleyCorrectedEmployeeList.xls Also find mentioned details for scenarios tried out with QA team. Regards, Satya Prkash

              People

              Assignee:
              jennifer.leugers Jennifer Leugers
              Reporter:
              jennifer.leugers Jennifer Leugers
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: