Bug 1328907 - [pt_BR] Deploy->Rule Deployments page content not generated properly and graphical content not rendered properly
Summary: [pt_BR] Deploy->Rule Deployments page content not generated properly and grap...
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.3.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Marco Rietveld
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-20 14:27 UTC by Krishna Babu K
Modified: 2020-03-27 19:36 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 19:36:34 UTC
Type: Bug


Attachments (Terms of Use)
Screen shot reference for pt_BR locale (68.08 KB, image/png)
2016-04-20 14:27 UTC, Krishna Babu K
no flags Details
Screen shot reference for en_US locale (84.74 KB, image/png)
2016-04-20 14:28 UTC, Krishna Babu K
no flags Details

Description Krishna Babu K 2016-04-20 14:27:16 UTC
Created attachment 1149108 [details]
Screen shot reference for pt_BR locale

Description of problem:
When logged in business-central with pt_BR locale, the Deploy->Rule Deployments content is not generated properly compared with en_US locale. For example 'SERVER TEMPLATES' appearing as '!!!ServerNavigationView.TitleText!!!'. Graphical content like label, buttons, tabs not displaying.

Version-Release number of selected component (if applicable):
6.3.0 GA

How reproducible:
Always

Steps to Reproduce:
1.Log in to business-central with pt_BR locale
2.Navigate to Deploy->Rule Deployments
3.Content on this page not displaying properly

Actual results:
Content not displaying properly

Expected results:
Should display properly

Additional info:
Screen shots of en_US and pt_BR attached for comparison and better understanding.

Comment 1 Krishna Babu K 2016-04-20 14:28:05 UTC
Created attachment 1149109 [details]
Screen shot reference for en_US locale


Note You need to log in before you can comment on or make changes to this bug.