Bug 972767

Summary:	Saving a process does not reload the Problems detected
Product:	[Retired] JBoss BPMS Platform 6	Reporter:	Zuzana Krejčová <zkrejcov>
Component:	jBPM Designer	Assignee:	Tihomir Surdilovic <tsurdilo>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Zuzana Krejčová <zkrejcov>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.0.0	CC:	kverlaen, lpetrovi
Target Milestone:	ER1
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:07:01 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 Zuzana Krejčová 2013-06-10 14:38:11 UTC

Description of problem:
When you create any type of asset, Problems tab is opened. This of course happens for new processes as well, in their case the Problems tab even shows that the start and end nodes are missing for the new process. If you fix that and save the process, the problems reported do not disappear (from the Problems tab). 
The problems detected are refreshed upon saving an asset through the menu bar, File - Save, which is unfortunately unavailable for processes.
This means that you cannot build and deploy a project/artefact with a new process until you save another asset (e.g. pom.xml, task form, ...).


Version-Release number of selected component (if applicable):
BPMS 6, DR5


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Tihomir Surdilovic 2013-06-19 17:03:09 UTC

The Problems tab should not be shown by UF in case of bpmn2 assets. Designer currently still has its own visual validation mechanism. I would suggest not making this a Designer BZ since it does not control this tab. Would be nice if in UF we can control its showing up or not.

Comment 5 Lukáš Petrovický 2014-02-07 16:15:56 UTC

This BZ has been part of the 6.0.0 stream.