[JBoss JIRA] (DROOLS-3259) [DMN Designer] `inputData` and `variable` must have the same name value
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3259?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-3259:
-------------------------------------
Can confirm is fixed by the linked PR.
> [DMN Designer] `inputData` and `variable` must have the same name value
> -----------------------------------------------------------------------
>
> Key: DROOLS-3259
> URL: https://issues.jboss.org/browse/DROOLS-3259
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Blocker
> Labels: drools-tools
> Attachments: diagram.png, dtable.png
>
>
> When the user persists the following diagram:
> !diagram.png|thumbnail!
> ..with the following Decision Table:
> !dtable.png|thumbnail!
> ..the {{inputData}} and {{variable}} tags don't have the same {{name}} value in the attribute {{name}}, see:
> {quote}<dmn:inputData id="_67412B2F-A661-48C6-971C-6E184A519592" name="Country">
> <dmn:variable id="_8F4476AB-1BEB-4FDB-8192-73BB0A520236" name="" typeRef="string"></dmn:variable>{quote}
> The expected behaviour is this:
> {quote}<dmn:inputData id="_67412B2F-A661-48C6-971C-6E184A519592" name="Country">
> <dmn:variable id="_8F4476AB-1BEB-4FDB-8192-73BB0A520236" name="Country" typeRef="string"></dmn:variable>{quote}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3250) [DMN Designer] Information Item name is empty by default
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3250?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-3250:
-------------------------------------
Can confirm is fixed by the linked PR.
> [DMN Designer] Information Item name is empty by default
> --------------------------------------------------------
>
> Key: DROOLS-3250
> URL: https://issues.jboss.org/browse/DROOLS-3250
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Carreiro
> Priority: Blocker
> Labels: drools-tools
>
> The properties of decision has two sections with *Name* property. One general *Decision Name* and one *Information Item Name*.
> The second *Information Item Name* reflects in <variable/> tag of the backing xml file. Its value important for the runtime.
> I think we should solve this issue doing two actions:
> - Make *Information Item Name* readonly
> - Set *Information Item Name* automatically according to *Decision Name*
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3266) [DMN Designer] Remove some properties from the Properties Panel
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3266?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-3266:
-------------------------------------
Can confirm is fixed by linked PR.
> [DMN Designer] Remove some properties from the Properties Panel
> ---------------------------------------------------------------
>
> Key: DROOLS-3266
> URL: https://issues.jboss.org/browse/DROOLS-3266
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Blocker
> Labels: drools-tools
> Attachments: decision-table-output-header-selected.png, input-selected.png, input.png
>
>
> Remove the properties highlighted in red from the Properties Panel:
> I) When an input node is selected
> !input-selected.png|thumbnail!
> II) When a decision table header output is selected
> !decision-table-output-header-selected.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11316) Remove unused dependencies from org.jberet.jberet-core
by Yeray Borges (Jira)
Yeray Borges created WFLY-11316:
-----------------------------------
Summary: Remove unused dependencies from org.jberet.jberet-core
Key: WFLY-11316
URL: https://issues.jboss.org/browse/WFLY-11316
Project: WildFly
Issue Type: Bug
Components: Batch
Reporter: Yeray Borges
Assignee: Yeray Borges
Analysis of org.jberet.jberet-core shows:
* org.jboss.jts is unused
* jberet only uses javax.enterprise.api, javax.inject.api, javax.annotation.api and javax.batch.api from javaee.api, maybe we could reduce the final size removing javaee.api and add only the required modules.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11315) Remove unused dependencies from org.jboss.as.jpa
by Yeray Borges (Jira)
Yeray Borges created WFLY-11315:
-----------------------------------
Summary: Remove unused dependencies from org.jboss.as.jpa
Key: WFLY-11315
URL: https://issues.jboss.org/browse/WFLY-11315
Project: WildFly
Issue Type: Bug
Components: JPA / Hibernate
Reporter: Yeray Borges
Assignee: Yeray Borges
This issue folows up WFLY-11279. There are additional dependencies that can be removed from org.jboss.as.jpa.
The additional dependencies are:
* javax.annotation.api
* javax.resource.api
* javax.servlet.api
* org.jboss.common-beans
* org.jboss.threads
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3291) [DMN Designer] Allowed Values just for built in types
by Jozef Marko (Jira)
Jozef Marko created DROOLS-3291:
-----------------------------------
Summary: [DMN Designer] Allowed Values just for built in types
Key: DROOLS-3291
URL: https://issues.jboss.org/browse/DROOLS-3291
Project: Drools
Issue Type: Enhancement
Components: DMN Editor
Reporter: Jozef Marko
Assignee: Michael Anstis
Citing form spec:
{code}
ItemDefinition element SHALL be defined using only one of the alternative ways:
- reference to a built-in or imported typeRef, possibly restricted with allowedValues;
- composition of ItemDefinition elements.
{code}
Because of the above, I think we should hide constraint component for ItemDefinitions of type structure.
h2. Manual Acceptance test
- User is not able to add constraint (allowedValues) for item definition of Structure type
-- Create form scratch
-- Change existing that already had constraints
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3269) [DMN Designer] Context: Default can be any expression type
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3269?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-3269:
-------------------------------------
[~manstis] give me some time please, started anotehr pr review, will get back to you, hopefully today.
> [DMN Designer] Context: Default can be any expression type
> ----------------------------------------------------------
>
> Key: DROOLS-3269
> URL: https://issues.jboss.org/browse/DROOLS-3269
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Blocker
> Labels: drools-tools
> Attachments: Qclt6jQn.dmn, Screenshot from 2018-11-09 08-16-34.png
>
>
> The "default" box can be any type of expression, specially decision tables and nested contexts.
> Furthermore the "default" box on contexts is optional. We must provide a way for it to be removed. When support for _any_ type of expression we'll be able to have a {{null}} value for the expression so this should fix itself.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3162) Resolve Table (grid) width for Scenario
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-3162?page=com.atlassian.jira.plugi... ]
Daniele Zonca updated DROOLS-3162:
----------------------------------
Story Points: 5
> Resolve Table (grid) width for Scenario
> ---------------------------------------
>
> Key: DROOLS-3162
> URL: https://issues.jboss.org/browse/DROOLS-3162
> Project: Drools
> Issue Type: Sub-task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Daniele Zonca
> Priority: Major
> Labels: UX-CSS
>
> Table does not extend to the full width of the canvas area, which in the default view creates a gap between the table and the right panel. This could affect usability as the visual association and proximity between the selected cell and the input area (in the right panel) is reduced.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months