October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1936) [DMN Editor] Connection between elements can not be deleted

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1936?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3390 to DROOLS-1936: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1936 (was: GUVNOR-3390) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: DMN Editor (was: DMN Tools) Fix Version/s: 7.5.0.Final (was: 7.5.0.Final) > [DMN Editor] Connection between elements can not be deleted > ----------------------------------------------------------- > > Key: DROOLS-1936 > URL: https://issues.jboss.org/browse/DROOLS-1936 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Fix For: 7.5.0.Final > > > User is unable to delete just connection between elements and preserve previously connected elements. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1938) [DMN Editor] Context table is not cleared

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1938?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3381 to DROOLS-1938: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1938 (was: GUVNOR-3381) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: DMN Editor (was: DMN Tools) Fix Version/s: 7.5.0.Final (was: 7.5.0.Final) > [DMN Editor] Context table is not cleared > ----------------------------------------- > > Key: DROOLS-1938 > URL: https://issues.jboss.org/browse/DROOLS-1938 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Fix For: 7.5.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1939) [DMN Editor] Toolbar reacts on the Enter key

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1939?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3251 to DROOLS-1939: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1939 (was: GUVNOR-3251) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: DMN Editor (was: DMN Tools) Affects Version/s: 7.1.0.Beta2 (was: 7.1.0.Beta2) Fix Version/s: 7.5.0.Final (was: 7.5.0.Final) > [DMN Editor] Toolbar reacts on the Enter key > -------------------------------------------- > > Key: DROOLS-1939 > URL: https://issues.jboss.org/browse/DROOLS-1939 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.1.0.Beta2 > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Trivial > Labels: reported-by-qe > Fix For: 7.5.0.Final > > Attachments: 1.png, 2.png, 3.png, 4.png > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1940) [DMN Editor] Dynamic Form "read only" not working

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1940?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3219 to DROOLS-1940: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1940 (was: GUVNOR-3219) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: DMN Editor (was: DMN Tools) Fix Version/s: 7.5.0.Final (was: 7.5.0.Final) > [DMN Editor] Dynamic Form "read only" not working > ------------------------------------------------- > > Key: DROOLS-1940 > URL: https://issues.jboss.org/browse/DROOLS-1940 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Pere Fernández Pérez > Fix For: 7.5.0.Final > > > I don't know whether it's related to my problems with a object hierarchy and {{@FormField}} re-use; but fields annotated {{@FieldReadOnly}} do not appear as read-only in the "Properties Panel". For example:- > {code} > @FieldDefinition(labelMode = LabelMode.OVERRIDE_I18N_KEY) > public class Id implements DMNProperty { > ... > @ReadOnly > @FieldReadOnly > public static final Boolean readOnly = true; > ... > } > public abstract class DMNModelInstrumentedBase implements DMNDefinition { > > //No @FormFields etc > > } > > public abstract class DMNElement extends DMNModelInstrumentedBase { > > @Property > @FormField > protected Id id; > .... > } > > public abstract class NamedElement extends DMNElement { > .... > } > > @FormDefinition(policy = FieldPolicy.ONLY_MARKED) > public class InformationItem extends NamedElement implements DMNPropertySet { > .... > } > {code} > The "Propeties" widget for "Id" can still be edited; although changes are not persisted (i.e. if I change the "Id" to "xyz" and then click on a different node and back to the one I changed the "Id" property is not "xyz"). I would however expected the {{TextBox}} to have been read-only and the value not editable. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1941) [DMN Editor] ToolBox: Add support for creating "source" nodes from a "target"

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1941?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3291 to DROOLS-1941: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1941 (was: GUVNOR-3291) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: DMN Editor (was: DMN Tools) Fix Version/s: 7.5.0.Final (was: 7.5.0.Final) > [DMN Editor] ToolBox: Add support for creating "source" nodes from a "target" > ----------------------------------------------------------------------------- > > Key: DROOLS-1941 > URL: https://issues.jboss.org/browse/DROOLS-1941 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Fix For: 7.5.0.Final > > > The "Toolbox" (see {{DMNFlowActionsToolboxControlProvider}}) currently supports creating "target" nodes from a "source" node and automatically joining "source" to "target" however [~tirelli] has requested the ability to select an existing "target" node and create a new "source" node from the Toolbox with the resulting connector joining "source" to "target". I.E. support creating the inverse of what is currently supported. > * Should be able to create a BKM from Decision (connection from BKM to Decision). At the moment you can select BKM and add Decision, but need to support selecting a Decision and making an incoming BKM > * Should be able to create a KnowledgeSources from bothh Decisions and BKMs. At the moment you can select a KnowledgeSource and adda Decision or BKM, but need to support selecting either a Decision or BKM and making an incoming KS -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1937) [DMN Editor] Dynamic Form Properties with nested hierarchy binds to wrong object/widget

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1937?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-3217 to DROOLS-1937: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1937 (was: GUVNOR-3217) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: DMN Editor (was: DMN Tools) Fix Version/s: 7.5.0.Final (was: 7.5.0.Final) > [DMN Editor] Dynamic Form Properties with nested hierarchy binds to wrong object/widget > --------------------------------------------------------------------------------------- > > Key: DROOLS-1937 > URL: https://issues.jboss.org/browse/DROOLS-1937 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Roger Martínez > Priority: Critical > Labels: Stunner > Fix For: 7.5.0.Final > > > The Dynamic Form generated from a nested object hierarchy binds objects/widgets to the incorrect instances. For example; the below classes define an {{Id}} form field that is used in both {{InputData}} (through inheritance) and {{InformationItem}} (through sub-form reference and inheritance). When changing the {{Id}} field (for example) in the {{InputData}} form property the "Id" value of the nested "Information Item" is updated. > {code} > public abstract class DMNModelInstrumentedBase implements DMNDefinition { > > //No @FormFields etc > > } > > public abstract class DMNElement extends DMNModelInstrumentedBase { > > @Property > @FormField > protected Id id; > > @Property > @FormField(afterElement = "id") > protected Label label; > > @Property > @FormField(afterElement = "label") > protected Description description; > > .... > } > > public abstract class NamedElement extends DMNElement { > > @Property > @FormField(afterElement = "description") > protected Name name; > > .... > } > > @FormDefinition(policy = FieldPolicy.ONLY_MARKED) > public class InformationItem extends NamedElement implements DMNPropertySet { > > @Property > @FormField(afterElement = "name") > protected QName typeRef; > > .... > } > public abstract class DRGElement extends NamedElement {} > @FormDefinition(policy = FieldPolicy.ONLY_MARKED) > public class InputData extends DRGElement { > ... > @PropertySet > @FormField(afterElement = "name") > protected InformationItem variable; > ... > } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1933) Support template keys in rule metadata inside rule templates

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1933?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1907 to DROOLS-1933: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1933 (was: GUVNOR-1907) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Template Editor (was: Guided Rule Templates) > Support template keys in rule metadata inside rule templates > ------------------------------------------------------------ > > Key: DROOLS-1933 > URL: https://issues.jboss.org/browse/DROOLS-1933 > Project: Drools > Issue Type: Feature Request > Components: Guided Template Editor > Reporter: Jim van Dam > Priority: Minor > Labels: rule, templates > > https://issues.jboss.org/browse/GUVNOR-1431 created support for the use of template keys in LHS and RHS expressions, but to be able to do the same for metadata would be very useful for us. > The rule template could look like this: > rule "xyz" > @Description(@{ruledesc}) > when > ... > then > ... > On load template data users can create rules including metadata -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1934) Allow a custom suffix for rule names in rule templates

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1934?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2160 to DROOLS-1934: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1934 (was: GUVNOR-2160) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Template Editor (was: Guided Rule Templates) Affects Version/s: 6.1.0.Final (was: drools_6.1.0.Final) > Allow a custom suffix for rule names in rule templates > ------------------------------------------------------ > > Key: DROOLS-1934 > URL: https://issues.jboss.org/browse/DROOLS-1934 > Project: Drools > Issue Type: Feature Request > Components: Guided Template Editor > Affects Versions: 6.1.0.Final > Environment: RedHat Linux 6.3 x86_64; Firefox 10.0.5 > Reporter: Stephen Slaboda > Labels: drools-wb, templates > > When attempting to extend a templated rule, there are many choices provided, but they are all suffixed by numbers, which makes it difficult to determine which rule is actually desired. Likewise, looking at the source or setting up unit tests is a bit tedious for the same reasons. Please investigate some way to make it more obvious which rule is being referenced, such as a suffix that is specified as part of the template data ? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1935) Rule Templates: Separate template from data

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1935?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1929 to DROOLS-1935: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1935 (was: GUVNOR-1929) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Template Editor (was: Guided Rule Templates) Affects Version/s: 5.5.0.Final (was: drools-5.4.0.Final) > Rule Templates: Separate template from data > ------------------------------------------- > > Key: DROOLS-1935 > URL: https://issues.jboss.org/browse/DROOLS-1935 > Project: Drools > Issue Type: Feature Request > Components: Guided Template Editor > Affects Versions: 5.5.0.Final > Reporter: Michael Anstis > > Rule Templates in Guvnor allow a template to be defined and data backing the same template. It would be good to be able to (a) separate template from data so a single template can have different sets of data applied, or (b) different templates can have the same data applied, (c) allow creation of data by grid, by upload, by RPC etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1931) Allow Formulas in Guided Rule Template Keys

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1931?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2155 to DROOLS-1931: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1931 (was: GUVNOR-2155) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Template Editor (was: Guided Rule Templates) Affects Version/s: 6.1.0.Final (was: drools_6.1.0.Final) > Allow Formulas in Guided Rule Template Keys > ------------------------------------------- > > Key: DROOLS-1931 > URL: https://issues.jboss.org/browse/DROOLS-1931 > Project: Drools > Issue Type: Feature Request > Components: Guided Template Editor > Affects Versions: 6.1.0.Final > Environment: RedHat Linux 6.3 x86_64; Firefox 10.0.5 > Reporter: Stephen Slaboda > Labels: formulas, templates, workbench > > Please consider adding the ability to enter a formula into the data tab in the Guided Rule Template editor. While this is possible via the Guided Decision Table editor, it is not possible in the Guided Rule Template editor. This appears to be a gap in the similarities between the two. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 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