WORKTERRAProject Type: software

WORKTERRA

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

City of Bellevue - Server Error on EE Record

    Details

    • Type: Bug
    • Status: Production Complete
    • Priority: High
    • Resolution: Bug Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: BenAdmin
    • Environment:
      Production
    • Bug Severity:
      Medium
    • Module:
      BenAdmin - EDS
    • Reported by:
      Client
    • Company:
      City of Bellevue
    • Sprint:
      WT Sprint 40 - Bugs

      Description

      We are getting the attached server error on Kristina Galloway's record on the demographic record. Please advise as this group is currently in OE

        Attachments

          Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. WT-11829 City of Bellevue - Server Error

          • Critical - This problem will block progress.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. WT-11791 Qualifying Event : Validation for selecting Waiting Period if Effective Date Rule is selected as "Use Waiting Period"

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

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            umesh.kadam Umesh Kadam (Inactive) added a comment -

            Hi Debbie Kulling,

            Please find below 3Cs :

            Concern Getting server error on Demographics page of employee Kristina Galloway
            Cause
            • While showing Demographics page, system tries to get effective date using QE raised for an employee
            • For Krishinia Galloway, "Employee Change - Declaration of DP (Enter Date of DP Declaration)" QE has been raised with effective date "07/18/2017".
            • For this QE "Effective Date Rule" has been selected as "Use Waiting Period" but no any option selected under "Waiting Period"
            • Hence system is getting NULL value for effective date of this QE which is causing server error on demographics page
            • Please find attached screenshot
            Correction Please select correct option under "Waiting Period, it will work.
            On Stage, "First of Month Following Event Date" has been selected under "Waiting Period"

            We have created WT-11791 to add validation to select "Waiting Period" if "Effective Date Rule" has been selected as "Use Waiting Period".

            Thanks and Regards,
            :: Umesh Kadam

            CC : Satya, Amruta Lohiya, Rakesh Shahane, Swapnil Pandhare

            Show
            umesh.kadam Umesh Kadam (Inactive) added a comment - Hi Debbie Kulling , Please find below 3Cs : Concern Getting server error on Demographics page of employee Kristina Galloway Cause While showing Demographics page, system tries to get effective date using QE raised for an employee For Krishinia Galloway, "Employee Change - Declaration of DP (Enter Date of DP Declaration)" QE has been raised with effective date "07/18/2017". For this QE "Effective Date Rule" has been selected as "Use Waiting Period" but no any option selected under "Waiting Period" Hence system is getting NULL value for effective date of this QE which is causing server error on demographics page Please find attached screenshot Correction Please select correct option under "Waiting Period, it will work. On Stage, "First of Month Following Event Date" has been selected under "Waiting Period" We have created WT-11791 to add validation to select "Waiting Period" if "Effective Date Rule" has been selected as "Use Waiting Period". Thanks and Regards, :: Umesh Kadam CC : Satya , Amruta Lohiya , Rakesh Shahane , Swapnil Pandhare
            Hide
            Permalink
            satyap Satya added a comment -

            Swapnil Pandhare,

            As permanent fix to avoid this scenario, we will make ‘waiting period option’ mandatory whenever ‘Use Waiting period’ option has been selected for qualifying event effective date rule.

            Please refer mail Unable to embed resource: Re EE errors due to waiting period selections.msg of type application/octet-stream for details.

            Regards,
            Satya Prakash

            Cc: Rajiv Rajan Gaurav Sodani

            Show
            satyap Satya added a comment - Swapnil Pandhare , As permanent fix to avoid this scenario, we will make ‘waiting period option’ mandatory whenever ‘Use Waiting period’ option has been selected for qualifying event effective date rule. Please refer mail Unable to embed resource: Re EE errors due to waiting period selections.msg of type application/octet-stream for details. Regards, Satya Prakash Cc: Rajiv Rajan Gaurav Sodani
            Hide
            Permalink
            niteen.surwase Niteen Surwase (Inactive) added a comment - - edited

            Hi Debbie Kulling

            I have checked for above validation on Production (City of Bellevue For HSPL).
            So, When we select Effective Date Rule as Use Waiting Period, then Waiting Period Option field is mandatory. This is already implemented.

            I've scanned for NULL Waiting Period through all companies. Not found any QE with null Waiting Period.

            Please see below screen-shot for Waiting Period validation.

            Please check and close the ticket.

            Thanks,
            Niteen S.

            Cc: Swapnil Pandhare Satya Sheetal Bodhale

            Show
            niteen.surwase Niteen Surwase (Inactive) added a comment - - edited Hi Debbie Kulling I have checked for above validation on Production (City of Bellevue For HSPL). So, When we select Effective Date Rule as Use Waiting Period , then Waiting Period Option field is mandatory. This is already implemented. I've scanned for NULL Waiting Period through all companies. Not found any QE with null Waiting Period. Please see below screen-shot for Waiting Period validation. Please check and close the ticket. Thanks, Niteen S. Cc: Swapnil Pandhare Satya Sheetal Bodhale
            Hide
            Permalink
            sheetal.bodhale Sheetal Bodhale (Inactive) added a comment -

            Correction is done,so closing the ticket

            Show
            sheetal.bodhale Sheetal Bodhale (Inactive) added a comment - Correction is done,so closing the ticket
            Hide
            Permalink
            Jennifer.Reed Jennifer Reed (Inactive) added a comment -

            Satya Did we do a code fix on this? I was under the impression that were supposed to make the ‘waiting period option’ mandatory. Has this been done?

            Show
            Jennifer.Reed Jennifer Reed (Inactive) added a comment - Satya Did we do a code fix on this? I was under the impression that were supposed to make the ‘waiting period option’ mandatory. Has this been done?
            Hide
            Permalink
            swapnil.pandhare Swapnil Pandhare (Inactive) added a comment - - edited

            CC : Satya
            Hi Jennifer Reed

            We have not done any code fix for this. It's already a mandatory field. We are working on why this was not updated . We have updated waiting period option for this.
            Thanks,
            Swapnil P.

            Cc: Satya Swapnil Pandhare

            Show
            swapnil.pandhare Swapnil Pandhare (Inactive) added a comment - - edited CC : Satya Hi Jennifer Reed We have not done any code fix for this. It's already a mandatory field. We are working on why this was not updated . We have updated waiting period option for this. Thanks, Swapnil P. Cc: Satya Swapnil Pandhare
            Hide
            Permalink
            Jennifer.Reed Jennifer Reed (Inactive) added a comment -

            Swapnil Pandhare Satya Oh interesting...so it was already mandatory? So, do we have another ticket open to understand why this scenario happened? I don't see any, and I'm not comfortable with closing this ticket if we haven't discovered the root cause of how this happened.

            Thanks,
            Jenn

            Show
            Jennifer.Reed Jennifer Reed (Inactive) added a comment - Swapnil Pandhare Satya Oh interesting...so it was already mandatory? So, do we have another ticket open to understand why this scenario happened? I don't see any, and I'm not comfortable with closing this ticket if we haven't discovered the root cause of how this happened. Thanks, Jenn
            Hide
            Permalink
            swapnil.pandhare Swapnil Pandhare (Inactive) added a comment -

            CC : Satya Samir

            Hi Rakesh Roy ,

            Can you please assign this to QA to try to reproduce this issue on various browsers ?

            Thanks,
            Swapnil P.

            Show
            swapnil.pandhare Swapnil Pandhare (Inactive) added a comment - CC : Satya Samir Hi Rakesh Roy , Can you please assign this to QA to try to reproduce this issue on various browsers ? Thanks, Swapnil P.
            Hide
            Permalink
            venkatesh.pujari Venkatesh Pujari (Inactive) added a comment -

            Hi Sachin Hingole,

            Tried to reproduce this issue on IE11,Chrome and Firefox browsers. I tried adding a new QE,editing an existing one but could not reproduce this issue.

            Thanks,
            Venkatesh

            Show
            venkatesh.pujari Venkatesh Pujari (Inactive) added a comment - Hi Sachin Hingole , Tried to reproduce this issue on IE11,Chrome and Firefox browsers. I tried adding a new QE,editing an existing one but could not reproduce this issue. Thanks, Venkatesh
            Hide
            Permalink
            Jennifer.Reed Jennifer Reed (Inactive) added a comment -

            Adding comment for clarification:
            The waiting period option field is already mandatory, so we need to figure out how this scenario happened. Therefore, the ticket is still open. The data has already been corrected, so it should no longer be an issue for the client.

            Satya Swapnil Pandhare If we are still testing scenarios to figure out how this happened, should the ticket status be in Production Complete?

            Show
            Jennifer.Reed Jennifer Reed (Inactive) added a comment - Adding comment for clarification: The waiting period option field is already mandatory, so we need to figure out how this scenario happened. Therefore, the ticket is still open. The data has already been corrected, so it should no longer be an issue for the client. Satya Swapnil Pandhare If we are still testing scenarios to figure out how this happened, should the ticket status be in Production Complete?

              People

              Assignee:
              sachin.hingole Sachin Hingole (Inactive)
              Reporter:
              dkulling Debbie Kulling
              Account Executive:
              Debbie Kulling
              Developer:
              Umesh Kadam (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Dev Due Date:

                  Time Tracking

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