[JBoss JIRA] (DROOLS-3430) [DMN Designer] [Edge] Update Name via Name And DataType dialog
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3430?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3430:
-----------------------------------
Sprint: 2019 Week 02-04, 2018 Week 51-01 (was: 2018 Week 51-01)
> [DMN Designer] [Edge] Update Name via Name And DataType dialog
> --------------------------------------------------------------
>
> Key: DROOLS-3430
> URL: https://issues.jboss.org/browse/DROOLS-3430
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.16.0.Final
> Environment: Win10, Edge, eap-7.2
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools, edge
> Attachments: Screenshot from 2018-12-13 07-50-37.png
>
>
> User can rename boxed expression elements by single click into given grid cell. Then the *Name and DataType dialog* is shown to the user where he can rename the given element. The problem on *Edge* is confirming this renaming. On other browsers renaming is confirmed with clicking somewhere into canvas. On the *Edge* clicking to canvas close the dialog and renaming is discarded.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 5 months
[JBoss JIRA] (DROOLS-3468) [DMN Designer] Support Decision Service invocation
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3468?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3468:
-----------------------------------
Sprint: 2019 Week 02-04, 2018 Week 51-01 (was: 2018 Week 51-01)
> [DMN Designer] Support Decision Service invocation
> --------------------------------------------------
>
> Key: DROOLS-3468
> URL: https://issues.jboss.org/browse/DROOLS-3468
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.16.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Blocker
> Labels: drools-tools
> Attachments: Screenshot from 2019-01-02 15-37-21.png, a1 (1).dmn, error.log, server-error.log
>
>
> User is not able to model a DMN model where he declare a Decision service and invoke this Decision Service from other node, because the Decision Service node doesn't allow any incoming nor outgoing connections.
> h2. Acceptance criteria
> - Import attached model *a1*
> - Connect *mood* decision service and *Decision-1* decision node
> - Deploy the model
> - Try to evaluate model via a rest call
> - Check the output json doesn't contain [^error.log]
> - Check the server log doesn't contain [^server-error.log]
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 5 months
[JBoss JIRA] (DROOLS-3465) [DMN Designer] ContextGrid and DecisionTableGrid selectFirstCell() regression
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3465?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3465:
-----------------------------------
Sprint: 2019 Week 02-04, 2018 Week 51-01 (was: 2018 Week 51-01)
> [DMN Designer] ContextGrid and DecisionTableGrid selectFirstCell() regression
> -----------------------------------------------------------------------------
>
> Key: DROOLS-3465
> URL: https://issues.jboss.org/browse/DROOLS-3465
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.15.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
>
> (Programmatic) selection of the "first cell" in both the {{ContextGrid}} and {{DecisionTableGrid}} has regressed. Selection should ignore the "row number" column however changes adding explicit "Row number columns" for the foregoing grids that do not extend {{RowNumberColumn}} have caused the expected behaviour to break.
> h2. Acceptance criteria
> # Create new Decision
> # Set expression to either {{Context}} or {{DecisionTable}}
> # The whole row should not be selected, only one cell.
> # Check other expression types.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 5 months
[JBoss JIRA] (DROOLS-3445) Data type constraints: Date
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3445?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3445:
-----------------------------------
Sprint: 2019 Week 02-04, 2018 Week 51-01 (was: 2018 Week 51-01)
> Data type constraints: Date
> ---------------------------
>
> Key: DROOLS-3445
> URL: https://issues.jboss.org/browse/DROOLS-3445
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> Background
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types tab - as a user I want the ability to define constraints for the following types: Date (Expression, Enumeration, and Range.)
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 5 months
[JBoss JIRA] (DROOLS-3429) Serialization of KiePackages fails when SecurityManager is enabled
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3429?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3429:
-----------------------------------
Sprint: 2018 Week 48-50, 2019 Week 02-04, 2018 Week 51-01 (was: 2018 Week 48-50, 2018 Week 51-01)
> Serialization of KiePackages fails when SecurityManager is enabled
> ------------------------------------------------------------------
>
> Key: DROOLS-3429
> URL: https://issues.jboss.org/browse/DROOLS-3429
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.5.0.Final, 7.15.0.Final
> Environment: Running with IBM JDK 1.8
> Reporter: Marcel Abou Khalil
> Assignee: Mario Fusco
> Priority: Major
>
> Our Drools setup:
> - users write rules in a combination of DSL and Java code
> - rules are compiled
> - packages are stored in a database (rules are seldom changed but often ran)
> This has been working fine but in order to improve security, we've enabled the SecurityManager. This throws an exception while trying to serialize the consequence part of the rule:
> {code:java}
> Caused by: java.io.NotSerializableException: com.redacted.Rule_Events_REDACTED61028857611DefaultConsequenceInvoker
> - field (class "org.drools.core.definitions.rule.impl.RuleImpl$SafeConsequence", name: "delegate", type: "interface org.drools.core.spi.Consequence")
> - object (class "org.drools.core.definitions.rule.impl.RuleImpl$SafeConsequence", org.drools.core.definitions.rule.impl.RuleImpl$SafeConsequence@93071816)
> - writeExternal data
> - object (class "org.drools.core.definitions.rule.impl.RuleImpl", [Rule name=REDACTED, agendaGroup=end, salience=0, no-loop=true])
> - writeExternal data
> - object (class "org.drools.core.rule.JavaDialectRuntimeData", org.drools.core.rule.JavaDialectRuntimeData{...})
> - custom writeObject data (class "java.util.HashMap")
> - object (class "java.util.HashMap", {java=org.drools.core.rule.JavaDialectRuntimeData{...}, mvel=org.drools.core.rule.MVELDialectRuntimeData@b99ea6b2})
> - writeExternal data
> - root object (class "org.drools.core.rule.DialectRuntimeRegistry", org.drools.core.rule.DialectRuntimeRegistry@2d9acae8)
> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1213)
> at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1615)
> at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1576)
> at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1499)
> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1209)
> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:365)
> at org.drools.core.definitions.rule.impl.RuleImpl.writeExternal(RuleImpl.java:180)
> {code}
> Possible cause:
> Class {{RuleImpl}}, method {{writeExternal}} will write out {{null}} if the consequence is of type {{CompiledInvoker}}. But if the SecurityManager is enabled, the method {{wire}} will wrap the Consequence inside a {{SafeConsequence}}. A {{SafeConsequence}}, in contrast to the wrapped consequence is not a {{CompiledInvoker}}, so {{writeExternal}} will attempt to serialize it, instead of just writing {{null}} and fails.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 5 months
[JBoss JIRA] (DROOLS-3425) Unexpected behavior of docks when multiple editors are opened
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3425?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3425:
-----------------------------------
Sprint: 2018 Week 48-50, 2019 Week 02-04, 2018 Week 51-01 (was: 2018 Week 48-50, 2018 Week 51-01)
> Unexpected behavior of docks when multiple editors are opened
> -------------------------------------------------------------
>
> Key: DROOLS-3425
> URL: https://issues.jboss.org/browse/DROOLS-3425
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor, Scenario Simulation and Testing, Stunner
> Reporter: Klara Kufova
> Assignee: Toni Rikkola
> Priority: Critical
> Labels: ScenarioSimulation, drools-tools
> Attachments: screencast-11-12-18.webm, screencast-12-12-18.webm
>
>
> When multiple assets are opened in different editors, their docks incorrectly interfere. After opening two assets in a row, the Business Central freezes with an unexpected error. Closing one asset causes unexpected disappearance of the left panel.
> See the attached screencast for detailed information. After the assets are opened for the first time, everything seems correct. Once the {{.dmn}} file is opened for the second time, the issues start to occur.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 5 months