Bug 959186

Summary:	End Node - simulation parameters contain properties which are not used by target Distribution Type
Product:	[Retired] JBoss BPMS Platform 6	Reporter:	Sona Mala <smala>
Component:	jBPM Designer	Assignee:	Tihomir Surdilovic <tsurdilo>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Marek Baluch <mbaluch>
Severity:	low	Docs Contact:
Priority:	medium
Version:	6.0.0	CC:	kverlaen, mbaluch, rrajasek
Target Milestone:	ER6
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:12: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 Sona Mala 2013-05-03 10:07:07 UTC

Description of problem:
Simulation section in the property bar contains properties for all distribution types at the same moment. 

Version-Release number of selected component (if applicable):
6.0.0 DR3

How reproducible:
Show property bar for end node.

Steps to Reproduce:
1. put end node on canvas
2. show property bar for this task

  
Actual results:
There is processing time (min, max, mean) and standard deviation at the same time.


Expected results:
Same behaviour like for others types of task (human, manual, etc.)
 - normal - processing time (mean) and standard deviation
 - uniform, random - processing time (min, max)
 - poisson - processing time (mean)

Additional info:
related with 959182

Comment 1 Kris Verlaenen 2013-05-31 23:07:25 UTC

Tiho, does it make sense for end nodes to even have simulation properties?  Isn't an event node always instantaneous?

Comment 2 Tihomir Surdilovic 2013-11-21 00:38:52 UTC

I cannot reproduce the issue. In order for the selected property to be stored as the property value you must click outside of it or press enter (this is the same for pretty much every property in designer. Once that is done, the other properties switch accordingly and follow the expected results section. 

Kris, I think it is ok to have simulation properties on end events as well. Users are then able to add certain processing time for network latency, hardware, etc etc (I know it goes into details that are mostly not used but I think it is ok).

Comment 3 Marek Baluch 2013-12-21 15:45:48 UTC

Verified on ER6.