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

Health Tier Mapping - special character error

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Environment:
      Production
    • Bug Severity:
      Critical
    • Module:
      BenAdmin - Enrollment
    • Reported by:
      EDI
    • Company:
      Groendyke
    • Item State:
      Production Complete - Closed
    • Sprint:
      WT Sprint 41

      Description

      Hello Amit Thorve and Vinayak Kulkarni,

      Is there a way to bypass this error during open enrollment? It’s slowing down the process to terminate current or clone over the health tier mapping for new plans. I have 44 of them to do for Groendyke’s VSP file, but for companies with larger structures, this will slow down the process even more.

      CC - Rochelle Thomas, Damion M Velasquez, Chris Ellenberger, Alex Nguyen, Abhay Patil, Cindy Wibbing

        Attachments

          Issue Links

            Activity

            Hide
            rashmita.dudhe Rashmita Dudhe (Inactive) added a comment -

            Verified in Stage Environment consider below scenarios:

            1]Add Health tier policy mapping name with a Different combination of special characters like - &(),.
            2]Clone health tier policy no with policy mapping name with a Different combination of special characters like - &(),.
            3]Add new employee Enrolled in plan and cross verified through SA utility Health tier policy no allocated properly
            4]Verfied by increasing tier in same Year with the different Effective date.
            5]Verfied by Updating Health tier policy name and policy mapping
            6]Verfied by deleting non used Health tier policy mapping

            All above scenarios it is working fine as expected.

            Show
            rashmita.dudhe Rashmita Dudhe (Inactive) added a comment - Verified in Stage Environment consider below scenarios: 1]Add Health tier policy mapping name with a Different combination of special characters like - &(),. 2]Clone health tier policy no with policy mapping name with a Different combination of special characters like - &(),. 3]Add new employee Enrolled in plan and cross verified through SA utility Health tier policy no allocated properly 4]Verfied by increasing tier in same Year with the different Effective date. 5]Verfied by Updating Health tier policy name and policy mapping 6]Verfied by deleting non used Health tier policy mapping All above scenarios it is working fine as expected.
            Hide
            rashmita.dudhe Rashmita Dudhe (Inactive) added a comment -

            Verified in production Environment consider below scenarios:
            1]Add Health tier policy mapping name with a Different combination of special characters like - &(),.
            2]Clone health tier policy no with policy mapping name with a Different combination of special characters like - &(),.
            3]Add new employee Enrolled in plan and cross verified through SA utility Health tier policy no allocated properly
            4]Verfied by increasing tier in same Year with the different Effective date.
            5]Verfied by Updating Health tier policy name and policy mapping
            6]Verfied by deleting non used Health tier policy mapping
            All above scenarios it is working fine as expected.

            Show
            rashmita.dudhe Rashmita Dudhe (Inactive) added a comment - Verified in production Environment consider below scenarios: 1]Add Health tier policy mapping name with a Different combination of special characters like - &(),. 2]Clone health tier policy no with policy mapping name with a Different combination of special characters like - &(),. 3]Add new employee Enrolled in plan and cross verified through SA utility Health tier policy no allocated properly 4]Verfied by increasing tier in same Year with the different Effective date. 5]Verfied by Updating Health tier policy name and policy mapping 6]Verfied by deleting non used Health tier policy mapping All above scenarios it is working fine as expected.
            Hide
            rashmita.dudhe Rashmita Dudhe (Inactive) added a comment -

            Hi Van Nguyen,

            This is deployed and verified in the Production environment.
            Kindly check and update Jira accordingly.

            Thanks,
            Rashmita

            Show
            rashmita.dudhe Rashmita Dudhe (Inactive) added a comment - Hi Van Nguyen , This is deployed and verified in the Production environment. Kindly check and update Jira accordingly. Thanks, Rashmita
            Hide
            gaurav.sodani Gaurav Sodani (Inactive) added a comment -

            Hi All,

            Attaching the production deployment approval email for reference

            Regards
            Gaurav

            Show
            gaurav.sodani Gaurav Sodani (Inactive) added a comment - Hi All, Attaching the production deployment approval email for reference Regards Gaurav
            Hide
            Van.Nguyen Van Nguyen (Inactive) added a comment -

            Hi all,

            It works in production and ignores special characters - &(),.

            Thank you so much!!!

            Show
            Van.Nguyen Van Nguyen (Inactive) added a comment - Hi all, It works in production and ignores special characters - &(),. Thank you so much!!!

              People

              Assignee:
              Van.Nguyen Van Nguyen (Inactive)
              Reporter:
              Van.Nguyen Van Nguyen (Inactive)
              EDI Analyst 1:
              Van Nguyen (Inactive)
              Developer:
              Shailendra Honrao (Inactive)
              QA:
              Rashmita Dudhe (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Dev Due Date:
                Pre-Prod Due Date:
                Production Due Date:
                Code Review Date:

                  Time Tracking

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