Bug 1012478

Summary: zanata translation had to be applied to form modeler System Field types forms
Product: [Retired] JBoss BPMS Platform 6 Reporter: Neus Miras <nmirasch>
Component: Form ModelerAssignee: Pere Fernàndez <pere.fernandez>
Status: CLOSED CURRENTRELEASE QA Contact: Jan Hrcek <jhrcek>
Severity: medium Docs Contact:
Priority: high    
Version: 6.0.0CC: pzapataf
Target Milestone: ER5   
Target Release: 6.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-06 20:09:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Neus Miras 2013-09-26 14:20:18 UTC
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.

Comment 2 Pedro Zapata 2013-09-30 15:09:10 UTC
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.

Comment 3 Pere Fernàndez 2013-10-02 17:01:42 UTC
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.

Comment 5 Pere Fernàndez 2013-10-07 10:32:53 UTC
Waiting to zanata team to translate the new resources.

Comment 6 Jan Hrcek 2014-01-07 13:26:06 UTC
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.