Uploaded image for project: 'Project Simple'
  1. Project Simple
  2. ST-363

Pages(Form Builder), Forms Library, Site branding and Configuration tabs are not shown in Confirmation Popup while saving existing rule.

    Details

    • Environment:
      Stage, QA
    • Bug Type:
      Functional
    • Bug Severity:
      Medium
    • Module:
      BenAdmin - Enrollment
    • Reported by:
      Harbinger
    • Company:
      All Clients/Multiple Clients
    • Item State:
      Stage QA - Production Deployment on Hold

      Attachments

      1. st_363_configure site.png
        st_363_configure site.png
        85 kB
      2. st_363_forms library.png
        st_363_forms library.png
        71 kB
      3. ST-363.png
        ST-363.png
        60 kB

        Issue Links

          Activity

          Hide
          vinanti.yadav Vinanti Yadav (Inactive) added a comment - - edited

          Hi Prasad Pise,

          Please Refer Below 3C's:

          Concern : Pages(Form Builder), Forms Library, Site branding and Configuration tabs are not shown in Confirmation Popup while saving existing rule.

          Cause: Code implementation is not done.

          Correction: code fix is done.

          Impacted area :
          1. Form Builder, site branding and Config. pages, Forms Library pages tabs need to be display page name if that particular rule is used by that module.
          e.g :
          Rule 31 is used by Form Builder, Forms Library,Site branding and Config then all three tabs must contain a page name that refer Generic Eligibility Rule.

          2. Also check rule used by all three module gets display in Eligibility rule page (Main Page)

          This issue is found while doing unit testing of WT-11377

          Please start testing ASAP this need to be gets deploy on Prod by 14 Oct.

          CC : Amruta Lohiya, Jyoti Mayne, Satya, Priya Dhamande, Hrishikesh Deshpande

          Show
          vinanti.yadav Vinanti Yadav (Inactive) added a comment - - edited Hi Prasad Pise , Please Refer Below 3C's: Concern : Pages(Form Builder), Forms Library, Site branding and Configuration tabs are not shown in Confirmation Popup while saving existing rule. Cause : Code implementation is not done. Correction : code fix is done. Impacted area : 1. Form Builder, site branding and Config. pages, Forms Library pages tabs need to be display page name if that particular rule is used by that module. e.g : Rule 31 is used by Form Builder, Forms Library,Site branding and Config then all three tabs must contain a page name that refer Generic Eligibility Rule. 2. Also check rule used by all three module gets display in Eligibility rule page (Main Page) This issue is found while doing unit testing of WT-11377 Please start testing ASAP this need to be gets deploy on Prod by 14 Oct. CC : Amruta Lohiya , Jyoti Mayne , Satya , Priya Dhamande , Hrishikesh Deshpande
          Hide
          prasadp Prasad Pise (Inactive) added a comment -

          CC: Hrishikesh DeshpandeRakesh RoySachin Hingole

          FYI, Deployment date for this on production is mentioned as 12 OCt 2017.

          Show
          prasadp Prasad Pise (Inactive) added a comment - CC: Hrishikesh Deshpande Rakesh Roy Sachin Hingole FYI, Deployment date for this on production is mentioned as 12 OCt 2017.
          Hide
          vinanti.yadav Vinanti Yadav (Inactive) added a comment -

          Hi Rashmita Dudhe,

          As all generic Eligibility related changes are move on Prod on 14 Oct so we need to move this jira on prod on 14 Oct.

          Thanks,
          Vinanti

          CC : Jyoti Mayne, Amruta Lohiya, Satya, Prasad Pise, Hrishikesh Deshpande

          Show
          vinanti.yadav Vinanti Yadav (Inactive) added a comment - Hi Rashmita Dudhe , As all generic Eligibility related changes are move on Prod on 14 Oct so we need to move this jira on prod on 14 Oct. Thanks, Vinanti CC : Jyoti Mayne , Amruta Lohiya , Satya , Prasad Pise , Hrishikesh Deshpande
          Hide
          rashmita.dudhe Rashmita Dudhe (Inactive) added a comment -

          Verified on LB environment consider below scenarios:
          1]For builder add and update Eligibility rule
          2]Site branding and Configuration add and update Eligibility rule
          3]Forms Library add and update Eligibility rule
          4]Cross verified on Confirmation pop up by edit same rule for For builder, Form library, Site branding and Configuration
          5]Cross Verified for employee login.

          Working fine as expected.

          Show
          rashmita.dudhe Rashmita Dudhe (Inactive) added a comment - Verified on LB environment consider below scenarios: 1]For builder add and update Eligibility rule 2]Site branding and Configuration add and update Eligibility rule 3]Forms Library add and update Eligibility rule 4]Cross verified on Confirmation pop up by edit same rule for For builder, Form library, Site branding and Configuration 5]Cross Verified for employee login. Working fine as expected.
          Hide
          rashmita.dudhe Rashmita Dudhe (Inactive) added a comment -

          Verified on Stage environment consider below scenarios:
          1]For builder add and update Eligibility rule
          2]Site branding and Configuration add and update Eligibility rule
          3]Forms Library add and update Eligibility rule
          4]Cross verified on Confirmation pop up by edit same rule for For builder, Form library, Site branding and Configuration
          5]Cross Verified for employee login.
          Working fine as expected.

          Show
          rashmita.dudhe Rashmita Dudhe (Inactive) added a comment - Verified on Stage environment consider below scenarios: 1]For builder add and update Eligibility rule 2]Site branding and Configuration add and update Eligibility rule 3]Forms Library add and update Eligibility rule 4]Cross verified on Confirmation pop up by edit same rule for For builder, Form library, Site branding and Configuration 5]Cross Verified for employee login. Working fine as expected.
          Hide
          vinanti.yadav Vinanti Yadav (Inactive) added a comment -

          Hi Rashmita Dudhe,

          This Fix is deployed on Azure.

          Thanks & Regards,
          Vinanti

          Show
          vinanti.yadav Vinanti Yadav (Inactive) added a comment - Hi Rashmita Dudhe , This Fix is deployed on Azure. Thanks & Regards, Vinanti
          Hide
          sanjana.jadhav Sanjana Jadhav (Inactive) added a comment - - edited

          Verified on production environment consider below scenarios:
          1]For builder add and update Eligibility rule
          2]Site branding and Configuration add and update Eligibility rule
          3]Forms Library add and update Eligibility rule
          4]Cross verified on Confirmation pop up by edit same rule for For builder, Form library, Site branding and Configuration
          5]Cross Verified for employee login.
          Working fine as expected.
          PFA

          Thanks,
          Sanjana Jadhav

          CC: Prasad Pise Sachin Hingole Rakesh Roy

          Show
          sanjana.jadhav Sanjana Jadhav (Inactive) added a comment - - edited Verified on production environment consider below scenarios: 1]For builder add and update Eligibility rule 2]Site branding and Configuration add and update Eligibility rule 3]Forms Library add and update Eligibility rule 4]Cross verified on Confirmation pop up by edit same rule for For builder, Form library, Site branding and Configuration 5]Cross Verified for employee login. Working fine as expected. PFA Thanks, Sanjana Jadhav CC: Prasad Pise Sachin Hingole Rakesh Roy

            People

            Assignee:
            rashmita.dudhe Rashmita Dudhe (Inactive)
            Reporter:
            vinanti.yadav Vinanti Yadav (Inactive)
            Developer:
            Vinanti Yadav (Inactive)
            QA:
            Rashmita Dudhe (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Dev Due Date:
              Production Due Date:
              Code Review Date:

                Time Tracking

                Estimated:
                Original Estimate - 8h Original Estimate - 8h
                8h
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 21h
                21h