Hi Amit Thorve,

Concern: Special charter hyphen - is not allowed for Mapping Name

Cause: Earlier for Mapping name there was no validation. Currently only alphanumeric letters (a-z, A-Z, 0-9) with white space are allowed for Mapping Name. Code for same is implemented under JIRA WT-6901.
Mentioned Mapping Name contains hyphen. Hence system is showing validation while saving and cloning mapping.

Correction: If you remove hyphen from Mapping Name and proceed with saving and cloning it will work.
Otherwise we need to fix code to allow hyphen for Mapping Name after development approval.

Could you please confirm along with hyphen what extra special characters should be allowed for Mapping Name?

Gaurav Sodani We would required development approval for this change.

Cc: Amruta Lohiya

Jyoti Mayne First of all this is not a CHANGE REQUEST. If something is supported earlier and now we do not support it and when we removed the support we didn't care for checking if that character is used somewhere.

I really don't understand the logic behind this. How we can say that this is a change request? The hyphen was used in health tier policy mapping and now system is not allowing it. If you are saying that you can again implement this with a change request, approval of the change request etc. then why in first place it was blocked?

CC-Jennifer Reed, Nick, Jackie Sivigny, Abhay Patil

Hi Amit Thorve,

We are not referring this as a change request, however this needs a code change and will require this ticket be converted to a Bug and needs to go through formal approval process across each state. We will need to take this up for development approval to start of with

We are converting this ticket to Bug

Please let us know in case of any concern

Regards
Gaurav

Jennifer ReedNickJackie SivignyAbhay PatilSatyaNagini IndugulaJyoti Mayne

Hi All,

Attaching the development approval email for your reference

Regards
Gaurav

Hi Hrishikesh Deshpande,

We have scanned policy mapping name data on production and found that additional special charters like ( )& . , are used in mapping name. So we have allowed these special characters along with hyphen in validation for Mapping Name.

Thanks
Shailendra Honrao

Cc:Amruta Lohiya, Jyoti Mayne

Verified on Lb 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

in all above scenarios, it is working fine on LB. but this is not working on Codemap.

LB Testing Status - Pass
Codemap testing status - Fail

Hi All,

This ticket has been approved for stage deployment on 12/21/17.

Regards
Gaurav

This Issue is deployed on Stage. We will test it and update on Tuesday, 12/26.

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.

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.

Hi Van Nguyen,

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

Thanks,
Rashmita

Hi All,

Attaching the production deployment approval email for reference

Regards
Gaurav

Hi all,

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

Thank you so much!!!