Bug 1139215 - Inconsistent naming in Process Instance and Process Definition details.
Summary: Inconsistent naming in Process Instance and Process Definition details.
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ER3
: 6.1.0
Assignee: Marco Rietveld
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-08 12:12 UTC by Marek Baluch
Modified: 2020-03-27 19:42 UTC (History)
1 user (show)

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

Attachments (Terms of Use)
process def (315.62 KB, image/png)
2014-11-24 16:02 UTC, Mauricio Salatino 		no flags Details
process instances (253.79 KB, image/png)
2014-11-24 16:02 UTC, Mauricio Salatino 		no flags Details
View All

Description Marek Baluch 2014-09-08 12:12:55 UTC 
*** Description of problem:
Inconsistent naming in Process Instance and Process Definition details.

One mentions 'Views' the other 'Options' but these are essentially the same menus.

*** How to reproduce:
1) go "process management"
2) go "process definitions" | "process instances"
3) hit the magnification glass icon for details.

*** Actual result
Process Definition details panel says "Options" while Process Instance details panel says "Views".
Comment 2 Mauricio Salatino 2014-11-24 16:01:56 UTC 
Both has being unified in 6.2.x I'm attaching 2 screenshots showing that the two screens are defining an Options Menu in the details tab.
Comment 3 Mauricio Salatino 2014-11-24 16:02:20 UTC 
Created attachment 960836 [details]
process def
Comment 4 Mauricio Salatino 2014-11-24 16:02:41 UTC 
Created attachment 960848 [details]
process instances
Comment 5 Pavel Kralik 2015-01-07 16:03:34 UTC 
Verified BPMS 6.1.0.ER3
Comment 6 PnT Account Manager 2017-12-07 23:36:01 UTC 
Employee 'msalatin' has left the company.
Note You need to log in before you can comment on or make changes to this bug.