Bug 1104237

Summary:	When the KPI is exported, the associated data source should too
Product:	[Retired] JBoss BPMS Platform 6	Reporter:	Van Halbert <vhalbert>
Component:	BAM	Assignee:	David Gutierrez <dgutierr>
Status:	CLOSED EOL	QA Contact:	Gui Jospin <gjospin>
Severity:	medium	Docs Contact:
Priority:	high
Version:	6.0.1	CC:	kverlaen, mbaluch, vhalbert
Target Milestone:	ER4
Target Release:	6.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1104294 (view as bug list)		Environment:
Last Closed:	2020-03-27 20:06:14 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:
Bug Depends On:
Bug Blocks:	1104294

Comment 2 David Gutierrez 2014-12-09 11:02:14 UTC

Fixed. 

Now, when a dashboard is automatically imported on startup (via initial module mechanism) no exception is raised if the dashboard is referencing to a non existing data source. All the artifacts (workspace, data providers & kpis) will be  imported ok. All the KPIS will show the "No data" available message as the datasource is not available. Once we create the datasource reference the KPIs will start to display data again.

As for the creation of the data source there exists two options:

1.- Force the end user to define the datasource after the installation.

2.- Create an initial module for the automatic creation of the data source reference on startup. 

In both cases the JNDI datasource must exists on the container prior to the installation of the app. The recommended option is #2 since all the artifacts: workspace, dashboard and datasource are created with no human intervention.

(master) https://github.com/droolsjbpm/dashboard-builder/commit/f760d34e2f7c190365907bf5c2243b742df2d36e

(6.2.x) https://github.com/droolsjbpm/dashboard-builder/commit/b6a1c34dfbf4de3528d3c71aaf3c007501f65a96


NOTE: please do let me know if this fix has to be backported to 6.0.x.

Comment 3 Van Halbert 2014-12-09 13:16:10 UTC

As for back porting to 6.0.x, If DV 6.2 (releasing next year) will be continueng on 6.0.x, then I would say yes.

Comment 4 David Gutierrez 2014-12-09 15:18:51 UTC

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

Comment 5 Jan Hrcek 2015-02-11 09:57:26 UTC

The import/export feature has been improved since this BZ was opened. User now has option to put exported kpis/workspaces/datasource definitions into dashbuilder's WEB-INF/deployments folder. I haven't found any issues with this feature, so marking this BZ as verified.