Hide Forgot
The system forms defined for the different field types include the translations adhoc. This forms labels and help text had to use zanata system for translation.
This prevents the field properties to be translated in Zanata. The solution will also allow to translate user defined forms by adding an optional resource bundle to the form definition.
Enabled zanata translations for platform forms. Commits (master): https://github.com/droolsjbpm/jbpm-form-modeler/commit/0bb94ddd3202952cb3d275332f7b3408f02fc72c Commits (6.0.x): https://github.com/droolsjbpm/jbpm-form-modeler/commit/e75529377eaad8469aaa7defe5a3e316b6d04809 Waiting to zanata team to translate the new resources.
Fixed (In reply to Pere Fernàndez from comment #3) Enabled zanata translations for platform forms. Commits (master): https://github.com/droolsjbpm/jbpm-form-modeler/commit/0bb94ddd3202952cb3d275332f7b3408f02fc72c https://github.com/droolsjbpm/jbpm-form-modeler/commit/03f88bb2f7bff458236d3f5d817b5ada86d6a536 Commits (6.0.x): https://github.com/droolsjbpm/jbpm-form-modeler/commit/e75529377eaad8469aaa7defe5a3e316b6d04809 https://github.com/droolsjbpm/jbpm-form-modeler/commit/7170086719133ddc10752cf60acab00127263413 Waiting to zanata team to translate the new resources.
Waiting to zanata team to translate the new resources.
Ok, verified the presence of fix in BPMS 6.0.0 ER7 and also checked, that switching locale in business central enables the respective language in the form modeler form field properties.