Bug 1004767
Summary: | Decision Table Wizard: expand columns section has two default behaviours | ||
---|---|---|---|
Product: | [Retired] JBoss BRMS Platform 6 | Reporter: | Zuzana Krejčová <zkrejcov> |
Component: | Business Central | Assignee: | manstis |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Radovan Synek <rsynek> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.0.0 | CC: | etirelli, lpetrovi, rsynek, zkrejcov |
Target Milestone: | ER5 | Flags: | manstis:
needinfo+
zkrejcov: needinfo+ |
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:18:02 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
Zuzana Krejčová
2013-09-05 12:49:12 UTC
The behaviour is without change - if I skip "Columns to expand" page, columns are not expanded. If I go through this page (without changing anything on it), I can see expanded columns in the created table. What version of kie-wb did you use? I repeated my test with the current "master" and columns are expanded if you skip the "Column Expansion Page" and if you visit the "Column Expansion Page". I used the "mortgages" project; added "Applicant->age" and set a "Optional value list" of "10,20". Two rows are created in both scenarios for "10" and "20". This is a question for Radek - he is the QA contact now. I have tested this with BPMS-6.0.0.ER4. Now I found out that this issue happens only when you created some GDT with visiting the "Columns to expand" page first. 1. GDT with skipping "Columns to expand" page => columns expanded 2. GDT with visiting "Columns to expand" page => columns expanded 3. repeat step 1, now columns are NOT expanded. I hope this will help. Thanks for the steps to replicate. Issue (finally!) found and fixed. Verified on BRMS-6.0.0.ER5 |