[JBoss JIRA] (DROOLS-3227) [DMN Designer] Decision table output data type is not stored if decision table is generated according to input data
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3227?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3227:
--------------------------------
Workaround Description: Create Decision table at first and then connect Input data nodes with the decision node.
Workaround: Workaround Exists
> [DMN Designer] Decision table output data type is not stored if decision table is generated according to input data
> -------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3227
> URL: https://issues.jboss.org/browse/DROOLS-3227
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
> Attachments: auto.dmn
>
>
> The decision table output column data type is not stored, if the decision table was generated according to some input data.
> An example of such table is attached [^auto.dmn] . This table was created in steps below:
> - Create new DMN diagram
> - Add an Input Data node : *applicant*
> - Add a Decision node: *applicant score*
> - Connect them
> - Define new data type: *tApplicant*.
> -- lang:string (Constraints: "c", "java")
> -- open source: boolean
> - Set *applicant* node data type as *tApplicant*
> - Set *applicant score* node data type as *number*
> - Open expression editor for *applicant score* node
> - Set its top level expression as Decision Table
> - Save and download DMN model
> - It will be like the attached
> {code:xml}
> <dmn:output id="_E6C7E5E6-45C5-4FC2-A37B-69806046893F" name="output-1" typeRef="string">
> <dmn:outputValues id="_B473BAB4-521D-4FD9-88BC-C28CD497F03A">
> <dmn:text></dmn:text>
> </dmn:outputValues>
> <dmn:defaultOutputEntry id="_85BF133E-380C-4F0E-9E2A-0C5C6493F6B4" typeRef="string">
> <dmn:text></dmn:text>
> </dmn:defaultOutputEntry>
> </dmn:output>
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3227) [DMN Designer] Decision table output data type is not stored if decision table is generated according to input data
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3227?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3227:
--------------------------------
Attachment: auto.dmn
> [DMN Designer] Decision table output data type is not stored if decision table is generated according to input data
> -------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3227
> URL: https://issues.jboss.org/browse/DROOLS-3227
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Blocker
> Labels: drools-tools
> Attachments: auto.dmn
>
>
> Issue spotted during DROOLS-3214, however probably not related.
> If decision table output data type is changed, the change is not reflected in the xml.
> Please follow my steps:
> - Create new DMN diagram
> - Add a decision node
> - Set the decision node top level expression as a decision table
> - Double click on Output header cell
> - Select boolean lets say
> - Save the diagram
> Check the source, there will be still stored string output data type, like below:
> {code:xml}
> <dmn:decisionTable id="_DE6CDA18-99D1-4259-9F6D-825209DF7DE8" typeRef="string" hitPolicy="ANY" preferredOrientation="Rule-as-Row">
> <dmn:input id="_EB7B7C02-4131-468C-B1B1-023C39045B66">
> <dmn:inputExpression id="_C72A9C94-130C-4BA5-A529-49BAE217DDFF" typeRef="string">
> <dmn:text>input-1</dmn:text>
> </dmn:inputExpression>
> <dmn:inputValues id="_1EC58DD6-21EB-4822-A333-581363BC325B">
> <dmn:text></dmn:text>
> </dmn:inputValues>
> </dmn:input>
> <dmn:output id="_81248A6E-0239-404A-B891-C7C0BEE6B501" name="output-1" typeRef="string">
> <dmn:outputValues id="_26301186-9EB2-43E8-B6F8-458361E99B45">
> <dmn:text></dmn:text>
> </dmn:outputValues>
> <dmn:defaultOutputEntry id="_EAC89F66-3B9E-4781-B670-1282975F4F1E" typeRef="string">
> <dmn:text></dmn:text>
> </dmn:defaultOutputEntry>
> </dmn:output>
> <dmn:rule id="_EC0CEE6B-E4D5-4DE2-9EE5-86C955933B4E">
> <dmn:inputEntry id="_91AA6110-0A85-4C95-B0B3-D1B084CB0089">
> <dmn:text>"you are right"</dmn:text>
> </dmn:inputEntry>
> <dmn:outputEntry id="_6FACD1CE-8301-413E-8C77-F04AD71B3C78" typeRef="string">
> <dmn:text>true</dmn:text>
> </dmn:outputEntry>
> </dmn:rule>
> </dmn:decisionTable>
> </dmn:decision>
> {code}
> But the UI is like:
> !Screenshot from 2018-11-01 10-59-08.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3227) [DMN Designer] Decision table output data type is not stored if decision table is generated according to input data
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3227?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3227:
--------------------------------
Priority: Critical (was: Blocker)
> [DMN Designer] Decision table output data type is not stored if decision table is generated according to input data
> -------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3227
> URL: https://issues.jboss.org/browse/DROOLS-3227
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
> Attachments: auto.dmn
>
>
> Issue spotted during DROOLS-3214, however probably not related.
> If decision table output data type is changed, the change is not reflected in the xml.
> Please follow my steps:
> - Create new DMN diagram
> - Add a decision node
> - Set the decision node top level expression as a decision table
> - Double click on Output header cell
> - Select boolean lets say
> - Save the diagram
> Check the source, there will be still stored string output data type, like below:
> {code:xml}
> <dmn:decisionTable id="_DE6CDA18-99D1-4259-9F6D-825209DF7DE8" typeRef="string" hitPolicy="ANY" preferredOrientation="Rule-as-Row">
> <dmn:input id="_EB7B7C02-4131-468C-B1B1-023C39045B66">
> <dmn:inputExpression id="_C72A9C94-130C-4BA5-A529-49BAE217DDFF" typeRef="string">
> <dmn:text>input-1</dmn:text>
> </dmn:inputExpression>
> <dmn:inputValues id="_1EC58DD6-21EB-4822-A333-581363BC325B">
> <dmn:text></dmn:text>
> </dmn:inputValues>
> </dmn:input>
> <dmn:output id="_81248A6E-0239-404A-B891-C7C0BEE6B501" name="output-1" typeRef="string">
> <dmn:outputValues id="_26301186-9EB2-43E8-B6F8-458361E99B45">
> <dmn:text></dmn:text>
> </dmn:outputValues>
> <dmn:defaultOutputEntry id="_EAC89F66-3B9E-4781-B670-1282975F4F1E" typeRef="string">
> <dmn:text></dmn:text>
> </dmn:defaultOutputEntry>
> </dmn:output>
> <dmn:rule id="_EC0CEE6B-E4D5-4DE2-9EE5-86C955933B4E">
> <dmn:inputEntry id="_91AA6110-0A85-4C95-B0B3-D1B084CB0089">
> <dmn:text>"you are right"</dmn:text>
> </dmn:inputEntry>
> <dmn:outputEntry id="_6FACD1CE-8301-413E-8C77-F04AD71B3C78" typeRef="string">
> <dmn:text>true</dmn:text>
> </dmn:outputEntry>
> </dmn:rule>
> </dmn:decisionTable>
> </dmn:decision>
> {code}
> But the UI is like:
> !Screenshot from 2018-11-01 10-59-08.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3227) [DMN Designer] Decision table output data type is not stored if decision table is generated according to input data
by Jozef Marko (Jira)
Jozef Marko created DROOLS-3227:
-----------------------------------
Summary: [DMN Designer] Decision table output data type is not stored if decision table is generated according to input data
Key: DROOLS-3227
URL: https://issues.jboss.org/browse/DROOLS-3227
Project: Drools
Issue Type: Bug
Components: DMN Editor
Affects Versions: 7.14.0.Final
Reporter: Jozef Marko
Assignee: Michael Anstis
Issue spotted during DROOLS-3214, however probably not related.
If decision table output data type is changed, the change is not reflected in the xml.
Please follow my steps:
- Create new DMN diagram
- Add a decision node
- Set the decision node top level expression as a decision table
- Double click on Output header cell
- Select boolean lets say
- Save the diagram
Check the source, there will be still stored string output data type, like below:
{code:xml}
<dmn:decisionTable id="_DE6CDA18-99D1-4259-9F6D-825209DF7DE8" typeRef="string" hitPolicy="ANY" preferredOrientation="Rule-as-Row">
<dmn:input id="_EB7B7C02-4131-468C-B1B1-023C39045B66">
<dmn:inputExpression id="_C72A9C94-130C-4BA5-A529-49BAE217DDFF" typeRef="string">
<dmn:text>input-1</dmn:text>
</dmn:inputExpression>
<dmn:inputValues id="_1EC58DD6-21EB-4822-A333-581363BC325B">
<dmn:text></dmn:text>
</dmn:inputValues>
</dmn:input>
<dmn:output id="_81248A6E-0239-404A-B891-C7C0BEE6B501" name="output-1" typeRef="string">
<dmn:outputValues id="_26301186-9EB2-43E8-B6F8-458361E99B45">
<dmn:text></dmn:text>
</dmn:outputValues>
<dmn:defaultOutputEntry id="_EAC89F66-3B9E-4781-B670-1282975F4F1E" typeRef="string">
<dmn:text></dmn:text>
</dmn:defaultOutputEntry>
</dmn:output>
<dmn:rule id="_EC0CEE6B-E4D5-4DE2-9EE5-86C955933B4E">
<dmn:inputEntry id="_91AA6110-0A85-4C95-B0B3-D1B084CB0089">
<dmn:text>"you are right"</dmn:text>
</dmn:inputEntry>
<dmn:outputEntry id="_6FACD1CE-8301-413E-8C77-F04AD71B3C78" typeRef="string">
<dmn:text>true</dmn:text>
</dmn:outputEntry>
</dmn:rule>
</dmn:decisionTable>
</dmn:decision>
{code}
But the UI is like:
!Screenshot from 2018-11-01 10-59-08.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3225) [DMN Designer] Decision table output data type is not stored
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3225?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3225:
--------------------------------
Attachment: auto.dmn
> [DMN Designer] Decision table output data type is not stored
> ------------------------------------------------------------
>
> Key: DROOLS-3225
> URL: https://issues.jboss.org/browse/DROOLS-3225
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Blocker
> Labels: drools-tools
> Attachments: Screenshot from 2018-11-01 10-59-08.png, Screenshot from 2018-11-01 15-31-19.png, job-interview.dmn
>
>
> Issue spotted during DROOLS-3214, however probably not related.
> If decision table output data type is changed, the change is not reflected in the xml.
> Please follow my steps:
> - Create new DMN diagram
> - Add a decision node
> - Set the decision node top level expression as a decision table
> - Double click on Output header cell
> - Select boolean lets say
> - Save the diagram
> Check the source, there will be still stored string output data type, like below:
> {code:xml}
> <dmn:decisionTable id="_DE6CDA18-99D1-4259-9F6D-825209DF7DE8" typeRef="string" hitPolicy="ANY" preferredOrientation="Rule-as-Row">
> <dmn:input id="_EB7B7C02-4131-468C-B1B1-023C39045B66">
> <dmn:inputExpression id="_C72A9C94-130C-4BA5-A529-49BAE217DDFF" typeRef="string">
> <dmn:text>input-1</dmn:text>
> </dmn:inputExpression>
> <dmn:inputValues id="_1EC58DD6-21EB-4822-A333-581363BC325B">
> <dmn:text></dmn:text>
> </dmn:inputValues>
> </dmn:input>
> <dmn:output id="_81248A6E-0239-404A-B891-C7C0BEE6B501" name="output-1" typeRef="string">
> <dmn:outputValues id="_26301186-9EB2-43E8-B6F8-458361E99B45">
> <dmn:text></dmn:text>
> </dmn:outputValues>
> <dmn:defaultOutputEntry id="_EAC89F66-3B9E-4781-B670-1282975F4F1E" typeRef="string">
> <dmn:text></dmn:text>
> </dmn:defaultOutputEntry>
> </dmn:output>
> <dmn:rule id="_EC0CEE6B-E4D5-4DE2-9EE5-86C955933B4E">
> <dmn:inputEntry id="_91AA6110-0A85-4C95-B0B3-D1B084CB0089">
> <dmn:text>"you are right"</dmn:text>
> </dmn:inputEntry>
> <dmn:outputEntry id="_6FACD1CE-8301-413E-8C77-F04AD71B3C78" typeRef="string">
> <dmn:text>true</dmn:text>
> </dmn:outputEntry>
> </dmn:rule>
> </dmn:decisionTable>
> </dmn:decision>
> {code}
> But the UI is like:
> !Screenshot from 2018-11-01 10-59-08.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3225) [DMN Designer] Decision table output data type is not stored
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3225?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3225:
--------------------------------
Attachment: (was: auto.dmn)
> [DMN Designer] Decision table output data type is not stored
> ------------------------------------------------------------
>
> Key: DROOLS-3225
> URL: https://issues.jboss.org/browse/DROOLS-3225
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Blocker
> Labels: drools-tools
> Attachments: Screenshot from 2018-11-01 10-59-08.png, Screenshot from 2018-11-01 15-31-19.png, job-interview.dmn
>
>
> Issue spotted during DROOLS-3214, however probably not related.
> If decision table output data type is changed, the change is not reflected in the xml.
> Please follow my steps:
> - Create new DMN diagram
> - Add a decision node
> - Set the decision node top level expression as a decision table
> - Double click on Output header cell
> - Select boolean lets say
> - Save the diagram
> Check the source, there will be still stored string output data type, like below:
> {code:xml}
> <dmn:decisionTable id="_DE6CDA18-99D1-4259-9F6D-825209DF7DE8" typeRef="string" hitPolicy="ANY" preferredOrientation="Rule-as-Row">
> <dmn:input id="_EB7B7C02-4131-468C-B1B1-023C39045B66">
> <dmn:inputExpression id="_C72A9C94-130C-4BA5-A529-49BAE217DDFF" typeRef="string">
> <dmn:text>input-1</dmn:text>
> </dmn:inputExpression>
> <dmn:inputValues id="_1EC58DD6-21EB-4822-A333-581363BC325B">
> <dmn:text></dmn:text>
> </dmn:inputValues>
> </dmn:input>
> <dmn:output id="_81248A6E-0239-404A-B891-C7C0BEE6B501" name="output-1" typeRef="string">
> <dmn:outputValues id="_26301186-9EB2-43E8-B6F8-458361E99B45">
> <dmn:text></dmn:text>
> </dmn:outputValues>
> <dmn:defaultOutputEntry id="_EAC89F66-3B9E-4781-B670-1282975F4F1E" typeRef="string">
> <dmn:text></dmn:text>
> </dmn:defaultOutputEntry>
> </dmn:output>
> <dmn:rule id="_EC0CEE6B-E4D5-4DE2-9EE5-86C955933B4E">
> <dmn:inputEntry id="_91AA6110-0A85-4C95-B0B3-D1B084CB0089">
> <dmn:text>"you are right"</dmn:text>
> </dmn:inputEntry>
> <dmn:outputEntry id="_6FACD1CE-8301-413E-8C77-F04AD71B3C78" typeRef="string">
> <dmn:text>true</dmn:text>
> </dmn:outputEntry>
> </dmn:rule>
> </dmn:decisionTable>
> </dmn:decision>
> {code}
> But the UI is like:
> !Screenshot from 2018-11-01 10-59-08.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3193) UX to support selection of multiple data/domain object instances
by Klara Kufova (Jira)
[ https://issues.jboss.org/browse/DROOLS-3193?page=com.atlassian.jira.plugi... ]
Klara Kufova commented on DROOLS-3193:
--------------------------------------
[~uxdlc], don't worry about it, Liz, I will move this issue directly to the next sprint. Thanks for scheduling the meeting!
> UX to support selection of multiple data/domain object instances
> ----------------------------------------------------------------
>
> Key: DROOLS-3193
> URL: https://issues.jboss.org/browse/DROOLS-3193
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
> Attachments: Screen Shot 2018-10-30 at 10.50.55 AM.png
>
>
> As user I want to use multiple instances of the same data object in my test scenarios (multiple instances support) (i.e. scenario with more than one instance of “Person”...), so that I can create a test scenario.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3220) [DMN Designer] [Edge] Unable to edit context cell
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3220?page=com.atlassian.jira.plugi... ]
Jozef Marko closed DROOLS-3220.
-------------------------------
Resolution: Cannot Reproduce
Tried with latest bits, seems working fine.
> [DMN Designer] [Edge] Unable to edit context cell
> -------------------------------------------------
>
> Key: DROOLS-3220
> URL: https://issues.jboss.org/browse/DROOLS-3220
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Environment: Windows, Edge browser
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Priority: Blocker
> Labels: drools-tools
> Attachments: drools-3220.gif
>
>
> User is unable to invoke edit mode for context cells. Other expression types seems to work fine.
> Spotted during DROOLS-3214 review, however don't think it is related.
> h2. Acceptance test
> Invoke edit mode of regular cell
> - Literal
> - Dec. Table
> - Function
> - Relation
> - Invocation
> - Context
> Invoke edit mode of header cell - where applicable
> - Literal
> - Dec. Table
> - Function
> - Relation
> - Invocation
> - Context
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFCORE-4195) CLI/Admin Console does not prompt for a reload after adding a new server-group to server-scoped-roles.
by Chao Wang (Jira)
[ https://issues.jboss.org/browse/WFCORE-4195?page=com.atlassian.jira.plugi... ]
Chao Wang commented on WFCORE-4195:
-----------------------------------
User {{test}} can not see the new server group without a reload operation because [ServerGroupScopedRoleWriteAttributeHandler.applyUpdateToRuntime()|https:/...] (where it applies change to constraint) is not executed for write operation:
{code:java}
/core-service=management/access=authorization/server-group-scoped-role=maintainer-scope-role:write-attribute(name=server-groups, value=[main-server-group,new-server-group]
{code}
It's supposed to be called from a Runtime step handler in AbstractWriteAttributeHandler.execute(), but it's skipped at [if (requiresRuntime(context))|https://github.com/wildfly/wildfly-core/blob/7....] check.
[AbstractOperationContext.isHostCapableAddress()|https://github.com/wildfl...] returns false as following activeStep.address does not match the address format _The process is a HC, and the address of the operation is a subsystem in the host model or a child thereof_
{code:java}
activeStep.address.size() >= 2 && activeStep.address.getElement(0).getKey().equals(HOST) && activeStep.address.getElement(1).getKey().equals(SUBSYSTEM)
{code}
{code:xml}
[
("core-service" => "management"),
("access" => "authorization"),
("server-group-scoped-role" => "maintainer-scope-role")
]
{code}
I'd like to confirm the correct behavior with [~brian.stansberry] first. If not requiring a reload is preferable option as said in BZ, it seems that ServerGroupScopedRoleWriteAttributeHandler should override execute() and apply change to constraint without matching the activeStep.address format above ?
> CLI/Admin Console does not prompt for a reload after adding a new server-group to server-scoped-roles.
> ------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-4195
> URL: https://issues.jboss.org/browse/WFCORE-4195
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Affects Versions: 7.0.0.Alpha4
> Reporter: Chao Wang
> Assignee: Chao Wang
> Priority: Minor
>
> CLI/Admin Console does not prompt for a reload after adding a new server-group to server-scoped-roles.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month