Bug 1020892
Summary: | Longer content of history variables dialog is over the nearby fields | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Ivo Bek <ibek> | ||||
Component: | Business Central | Assignee: | Mauricio Salatino <msalatin> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Ivo Bek <ibek> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 6.0.0 | CC: | kverlaen | ||||
Target Milestone: | ER6 | ||||||
Target Release: | 6.0.0 | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2014-08-06 20:07:00 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: | |||||||
Attachments: |
|
There is no way around this problem, because we don't have resizable popups. There are some plans to migrate these screens out of the popups so we can have a split perspective with the variable list and the details panels, like in tasks. Maybe it's a good time to do that but it could take some time, so I will check with Kris about this one. I've added a tooltip that shows the full content of the old and new value for the variable. I'm also trimming the variable value if it has more than 20 chars, so if it is long the user will need to point the table row in order to see the tooltip with the full value: Fixed in 6.0.x: http://github.com/droolsjbpm/jbpm-console-ng/commit/6cdcac446 Verified in BPMS 6.0.0.ER7 Filed another BZ 1048230 for the history variable window. It is not possible (yet) to test how the table looks and whether the content is over the nearby fields. |
Created attachment 813769 [details] Variable history dialog Description of problem: The attached screenshot explains the problem.