[JBoss JIRA] (DROOLS-625) Implement a passive pattern
by Tibor Zimányi (JIRA)
[ https://issues.jboss.org/browse/DROOLS-625?page=com.atlassian.jira.plugin... ]
Tibor Zimányi closed DROOLS-625.
--------------------------------
Resolution: Done
Closing this as it was done, based on the linked commits.
> Implement a passive pattern
> ---------------------------
>
> Key: DROOLS-625
> URL: https://issues.jboss.org/browse/DROOLS-625
> Project: Drools
> Issue Type: Feature Request
> Reporter: Mario Fusco
> Assignee: Mario Fusco
>
> Prepending a pattern with a '?' should make it passive (i.e. non reactive to right insertions) as dimostrated by the following test case.
> {code}
> @Test
> public void testPassiveInsert() throws Exception {
> String str =
> "global java.util.List list\n" +
> "rule R when\n" +
> " $i : Integer()\n" +
> " ?String( this == $i.toString() )\n" +
> "then\n" +
> " list.add( $i );\n" +
> "end\n";
> KieSession ksession = new KieHelper()
> .addContent(str, ResourceType.DRL)
> .build()
> .newKieSession();
> List<Integer> list = new ArrayList<Integer>();
> ksession.setGlobal("list", list);
> ksession.insert(1);
> ksession.insert("2");
> ksession.fireAllRules();
> assertEquals(0, list.size());
> ksession.insert("1");
> ksession.fireAllRules();
> assertEquals(0, list.size());
> ksession.insert(2);
> ksession.fireAllRules();
> assertEquals(1, list.size());
> assertEquals(2, (int)list.get(0));
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-592) Condition Evaluator should instantiate argument only once.
by Tibor Zimányi (JIRA)
[ https://issues.jboss.org/browse/DROOLS-592?page=com.atlassian.jira.plugin... ]
Tibor Zimányi closed DROOLS-592.
--------------------------------
Resolution: Won't Do
> Condition Evaluator should instantiate argument only once.
> ----------------------------------------------------------
>
> Key: DROOLS-592
> URL: https://issues.jboss.org/browse/DROOLS-592
> Project: Drools
> Issue Type: Feature Request
> Affects Versions: 6.2.0.Beta1
> Reporter: david hendi
> Assignee: Mario Fusco
> Priority: Optional
>
> the argument(s) used within the evaluate method of a Conditional Evaluator should instantiate argument only once in order to reduce object creation and GC.
> current generated class:
> public class ConditionEvaluatorfff283c427e34a39877bce16cac05521
> implements ConditionEvaluator
> {
> private static final String EXPRESSION = "!( ids contains 614201302l )";
> private final Declaration[] declarations;
>
> public ConditionEvaluatorfff283c427e34a39877bce16cac05521(Declaration[] paramArrayOfDeclaration)
> {
> this.declarations = paramArrayOfDeclaration;
> }
>
> public boolean evaluate(InternalFactHandle paramInternalFactHandle, InternalWorkingMemory paramInternalWorkingMemory, LeftTuple paramLeftTuple)
> {
> Collection localCollection = ((Context)paramInternalFactHandle.getObject()).getIds();
> Long localLong = new Long("614201302");
> return !(localLong == null ? false : localCollection == null ? false : EvaluatorHelper.contains(localCollection, localLong));
> }
> }
> proposed class:
> public class ConditionEvaluatorfff283c427e34a39877bce16cac05521
> implements ConditionEvaluator
> {
> private static final String EXPRESSION = "!( ids contains 614201302l )";
> private static Long localLong = new Long("614201302");
> private final Declaration[] declarations;
>
> public ConditionEvaluatorfff283c427e34a39877bce16cac05521(Declaration[] paramArrayOfDeclaration)
> {
> this.declarations = paramArrayOfDeclaration;
> }
>
> public boolean evaluate(InternalFactHandle paramInternalFactHandle, InternalWorkingMemory paramInternalWorkingMemory, LeftTuple paramLeftTuple)
> {
> Collection localCollection = ((Context)paramInternalFactHandle.getObject()).getIds();
>
> return !(localLong == null ? false : localCollection == null ? false : EvaluatorHelper.contains(localCollection, localLong));
> }
> }
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2655) [DMN Designer]: Decision Table: Automatically create input columns for each InputData element
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2655?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2655:
--------------------------------
Description:
[~tari_manga] suggested it advantageous to create input columns for each {{InputData}} element linked to the {{Decision}}/{{BusinessKnowledgeModel}} containing the {{DecisionTable}} expression. For example, if a BKM has 2 {{InputData}} nodes of simple data-types then two columns should be created. If a BKM has 1 {{InputData}} node of complex data-type that consists of 3 elements then 3 columns should be created.
- For simple data types the input column names should correspond exactly to InputData elements.
- For complex data types, we should use dot notation, e.g. Person.name, Person.salary ...
h3. PR Manual Acceptance Test
- Check Decision Table Decision node, with inputs (/)
- Check Decision Table Decision node, without inputs
- Check Non Decision Table Decision node, with inputs
- Check Non Decision Table Decision node, without inputs
- Check Decision Table BKM node, with inputs
- Check Decision Table BKM node, without inputs
- Check Non Decision Table BKM node, with inputs
- Check Non Decision Table BKM node, without inputs
was:
[~tari_manga] suggested it advantageous to create input columns for each {{InputData}} element linked to the {{Decision}}/{{BusinessKnowledgeModel}} containing the {{DecisionTable}} expression. For example, if a BKM has 2 {{InputData}} nodes of simple data-types then two columns should be created. If a BKM has 1 {{InputData}} node of complex data-type that consists of 3 elements then 3 columns should be created.
- For simple data types the input column names should correspond exactly to InputData elements.
- For complex data types, we should use dot notation, e.g. Person.name, Person.salary ...
h3. PR Manual Acceptance Test
- Check Decision Table Decision node, with inputs (?)
- Check Decision Table Decision node, without inputs
- Check Non Decision Table Decision node, with inputs
- Check Non Decision Table Decision node, without inputs
- Check Decision Table BKM node, with inputs
- Check Decision Table BKM node, without inputs
- Check Non Decision Table BKM node, with inputs
- Check Non Decision Table BKM node, without inputs
> [DMN Designer]: Decision Table: Automatically create input columns for each InputData element
> ---------------------------------------------------------------------------------------------
>
> Key: DROOLS-2655
> URL: https://issues.jboss.org/browse/DROOLS-2655
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> [~tari_manga] suggested it advantageous to create input columns for each {{InputData}} element linked to the {{Decision}}/{{BusinessKnowledgeModel}} containing the {{DecisionTable}} expression. For example, if a BKM has 2 {{InputData}} nodes of simple data-types then two columns should be created. If a BKM has 1 {{InputData}} node of complex data-type that consists of 3 elements then 3 columns should be created.
> - For simple data types the input column names should correspond exactly to InputData elements.
> - For complex data types, we should use dot notation, e.g. Person.name, Person.salary ...
> h3. PR Manual Acceptance Test
> - Check Decision Table Decision node, with inputs (/)
> - Check Decision Table Decision node, without inputs
> - Check Non Decision Table Decision node, with inputs
> - Check Non Decision Table Decision node, without inputs
> - Check Decision Table BKM node, with inputs
> - Check Decision Table BKM node, without inputs
> - Check Non Decision Table BKM node, with inputs
> - Check Non Decision Table BKM node, without inputs
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFLY-10690) Rename module name of rxjava
by Dmitrii Tikhomirov (JIRA)
[ https://issues.jboss.org/browse/WFLY-10690?page=com.atlassian.jira.plugin... ]
Dmitrii Tikhomirov reassigned WFLY-10690:
-----------------------------------------
Assignee: Dmitrii Tikhomirov (was: Alessio Soldano)
> Rename module name of rxjava
> ----------------------------
>
> Key: WFLY-10690
> URL: https://issues.jboss.org/browse/WFLY-10690
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Reporter: Marek Kopecký
> Assignee: Dmitrii Tikhomirov
> Priority: Critical
>
> Rename module name of rxjava:
> {noformat}
> $ cat ./modules/system/layers/base/io/reactivex/rxjava/main/module.xml | grep "module.name.*rx\|jar"
> <module name="io.reactivex.rxjava" xmlns="urn:jboss:module:1.5">
> <resource-root path="rxjava-2.1.9.jar"/>
> $
> {noformat}
> Module name doesn't reflect real rxjava2 package and artifactId, see [maven repo|https://mvnrepository.com/artifact/io.reactivex.rxjava2/rxjava/2.1.9]:
> {code:xml}
> <dependency>
> <groupId>io.reactivex.rxjava2</groupId>
> <artifactId>rxjava</artifactId>
> <version>2.1.9</version>
> </dependency>
> {code}
> Correct module name should be "io.reactivex.rxjava2.rxjava".
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2715) Null Pointer Exception on Accumulate
by Pedro Almeida (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2715?page=com.atlassian.jira.plugi... ]
Pedro Almeida closed DROOLS-2715.
---------------------------------
There is no bug, just a bad usage !
> Null Pointer Exception on Accumulate
> ------------------------------------
>
> Key: DROOLS-2715
> URL: https://issues.jboss.org/browse/DROOLS-2715
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.6.0.Final, 7.7.0.Final, 7.8.0.Final
> Reporter: Pedro Almeida
> Assignee: Mario Fusco
> Attachments: DroolsBug.zip
>
>
> I was able to get a Null Pointer out of a simple accumulate.
> Download the attached zip and run the test.
> java.lang.RuntimeException: java.lang.NullPointerException
> at org.drools.core.rule.SingleAccumulate.init(SingleAccumulate.java:88)
> at org.drools.core.phreak.PhreakAccumulateNode.doLeftInserts(PhreakAccumulateNode.java:148)
> at org.drools.core.phreak.PhreakAccumulateNode.doNode(PhreakAccumulateNode.java:89)
> at org.drools.core.phreak.RuleNetworkEvaluator.switchOnDoBetaNode(RuleNetworkEvaluator.java:567)
> at org.drools.core.phreak.RuleNetworkEvaluator.evalBetaNode(RuleNetworkEvaluator.java:538)
> at org.drools.core.phreak.RuleNetworkEvaluator.evalNode(RuleNetworkEvaluator.java:373)
> at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:333)
> at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:169)
> at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:127)
> at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:212)
> at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:87)
> at org.drools.core.concurrent.AbstractRuleEvaluator.internalEvaluateAndFire(AbstractRuleEvaluator.java:34)
> at org.drools.core.concurrent.SequentialRuleEvaluator.evaluateAndFire(SequentialRuleEvaluator.java:43)
> at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1067)
> at org.drools.core.common.DefaultAgenda.internalFireAllRules(DefaultAgenda.java:1014)
> at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1006)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1308)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1299)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1283)
> at tests.TestsClass.test(TestsClass.java:52)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
> at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
> at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
> at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
> Caused by: java.lang.NullPointerException
> at org.drools.core.reteoo.BaseLeftTuple.getObject(BaseLeftTuple.java:628)
> at org.drools.core.reteoo.BaseTuple.getObject(BaseTuple.java:48)
> at defaultpkg.Rule_Rule_X0Accumulate0Invoker.init(Rule_Rule_X0Accumulate0Invoker.java:21)
> at org.drools.core.rule.SingleAccumulate.init(SingleAccumulate.java:82)
> ... 41 more
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2715) Null Pointer Exception on Accumulate
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2715?page=com.atlassian.jira.plugi... ]
Mario Fusco resolved DROOLS-2715.
---------------------------------
Resolution: Done
Fixed by https://github.com/kiegroup/drools/commit/7a076259e381a687547c3df6615ba2a...
> Null Pointer Exception on Accumulate
> ------------------------------------
>
> Key: DROOLS-2715
> URL: https://issues.jboss.org/browse/DROOLS-2715
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.6.0.Final, 7.7.0.Final, 7.8.0.Final
> Reporter: Pedro Almeida
> Assignee: Mario Fusco
> Attachments: DroolsBug.zip
>
>
> I was able to get a Null Pointer out of a simple accumulate.
> Download the attached zip and run the test.
> java.lang.RuntimeException: java.lang.NullPointerException
> at org.drools.core.rule.SingleAccumulate.init(SingleAccumulate.java:88)
> at org.drools.core.phreak.PhreakAccumulateNode.doLeftInserts(PhreakAccumulateNode.java:148)
> at org.drools.core.phreak.PhreakAccumulateNode.doNode(PhreakAccumulateNode.java:89)
> at org.drools.core.phreak.RuleNetworkEvaluator.switchOnDoBetaNode(RuleNetworkEvaluator.java:567)
> at org.drools.core.phreak.RuleNetworkEvaluator.evalBetaNode(RuleNetworkEvaluator.java:538)
> at org.drools.core.phreak.RuleNetworkEvaluator.evalNode(RuleNetworkEvaluator.java:373)
> at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:333)
> at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:169)
> at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:127)
> at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:212)
> at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:87)
> at org.drools.core.concurrent.AbstractRuleEvaluator.internalEvaluateAndFire(AbstractRuleEvaluator.java:34)
> at org.drools.core.concurrent.SequentialRuleEvaluator.evaluateAndFire(SequentialRuleEvaluator.java:43)
> at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1067)
> at org.drools.core.common.DefaultAgenda.internalFireAllRules(DefaultAgenda.java:1014)
> at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1006)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1308)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1299)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1283)
> at tests.TestsClass.test(TestsClass.java:52)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
> at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
> at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
> at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
> Caused by: java.lang.NullPointerException
> at org.drools.core.reteoo.BaseLeftTuple.getObject(BaseLeftTuple.java:628)
> at org.drools.core.reteoo.BaseTuple.getObject(BaseTuple.java:48)
> at defaultpkg.Rule_Rule_X0Accumulate0Invoker.init(Rule_Rule_X0Accumulate0Invoker.java:21)
> at org.drools.core.rule.SingleAccumulate.init(SingleAccumulate.java:82)
> ... 41 more
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2720) [DMN Designer] Do not execute a command to update a cell value if the value has not changed
by Michael Anstis (JIRA)
Michael Anstis created DROOLS-2720:
--------------------------------------
Summary: [DMN Designer] Do not execute a command to update a cell value if the value has not changed
Key: DROOLS-2720
URL: https://issues.jboss.org/browse/DROOLS-2720
Project: Drools
Issue Type: Bug
Components: DMN Editor
Affects Versions: 7.8.0.Final
Reporter: Jozef Marko
Assignee: Michael Anstis
A command is executed by {{TextBoxDOMElement}} and {{TextAreaDOMElement}} when the editor looses focus however the command should not be executed if the value has not changed as it leads to what appears to be weird behaviour when undoing operations in the UI.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFLY-10264) Resteasy JSON provider fails in EE7 module
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/WFLY-10264?page=com.atlassian.jira.plugin... ]
Alessio Soldano resolved WFLY-10264.
------------------------------------
Fix Version/s: (was: 13.0.0.Beta1)
Resolution: Out of Date
This is basically out-of-date now that we moved to RESTEasy 3.6.0.Final and the ee8.preview.mode switch is gone (we're defaulting to EE8 mode).
> Resteasy JSON provider fails in EE7 module
> ------------------------------------------
>
> Key: WFLY-10264
> URL: https://issues.jboss.org/browse/WFLY-10264
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Reporter: Stuart Douglas
> Assignee: Jim Ma
> Priority: Blocker
> Labels: blocker-WF14
>
> org.jboss.resteasy.plugins.providers.jsonb.AbstractJsonBindingProvider depends on org.eclipse.yasoon classes, however these are not present when in EE7 mode
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2654) [DMN Designer] Automatically show (Name) edit control when adding new ContextEntries
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2654?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2654:
--------------------------------
Description:
When a new {{ContextEntry}} is added the User must double click on the {{Name}} cell to change the default value.
[~tari_manga] suggested it would be good if the {{Name}} editor was automatically shown and focused when the User creates a new {{ContextEntry}}.
h3. Manual Acceptance test
For each column/row agreed in comments that should support this feature:
- Append row/column, fill name, save reopen, check value stored (/)
- Try undo/redo after appending row/column (/)
- Add multiple items in row, check always the last is edited (/)
was:
When a new {{ContextEntry}} is added the User must double click on the {{Name}} cell to change the default value.
[~tari_manga] suggested it would be good if the {{Name}} editor was automatically shown and focused when the User creates a new {{ContextEntry}}.
h3. Manual Acceptance test
For each column/row agreed in comments that should support this feature:
- Append row/column, fill name, save reopen, check value stored (/)
- Try undo/redo after appending row/column (x)
- Add multiple items in row, check always the last is edited (/)
> [DMN Designer] Automatically show (Name) edit control when adding new ContextEntries
> ------------------------------------------------------------------------------------
>
> Key: DROOLS-2654
> URL: https://issues.jboss.org/browse/DROOLS-2654
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Labels: UX, UXTeam
>
> When a new {{ContextEntry}} is added the User must double click on the {{Name}} cell to change the default value.
> [~tari_manga] suggested it would be good if the {{Name}} editor was automatically shown and focused when the User creates a new {{ContextEntry}}.
> h3. Manual Acceptance test
> For each column/row agreed in comments that should support this feature:
> - Append row/column, fill name, save reopen, check value stored (/)
> - Try undo/redo after appending row/column (/)
> - Add multiple items in row, check always the last is edited (/)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years