October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1895) Find better location for the Audit log button

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1895?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2550 to DROOLS-1895: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1895 (was: GUVNOR-2550) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor (was: Guided Decision Table) > Find better location for the Audit log button > --------------------------------------------- > > Key: DROOLS-1895 > URL: https://issues.jboss.org/browse/DROOLS-1895 > Project: Drools > Issue Type: Task > Components: Guided Decision Table Editor > Reporter: Zuzka Krejčová > Assignee: Joe Sniezek > Priority: Minor > Labels: reported-by-qe > > The Audit log button now resides inside the View menu, which holds options for different view modes. Since Audit log is another part of the UI/feature, not a view mode, it would be better to move to a more appropriate place. > [~jsniezek] - any advice is welcome. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1896) Unify ModelField creation accross drools-wb repository tests

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1896?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3512 to DROOLS-1896: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1896 (was: GUVNOR-3512) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor Guided Rule Editor (was: DSL) (was: Guided Decision Table) (was: Guided Rule Editor) (was: XLS Decision Tables) Affects Version/s: 7.3.0.Final (was: 7.3.0.Final) > Unify ModelField creation accross drools-wb repository tests > ------------------------------------------------------------ > > Key: DROOLS-1896 > URL: https://issues.jboss.org/browse/DROOLS-1896 > Project: Drools > Issue Type: Task > Components: Guided Decision Table Editor, Guided Rule Editor > Affects Versions: 7.3.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Minor > > A lot of tests in the drools-wb/drools-wb-screens respository need a initialization using a lot of ModelFields instances. This initialization code is just calling of contructor multple times. The problem is that the constructor has like 5/6 parameters where just two of them are needed for tests. > This task should introduce static method that will construct ModelField but the most of constructor arguments will be hardcoded. This static method should be reused in all drools-wb-drools-wb-screens client tests. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1851) Guided Decision table: Multiple 'otherwise' for sub-group support

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1851?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1954 to DROOLS-1851: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1851 (was: GUVNOR-1954) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor (was: Guided Decision Table) Affects Version/s: 5.5.0.Final (was: drools-5.4.0.Final) > Guided Decision table: Multiple 'otherwise' for sub-group support > ----------------------------------------------------------------- > > Key: DROOLS-1851 > URL: https://issues.jboss.org/browse/DROOLS-1851 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Affects Versions: 5.5.0.Final > Reporter: Toshiya Kobayashi > Assignee: Michael Anstis > Attachments: otherwise.png, repository_export_otherwise.xml > > > If you set 'otherwise' for a cell, it equals to the rest of all defined values in the column. The request is accepting multiple 'otherwise' and it equals to the rest of all defined values in the sub-group. What is 'sub-group'? The intuitive approach is that Guvnor recognizes 'sub-group' from left to right. So if you have the same value cells (= so you can merge) in the left next column, it is the one sub-group for the 'otherwise'. It might be easier to understand with the image (See attached otherwise.png). > Words from a customer: > ===== > 1. I think the simplest approach to defining sub-groups will be to evaluate conditions from Left to right. So for the example I have provided Flight# will be the first sub-group, Airline the next sub-group. However if a different approach can be provided to create the sub-groups that would be acceptable as long as it is easy to create and visualize the sub-groups, specially for the Business Users. > 2. I think the sub-groups could be the default behavior. When multiple otherwise would be supported for a column an approach would be needed to understand the sub-group to which one otherwise applies, and the sub-group to which the 2nd otherwise applies within the same column. However from a backward compatibility perspective a toggle could be created (since currently otherwise can be on any row in the column). > ===== > I think the key part is if we can implement it without newly introduced meta-data. If you think we need to be more specific, please let me know. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1852) Guided decision table: "Value Lists" should be created with list widget rather than separating with commas

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1852?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1961 to DROOLS-1852: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1852 (was: GUVNOR-1961) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor (was: Guided Decision Table) Affects Version/s: 5.5.0.Final (was: drools-5.4.0.Beta2) > Guided decision table: "Value Lists" should be created with list widget rather than separating with commas > ---------------------------------------------------------------------------------------------------------- > > Key: DROOLS-1852 > URL: https://issues.jboss.org/browse/DROOLS-1852 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Affects Versions: 5.5.0.Final > Reporter: Michael Anstis > Assignee: Guilherme Carreiro > Priority: Minor > > A list of possible values are defined by typing literal values separated by commas into a TextBox. This should be changed to use a new widget that allows a list of values to be created, with the value editor being correct for the field's data-type. This widget will also need to be used in the Wizard. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1853) Rule Asset: Show the old test scenario results where this rule was used.

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1853?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1745 to DROOLS-1853: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1853 (was: GUVNOR-1745) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor Guided Rule Editor Guided Template Editor (was: Guided Decision Table) (was: Guided Rule Editor) (was: Guided Rule Templates) > Rule Asset: Show the old test scenario results where this rule was used. > ------------------------------------------------------------------------ > > Key: DROOLS-1853 > URL: https://issues.jboss.org/browse/DROOLS-1853 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor, Guided Rule Editor, Guided Template Editor > Reporter: Toni Rikkola > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1854) Integrate Data Set Module with Guided Editor

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1854?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2357 to DROOLS-1854: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1854 (was: GUVNOR-2357) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Data Model Oracle Guided Decision Table Editor Guided Decision Tree Editor Guided Rule Editor Guided Template Editor (was: Data Model Oracle) (was: Guided Decision Table) (was: Guided Decision Tree) (was: Guided Rule Editor) (was: Guided Rule Templates) (was: Guided Score Card) > Integrate Data Set Module with Guided Editor > -------------------------------------------- > > Key: DROOLS-1854 > URL: https://issues.jboss.org/browse/DROOLS-1854 > Project: Drools > Issue Type: Feature Request > Components: Data Model Oracle, Guided Decision Table Editor, Guided Decision Tree Editor, Guided Rule Editor, Guided Template Editor > Reporter: Justin Holmes > > As a rule author using the guided editor, > I would like the editors to integrate with the data set module, > so that I can author rules using Objects / Enumerations that are driven from an external data source, such as a database. > An example would be a set of country codes maintained in a database. I would like to write a decision table that has access to those country codes without having to replicate them in the guided editors. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1847) [Guided Decision Table] Enable renaming of the binding variable of a fact pattern associated with simple condition column

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1847?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3510 to DROOLS-1847: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1847 (was: GUVNOR-3510) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor (was: Guided Decision Table) Affects Version/s: 7.0.0.Final (was: 7.x) > [Guided Decision Table] Enable renaming of the binding variable of a fact pattern associated with simple condition column > ------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-1847 > URL: https://issues.jboss.org/browse/DROOLS-1847 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.Final > Reporter: Mark Coble > Assignee: Mark Coble > Priority: Minor > > Simple Condition Columns are created using fact patterns which can be bound to a variable name. Once saved this binding variable name cannot be changed. The user must delete the column and recreate if a new binding name is desired. > This feature request is to enable renaming of the binding variable which also updates any previous references to the old name, i.e., in an action column. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1848) Selection in "advanced" enum list will be deleted in certain scenario

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1848?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2052 to DROOLS-1848: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1848 (was: GUVNOR-2052) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor Guided Rule Editor Guided Template Editor (was: Guided Decision Table) (was: Guided Rule Editor) (was: Guided Rule Templates) Affects Version/s: 5.5.0.Final (was: drools-5.5.0.Final) > Selection in "advanced" enum list will be deleted in certain scenario > --------------------------------------------------------------------- > > Key: DROOLS-1848 > URL: https://issues.jboss.org/browse/DROOLS-1848 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor, Guided Rule Editor, Guided Template Editor > Affects Versions: 5.5.0.Final > Environment: Tomcat 6.x, Linux > Reporter: Xiandong su > Assignee: Mark Coble > > When there are 3 drop downs, one determines the values of the other, the selection in the last drop down will be removed (even after being saved before) when two actions occurred to the rules in the row. Two actions includes changing the rule body, or saving the rule twice. > For example: I have the following statement: > in fact [field1] [field2][field3] > each of the field is presented as a drop down by using the advanced ENUM feature - 1 determines the values in 2 and the selection of 2 determines the value of 3. > After the value in field3 is selected, I can move on and make the changes in the rule. When the first change occurred, Guvnor remembers the values being selected in all 3 fields. But when another change is make (or simply save the rule again), the selected value in the last field (field3) will be forgotten. > Another scenario is that, after all the selections in the drop down are saved, we rename the rule (counted as 1 action), and then clicking save file will cause the lost of the selection in the last drop down. > Please note this is only happening to the last field. I did not go further and make the statement contain more than 3 drop downs. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1849) Guided decision table: Require the ability to hide facts

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1849?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-339 to DROOLS-1849: ----------------------------------------------- Project: Drools (was: Guvnor) Key: DROOLS-1849 (was: GUVNOR-339) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor Guided Rule Editor Guided Template Editor (was: Guided Decision Table) (was: Guided Rule Editor) (was: Guided Rule Templates) Affects Version/s: 5.5.0.Final (was: drools-5.0.0) > Guided decision table: Require the ability to hide facts > -------------------------------------------------------- > > Key: DROOLS-1849 > URL: https://issues.jboss.org/browse/DROOLS-1849 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor, Guided Rule Editor, Guided Template Editor > Affects Versions: 5.5.0.Final > Reporter: Ed Wallen > Assignee: Michael Anstis > > I would like to have control over what facts are available to a decision table in Guvnor. > We may have facts A, B, and C and Decision Tables 1 and 2. We want to be able to configure Decision Table 1 to only see facts A and for Decision Table 2 to see facts B & C. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1850) Guided decision table: Add meta-data to control which fact properties are exposed when configuring conditions or actions

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1850?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-342 to DROOLS-1850: ----------------------------------------------- Project: Drools (was: Guvnor) Key: DROOLS-1850 (was: GUVNOR-342) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Decision Table Editor Guided Rule Editor Guided Template Editor (was: Guided Decision Table) (was: Guided Rule Editor) (was: Guided Rule Templates) Affects Version/s: 5.5.0.Final (was: drools-5.0.0) > Guided decision table: Add meta-data to control which fact properties are exposed when configuring conditions or actions > ------------------------------------------------------------------------------------------------------------------------ > > Key: DROOLS-1850 > URL: https://issues.jboss.org/browse/DROOLS-1850 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor, Guided Rule Editor, Guided Template Editor > Affects Versions: 5.5.0.Final > Reporter: Ed Wallen > Assignee: Michael Anstis > > I would like to have the control to hide or display properties that are exposed as conditions and actions in guvnor. I have a utility class that calculates a number for a condition check but when configured in the decision table it is selectable as an action property but I only want it configured for a condition. > Public Class A { > // Show the following method as a condition property and not an action property > public int calculateNumber() { > do some calculation.. > return results. > } > // Show the following method as a condition property and not an action and property > public BigDecimal getBalance() { > return balance > } > // Show the following method as a action property and not an condition property > public void assignValue(String value) { > this.value = value; > } > } -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2017