Bug 1038992 - 'Unable to complete your request' when switching process model to Metadata
Summary: 'Unable to complete your request' when switching process model to Metadata
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Designer
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ER6
: 6.0.0
Assignee: Tihomir Surdilovic
QA Contact: Zuzana Krejčová
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-06 10:14 UTC by Zuzana Krejčová
Modified: 2016-08-01 01:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:12:52 UTC
Type: Bug


Attachments (Terms of Use)
after switching to Metadata - error pop-up (83.75 KB, image/png)
2013-12-06 10:14 UTC, Zuzana Krejčová
no flags Details

Description Zuzana Krejčová 2013-12-06 10:14:00 UTC
Created attachment 833516 [details]
after switching to Metadata - error pop-up

Description of problem:
The 'read-only' Designer in Process Management perspectives has two tabs at the bottom. The first one, labelled Business Process, displays the process model / instance state. The other one is labelled Metadata; when switching to this tab, user gets an error pop-up saying "Unable to complete your request. The following exception occurred: null." No error is logged to the server log. After dismissing this error pop-up, the content of the Metadata tab/panel is blank. Nothing else seems broken by this.


Version-Release number of selected component (if applicable):
BPMS 6.0 ER5


How reproducible:
Every time, with process model for both the process definition and process instance (in Process Management perspectives).

Comment 1 Tihomir Surdilovic 2013-12-09 16:26:23 UTC
fixed in designer master and 6.0 branches. in the read-only mode the metadata tab does no longer appear.

Comment 2 Zuzana Krejčová 2013-12-20 16:21:21 UTC
Verified in ER6 - Metadata panel is no more.


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