Bug 1081185

Summary:	KPI in edit mode shows outdated data
Product:	[Retired] JBoss BPMS Platform 6	Reporter:	Pedro Zapata <pzapataf>
Component:	BAM	Assignee:	David Gutierrez <dgutierr>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jan Hrcek <jhrcek>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.0.1	CC:	kverlaen
Target Milestone:	ER1
Target Release:	6.0.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-08-06 19:50:08 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 Pedro Zapata 2014-03-26 17:28:32 UTC

1. Create a provider to an empty DB.
2. Create KPI to that DB.
3. Fill DB while the application is running.
4. Edit KPI again. You'll see the KPI still shows a message indicating there's no data. 

Note that if previous data existed in the DB this would be hardly noticeable, since usually data is not relevant for KPI composition. In view mode everything works as expected.

The underlying reason is the edit KPI is using the global dataset manager instead of the per-session one.

The fix is to initialize properly the thread local settings in the edit kpi jsps.

Comment 2 David Gutierrez 2014-04-09 15:33:46 UTC

Fixed.

Github commit (master): https://github.com/droolsjbpm/dashboard-builder/commit/4b6931407cfce6c1d7113dfdea6466f05d48d174

Github commit (6.0.x): https://github.com/droolsjbpm/dashboard-builder/commit/a89a9038fbe48d00cfb1050617beb165d1533472

Comment 3 Jan Hrcek 2014-05-02 10:32:18 UTC

Ok, verified with BPMS 6.0.2.ER2