Red Hat Bugzilla – Bug 1259187
Data types declared for some columns of dashbuilder data sets used in console are wrong
Last modified: 2017-12-07 18:37:39 EST
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
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.
6 modals with errors appears every time value of incorrect type is entered
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.
The dataset definition with the correct types has been fixed in following commits:
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
Employee 'email@example.com' has left the company.