Red Hat Bugzilla – Bug 1291732
Process Definitions perspective - process Name column not enabled by default
Last modified: 2016-01-04 08:10:01 EST
Created attachment 1106038 [details]
Screenshot illustrating the issue
Description of problem:
There's been change in default column setup in Process Definitions perspective. See screenshots illustrating the issue.
In 6.1.4 the Name and Actions columns were always enabled (it was not even possible to disable Name column). I think it made a lot of sense, because this table is useless unless user knows which process he is starting.
In 6.1.5 the process Name column is disabled by default. It can be enabled (so there is a workaround) but it is DISABLED BY DEFAULT. The table is basically useless without this column enabled, so user MUST enable it if he wants to know which process he is starting.
This is a regression since BPM Suite 6.1.4 most likely introduced by fix to bug# 1276354 which was included in BPM Suite 6.1.5
Version-Release number of selected component (if applicable):
BPM Suite 6.1.5
Steps to Reproduce:
1. Go to Authoring perspective and deploy some project with process definition (e.g. Evaluation)
2. Go to Process Management > Processs Process definitions
The Name column is not enabled - it is not clear which row corresponds to which process
The Name column was fixed in previous versions - it couldn't be disabled even if user wanted.
Created attachment 1106039 [details]
Screenshot showing how it worked in 6.1.4
Other perspectives are affected by the change too:
1) Process Instances: The columns Id and Name were fixed (enabled all the time), but are now configurable and disabled by default
2) Tasks: The columns Actions is now Fixed (THIS CHANGE IS DESIRABLE), but was previously Configurable and disabled by default.
This PR have the commit to restore the behavior showing the default selected columns:
The PR has been merged
The implementation is now working as before. Verified with BPM Suite 6.1.5 CR2