Uploaded image for project: 'New Features 2017'
  1. New Features 2017
  2. NF-4992

QE workflow not started for employee

    Details

    • Type: Bug
    • Status: Closed
    • Priority: High
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: UI Refresh
    • Labels:
      None
    • Environment:
      Others
    • Bug Type:
      Functional
    • Bug Severity:
      Critical
    • Level:
      Employee
    • Module:
      BenAdmin - Enrollment
    • Reported by:
      Harbinger
    • Company:
      CHMC
    • Item State:
      Production Complete - Closed

      Description

      Prerequisite -
      1.OE is going on
      2.Employee completed OE workflow
      3.Employee is in session
      4.Raise QE for EE

      Details - 300000676
      For QA-MATT-Azure
      User ID: mstricker/Test@123456

      Step:-
      1.Log in with EE
      2.EE stared OE work flow
      3.Complete OE workflow
      4.Navigate to Initiate Qualifying event
      5.Raise Marriage QE (11/09/2017)

      Actual - EE did not get QE workflow

      Expected - QE flow should started

        Attachments

          Issue Links

            Activity

            Hide
            mahendra.mungase Mahendra Mungase (Inactive) added a comment -

            We faced same issue on For QA-City of Bellevue-Azure

            User ID: taormina0101/Test_123456 or Test@123456

            Show
            mahendra.mungase Mahendra Mungase (Inactive) added a comment - We faced same issue on For QA-City of Bellevue-Azure User ID: taormina0101/Test_123456 or Test@123456
            Hide
            harshawardhan Harshawardhan Phalake (Inactive) added a comment -

            Hi Mahendra Mungase,
            As discussed we not able to reproduce the issue.
            This might be fixed in between build.

            Thanks,
            Harshawardhan.
            CC: Rohan J Khandave

            Show
            harshawardhan Harshawardhan Phalake (Inactive) added a comment - Hi Mahendra Mungase , As discussed we not able to reproduce the issue. This might be fixed in between build. Thanks, Harshawardhan. CC: Rohan J Khandave
            Hide
            mahendra.mungase Mahendra Mungase (Inactive) added a comment -

            Hi Harshawardhan Phalake

            We are not getting QE for Marriage event for below employee
            300000689
            For QA KinderCare
            User ID: tach01011985/Test_123456

            Hence reopening the same

            Thanks,
            mahendra

            Show
            mahendra.mungase Mahendra Mungase (Inactive) added a comment - Hi Harshawardhan Phalake We are not getting QE for Marriage event for below employee 300000689 For QA KinderCare User ID: tach01011985/Test_123456 Hence reopening the same Thanks, mahendra
            Hide
            rohan.khandave Rohan J Khandave (Inactive) added a comment -

            Hello Mahendra Mungase

            We found app server time is not sync with web server. Now we sync both machines timings.

            Please check.

            Thanks,
            RohanK

            CC – Sachin Hingole,Harshawardhan Phalake , [~meghana joshi], Nidhi Kaul

            Show
            rohan.khandave Rohan J Khandave (Inactive) added a comment - Hello Mahendra Mungase We found app server time is not sync with web server. Now we sync both machines timings. Please check. Thanks, RohanK CC – Sachin Hingole , Harshawardhan Phalake , [~meghana joshi] , Nidhi Kaul
            Hide
            nidhi.kaul Nidhi Kaul (Inactive) added a comment -

            Mahendra Mungase
            Wasn't this fixed long back?

            Nidhi.

            Show
            nidhi.kaul Nidhi Kaul (Inactive) added a comment - Mahendra Mungase Wasn't this fixed long back? Nidhi.
            Hide
            mahendra.mungase Mahendra Mungase (Inactive) added a comment -

            It was Server Time setting issue. It is fixed.

            Mahendra

            Show
            mahendra.mungase Mahendra Mungase (Inactive) added a comment - It was Server Time setting issue. It is fixed. Mahendra

              People

              Assignee:
              mahendra.mungase Mahendra Mungase (Inactive)
              Reporter:
              mahendra.mungase Mahendra Mungase (Inactive)
              Developer:
              Rohan J Khandave (Inactive)
              QA:
              Mahendra Mungase (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 2h
                  2h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 2h
                  2h