En tant que Agent CM dans un pays nécessitant la gestion d'Unicode (type Asie)
Je veux pouvoir identifier mon client via une écriture unicode
Afin de confirmer qu'il s'agit bien de lui / le trouver sur l'interface CXO
+ gestion unicode
UNICODE fields format change, i.e make difference between HOUSEHOLD'S NON UNICODE countries from HOUSEHOLD'S Unicode Countries in terms of 17 fields length + 2 fields to be displayed/masked.
= 2 UNICODE fields First Name(Prénom) and Last Name(NOMCLI) exist already on Household and Filiation objects. Display them on the forms
Option 1: Display UNICODE countries in fonction of HOUSEHOLD's Country:
Implement a Business Rule with the display of Unicode fields if the country is Unicode country and not Unicode fields if the country is not Unicode (rule applied once Household's Country is entered): 0,5 days
Implement a JS code which will change the lenghth of 17 fields in the fonction of Household's country (if Unicode or Not): 2
Address Normalization NEEDED: Implement an interface to call API ClubMed in order to have an autocompletion functionality in 6-8 Adress fields: 3 days
Update Household API CRM (semi-interface): 1,5 days
- Détails technique :Impact développement chez :
anneliseg
commented
7 years ago 
User Story :
En tant que Agent CM dans un pays nécessitant la gestion d'Unicode (type Asie) Je veux pouvoir identifier mon client via une écriture unicode Afin de confirmer qu'il s'agit bien de lui / le trouver sur l'interface CXO
+ gestion unicode
UNICODE fields format change, i.e make difference between HOUSEHOLD'S NON UNICODE countries from HOUSEHOLD'S Unicode Countries in terms of 17 fields length + 2 fields to be displayed/masked.
= 2 UNICODE fields First Name(Prénom) and Last Name(NOMCLI) exist already on Household and Filiation objects. Display them on the forms
Option 1: Display UNICODE countries in fonction of HOUSEHOLD's Country:
- Critères d'acceptance :