Investigate technical limitations and opportunities for translations in Native Objects

• Type: Spike
• Status: Closed
• Priority: Major
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: None
• Component/s: App Builder
• Labels: None
• Spike Type: Technical
• Conclusion:
  Hide

  1 - Adjust method getName from DataEngineNativeObject class. Return a Map<Locale, String>. ; ; 2 - Adjust parameter _customName (along with methods getCustomName) of DataEngineNativeObjectField to return a Map<Locale, String> ; ; 3 - Create a map inside DataEngineNativeObjectField to store non-changeable properties. ; ; 4 - Create a constructer with the following fields (non-changeable properties.): ; ; repeatable ; displayStyle ; indexable ; indexType ; validation ; multiple ; alphabeticalOrder

  Show

  1 - Adjust method getName from DataEngineNativeObject class. Return a Map<Locale, String>. 2 - Adjust parameter _customName (along with methods getCustomName) of DataEngineNativeObjectField to return a Map<Locale, String> 3 - Create a map inside DataEngineNativeObjectField to store non-changeable properties. 4 - Create a constructer with the following fields (non-changeable properties.): repeatable displayStyle indexable indexType validation multiple alphabeticalOrder
• Epic Link: App Builder - Extend Native Objects
• Sprint: App_Builder_7.4_05

This Spike aims to investigate what are the technical limitations and opportunities that we can leverage to set translations for Native Fields of Native Objects.

A huge part of the information (field) of Liferay Native Assets (Users, Blogs, etc.) comes with a translation to several (or even all) the languages supported in the instance configurations.

With that being said, when creating Custom Views for that Native Object in App Builder, customers doesn't expect to have to translate those native fields, since he didn't have this effort when they started using Liferay.

To achieve the best experience, we must find a way to leverage those translations for the Native Fields of Native Objects, in a way that the user will only need to set translations for Custom Fields.

The expected outcome of this Spike is:

1. Identify if it is possible or not to leverage the existing translations of the Native Fields of Native Objects when using App Builder
   1. If it is possible, investigate how and how much effort it will be
   2. If not, investigate what needs to change to make this happen and how impactful it will be.
2. Keep an eye to identify opportunities and alternative ways to achieve the goal and solve the problem described above.