Bug 1329840 - Selecting item in service repository does not meet documentation
Summary: Selecting item in service repository does not meet documentation
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Designer
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Tihomir Surdilovic
QA Contact: Jozef Marko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-23 18:41 UTC by Jozef Marko
Modified: 2020-03-27 19:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 19:11:11 UTC
Type: Bug


Attachments (Terms of Use)

Description Jozef Marko 2016-04-23 18:41:52 UTC
Description of problem:
The way how to select item in Service repository is not clear. Documentation [1] claims that selection should be done as double click. In real user has to select item from Service repository and confirm this selection with appropriate button. But the selection of one item is confusing. User can select only one column of the table. If user user tries to select whole line of the table by double click (the way described in documentation) he will not succeed.


Version-Release number of selected component (if applicable):
6.3.0.ER3


Steps to Reproduce:
1. Open any business process
2. Click on service repository button
3. Connect to url [2]
4. Try to select any displayed service


Actual results:
You will be able to select only one column of the table. It is not clear which service selected in that moment.


Expected results:
From the UI should be clear which service is selected. If improvement of service selection will be implemented in different way from the one described in documentation also documentation must be updated.

[1]
https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_BPM_Suite/6.2/html/User_Guide/sect-Domain-specific_Tasks.html   section 4.15.2.1

[2]
http://docs.jboss.org/jbpm/v6.2/repository/


Note You need to log in before you can comment on or make changes to this bug.