Enterprise Architecture Practice 2 - Handle bilingual in Casewise diagram

After presented the migration Excel format BFM (English version) into Casewise repository with Casewise diagrams, one more requirement came out from the customer, which required to combine their existing separated Excel format BFM (English version) and BFM (French version) into one Casewise model with bilingual (English and French) feature model diagrams.

They really didn’t want to maintain two separated language versions of BFM in Casewise with lots of time costing between two language version sync.
Casewise does have an out of box feature - Multi-Language Manager, which helps create different language versions of the models.

For instance, if you do have English version Casewise model, and want to have a translated French verison Casewise model. By using Casewise Multi-Language Manager, end up getting 2 models – one English version model and one French version model

Obviously, Casewise Multi-Language Manager wouldn’t fit the customer’s requirement one Casewise model diagram with bilingual (English and French) feature.
After a little bit digging and practicing Casewise Out-Of-Box features (region and properties), I figured out that the best practice approach as below, which fits the customer’s one Casewise model diagram with bilingual (English and French) feature.

1. Based on the migrated English version BFM
2. Add more property types for User Defined (BFM Business Services, BFM L1 Element, BFM L2 Element, BFM Competency), such as, Name(Fr), Description(Fr), and etc
3. Casewise AutoModeler imports Excel format BFM (French version) into Casewise repository
4. In Pallatte Properties use regions for BFM Business Services, BFM L1 Element, BFM L2 Element, BFM Competency
5. End user could esaily switch between the different region displays in Pallatte Properties for different language in the diagram. By default, it was configured to French language.