Bug 1259187

Summary:	Data types declared for some columns of dashbuilder data sets used in console are wrong
Product:	[Retired] JBoss BPMS Platform 6	Reporter:	Jan Hrcek <jhrcek>
Component:	Business Central	Assignee:	Marco Rietveld <mrietvel>
Status:	CLOSED EOL	QA Contact:	Lukáš Petrovický <lpetrovi>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	6.2.0	CC:	kverlaen, nmirasch
Target Milestone:	ER4
Target Release:	6.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-27 20:01:19 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 Jan Hrcek 2015-09-02 07:19:42 UTC

Description of problem:
Some dataset columns in jbpm-console's DashbuilderBootstrap are declared with wrong data type. This causes flurry of modals whenever user enters data of wrong type when defining new filter (e.g. String where number is expected). This can be easily prevented by using appropriate types when declaring dashbuilder data sets used by console.

This is quite a serious issue that needs to be resolved in the product. See 
https://issues.jboss.org/browse/JBPM-4724 for details

Version-Release number of selected component (if applicable):
BPM Suite 6.3.0

How reproducible:
Always

Steps to Reproduce:
1. In Process instance perspective start new filter creation.
2. Use column "processInstanceId" with operator "equals_to" and enter some String value like "asdf".
3. Click Ok and observe the deluge of modals.

Actual results:
6 modals with errors appears every time value of incorrect type is entered

Expected results:
The dialog for filter creation should not accept value of wrong type. This can be achieved by declaring correct type of columns when declaring dashbuilder data sets.

Additional info:

Comment 1 Neus Miras 2015-09-25 14:57:37 UTC

The dataset definition with the correct types has been fixed in following commits:

Console showcase:
Master
https://github.com/droolsjbpm/jbpm-console-ng/commit/b85d553911830ca72b46f9808969a2ff09f66b9d


6.3.x
https://github.com/droolsjbpm/jbpm-console-ng/commit/781c0f87790c7b222ba41804478e3db5672c4e51

kie-wb-distributions:
master
https://github.com/droolsjbpm/kie-wb-distributions/commit/76a2c56548a99cff677104c2a66e8ea8c32ab707

6.3.x
https://github.com/droolsjbpm/kie-wb-distributions/commit/324727e999206522a07b47257909f0f1a9651e65

Comment 2 Jan Hrcek 2015-10-22 05:23:16 UTC

Now it will be harder for users to make mistakes by entering incorrect filter parameters. Good job!
Verified with BPM Suite 6.2.0 ER4

Comment 3 PnT Account Manager 2017-12-07 23:37:39 UTC

Employee 'msalatin' has left the company.