[JBoss JIRA] (DROOLS-3185) [DMN Designer] Change Literal Expression to Decision Table
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3185?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3185:
--------------------------------
Description:
When user changes Decision node top level expression from literal expression to decision table, that decision table misses InputClause columns.
h2. Manual Acceptance Test
Check steps to reproduce, while InputData node has data type
- Built in type
- Custom type that has constraint
- Custom type that is collection
- Custom type that is recursive
- Multiple InputData nodes
- Multiple input nodes, mixed InputData and Decision
was:When user changes Decision node top level expression from literal expression to decision table, that decision table misses InputClause columns.
> [DMN Designer] Change Literal Expression to Decision Table
> ----------------------------------------------------------
>
> Key: DROOLS-3185
> URL: https://issues.jboss.org/browse/DROOLS-3185
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Attachments: Screenshot from 2018-10-25 14-40-06.png, screenshot-1.png
>
>
> When user changes Decision node top level expression from literal expression to decision table, that decision table misses InputClause columns.
> h2. Manual Acceptance Test
> Check steps to reproduce, while InputData node has data type
> - Built in type
> - Custom type that has constraint
> - Custom type that is collection
> - Custom type that is recursive
> - Multiple InputData nodes
> - Multiple input nodes, mixed InputData and Decision
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3141) [DMN Designer] Decision Table: Add additional Properties to drill-down
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3141?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-3141:
-------------------------------------
I approved PR as the issues should gone with JBPM-7166.
> [DMN Designer] Decision Table: Add additional Properties to drill-down
> ----------------------------------------------------------------------
>
> Key: DROOLS-3141
> URL: https://issues.jboss.org/browse/DROOLS-3141
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
> Attachments: a1.dmn
>
>
> The Properties Panel currently shows properties for Stunner-level "graph" components.
> *Further to DROOLS-2804, that added the generic support for "drill down" and {{ExpressionLanguage}} on {{LiteralExpression}}, this JIRA is to add support for the remaining properties that should be rendered when a component is "drilled down".*
> h2. Properties on the Grid Level
> The selection on the grid level should show the properties below. Please notice that selection of multiple cells, rows or columns should show empty properties panel.
> (everything should have ID, Description properties. Components which inherit from "NamedElement" should also have Name property)
> h3. Decision Table
> ||Selected item||Properties panel items||type|| ||
> |Row|n/a|n/a|n/a|
> |Input Column|Constraints|Text field|(/)|
> |Output Column|Output values|Unary tests|(/)|
> |Output Column|Default Output|expression|(/)|
> |Cell|ExpressionLanguage|URI|(/)|
> h2. Manual Acceptance Test
> - Switching between DRG and Grid editor, check proper fields shown
> - Switching between rows, columns, cells in Grid editor, check proper fields
> -- In same expression kind
> -- Across different expression kinds
> - Clear expression kind
> - Read only mode - older asset version
> - All Grid specific properties saved
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFCORE-4186) RBAC classification resources should not store default-xxx attribute values in the DMR model
by Brian Stansberry (Jira)
Brian Stansberry created WFCORE-4186:
----------------------------------------
Summary: RBAC classification resources should not store default-xxx attribute values in the DMR model
Key: WFCORE-4186
URL: https://issues.jboss.org/browse/WFCORE-4186
Project: WildFly Core
Issue Type: Bug
Components: Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
The RBAC classification resource are storing the values of the relevant default-requires-xxx attributes in the DMR model even though those are runtime-only attributes. The DMR value is unused in read-resource/read-attribute because the read handlers for the attribute don't read from DMR.
Unless WFCORE-4185 is fixed these will get propogated to slave HCs when they connect though.
Cleaning this up helps resolve WFCORE-4183 by removing irrelevant data that confuses domain mode transformer tests.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFCORE-4185) ReadMasterDomainModelUtil is including runtime-only attributes in what it provides
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFCORE-4185?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-4185:
-------------------------------------
Description:
Some resources (e.g. WildFly's transaction subsystem's log-store resource) may use the Resource tree DMR model node to store non-persistent, runtime-only state. If this is done, any such value should not be propagated to a remote HC.
(This is actually very unlikely to happen in practice as runtime-only attributes are not typically used in the domain model. It does affect transformer testing though as transformer tests usually don't take care to inform their extension that they are running in an HC.)
Cleaning this up helps resolve WFCORE-4183 by removing irrelevant data that confuses domain mode transformer tests.
was:
Some resource (e.g. WildFly's transaction subsystem's log-store resource) may use the Resource tree DMR model node to store non-persistent, runtime-only state. If this is done, any such value should not be propagated to a remote HC.
(This is actually very unlikely to happen in practice as runtime-only attributes are not typically used in the domain model. It does affect transformer testing though as transformer tests usually don't take care to inform their extension that they are running in an HC.)
> ReadMasterDomainModelUtil is including runtime-only attributes in what it provides
> ----------------------------------------------------------------------------------
>
> Key: WFCORE-4185
> URL: https://issues.jboss.org/browse/WFCORE-4185
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Minor
>
> Some resources (e.g. WildFly's transaction subsystem's log-store resource) may use the Resource tree DMR model node to store non-persistent, runtime-only state. If this is done, any such value should not be propagated to a remote HC.
> (This is actually very unlikely to happen in practice as runtime-only attributes are not typically used in the domain model. It does affect transformer testing though as transformer tests usually don't take care to inform their extension that they are running in an HC.)
> Cleaning this up helps resolve WFCORE-4183 by removing irrelevant data that confuses domain mode transformer tests.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFCORE-4185) ReadMasterDomainModelUtil is including runtime-only attributes in what it provides
by Brian Stansberry (Jira)
Brian Stansberry created WFCORE-4185:
----------------------------------------
Summary: ReadMasterDomainModelUtil is including runtime-only attributes in what it provides
Key: WFCORE-4185
URL: https://issues.jboss.org/browse/WFCORE-4185
Project: WildFly Core
Issue Type: Bug
Components: Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Some resource (e.g. WildFly's transaction subsystem's log-store resource) may use the Resource tree DMR model node to store non-persistent, runtime-only state. If this is done, any such value should not be propagated to a remote HC.
(This is actually very unlikely to happen in practice as runtime-only attributes are not typically used in the domain model. It does affect transformer testing though as transformer tests usually don't take care to inform their extension that they are running in an HC.)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFCORE-4184) ModelTestUtils.trimUndefinedChildren loses track of what object is undefined
by Brian Stansberry (Jira)
Brian Stansberry created WFCORE-4184:
----------------------------------------
Summary: ModelTestUtils.trimUndefinedChildren loses track of what object is undefined
Key: WFCORE-4184
URL: https://issues.jboss.org/browse/WFCORE-4184
Project: WildFly Core
Issue Type: Bug
Components: Management, Test Suite
Reporter: Brian Stansberry
Assignee: Brian Stansberry
ModelTestUtils.trimUndefinedChildren uses an 'undefined' var to track whether all fields in an ModelType.OBJECT node are undefined. But it does not reset the var before moving on to the next object, so the results from one node pollute the processing of the next.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months