Bug 1332979 - i18n process name garbled in Simulation tab
Summary: i18n process name garbled in Simulation tab
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Designer
Version: 6.3.0
Hardware: All
OS: All
unspecified
medium
Target Milestone: ---
: ---
Assignee: Tihomir Surdilovic
QA Contact: Kirill Gaevskii
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-04 13:10 UTC by Kirill Gaevskii
Modified: 2020-03-27 19:10 UTC (History)
0 users

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


Attachments (Terms of Use)
Business process with i18n name (7.98 KB, application/xml)
2016-05-04 13:10 UTC, Kirill Gaevskii
no flags Details
Screenshot (170.80 KB, image/png)
2016-05-04 13:10 UTC, Kirill Gaevskii
no flags Details
Another place with garbled process name (129.96 KB, image/png)
2016-05-04 13:30 UTC, Kirill Gaevskii
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1332992 0 unspecified CLOSED i18n: In simulation summary Start and End date and summary Interval values are not localized 2021-02-22 00:41:40 UTC

Internal Links: 1332992

Description Kirill Gaevskii 2016-05-04 13:10:15 UTC
Created attachment 1153835 [details]
Business process with i18n name

Description of problem:
If you have i18n process name it will be garbled in Simulation tab. See attachment.

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

How reproducible:
always

Steps to Reproduce:
1. Open attached Business Process
2. Start Process Simulation

Actual results:
Process name is garbled. See attached screenshot.

Expected results:
Name will be displayed i18n without any problem.

Comment 1 Kirill Gaevskii 2016-05-04 13:10:52 UTC
Created attachment 1153836 [details]
Screenshot

Comment 3 Kirill Gaevskii 2016-05-04 13:30:58 UTC
Created attachment 1153844 [details]
Another place with garbled process name


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