[JBoss JIRA] (DROOLS-2848) Make the Verifier Web Worker connector reusable for different V&V types
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2848?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-2848:
-----------------------------------
Sprint: 2018 Week 33-35, 2018 Week 36-38 (was: 2018 Week 33-35)
> Make the Verifier Web Worker connector reusable for different V&V types
> -----------------------------------------------------------------------
>
> Key: DROOLS-2848
> URL: https://issues.jboss.org/browse/DROOLS-2848
> Project: Drools
> Issue Type: Task
> Components: DMN Editor, Guided Decision Table Editor, verifier
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Labels: drools-tools
>
> Actions needed for this:
> * Rename DTable verifier to dtableverifier
> * Make a register for web workers that finds the right backend providers with CDI
> * Create webworker service into kie-wb-common-verifier-api that delivers the correct web worker files based on the module name.
> * Make the drools-wb-verifier-webworker provide the web worker so the the web worker service picks it up.
> * Move the actual web worker connection codes from dtables module to kie-wb-common-api and make them generic
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 8 months
[JBoss JIRA] (DROOLS-2563) [DMN Editor] Add support to define data-types
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2563?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-2563:
-----------------------------------
Sprint: 2018 Week 27-29, 2018 Week 30-32, 2018 Week 33-35, 2018 Week 36-38 (was: 2018 Week 27-29, 2018 Week 30-32, 2018 Week 33-35)
> [DMN Editor] Add support to define data-types
> ---------------------------------------------
>
> Key: DROOLS-2563
> URL: https://issues.jboss.org/browse/DROOLS-2563
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Guilherme Carreiro
> Labels: drools-tools
>
> As a practitioner, I want to be able to define Data Types in the UI, so that when the DMN engine evaluates a decision table input/output it will check if the type of the value matches the specified type.
> Verification conditions:
> Support added for the User to define data-types ({{ItemDefinition}}).
> This may become a top-level task when I get to work on it; as the requirement is quite large and encompasses nested data-types (a whole new grid will be required); and definition of enums, constrains on values etc.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 8 months
[JBoss JIRA] (DROOLS-2535) Standalone Authoring - Project Explorer should not show up with StandaloneAuthoringPerspective
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2535?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-2535:
-----------------------------------
Sprint: 2018 Week 17-18, 2018 Week 19-22, 2018 Week 23-24, 2018 Week 25-26, 2018 Week 27-29, 2018 Week 30-32, 2018 Week 33-35, 2018 Week 36-38 (was: 2018 Week 17-18, 2018 Week 19-22, 2018 Week 23-24, 2018 Week 25-26, 2018 Week 27-29, 2018 Week 30-32, 2018 Week 33-35)
> Standalone Authoring - Project Explorer should not show up with StandaloneAuthoringPerspective
> ----------------------------------------------------------------------------------------------
>
> Key: DROOLS-2535
> URL: https://issues.jboss.org/browse/DROOLS-2535
> Project: Drools
> Issue Type: Bug
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
>
> No need to have the ProjectExplorer when your goal is to edit a single asset. If you want to edit multiple you want the LibraryPerspective.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 8 months
[JBoss JIRA] (DROOLS-2823) FEEL Parser: `not` breaks with `list contains`
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2823?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-2823:
-----------------------------------
Sprint: 2018 Week 30-32, 2018 Week 33-35, 2018 Week 36-38 (was: 2018 Week 30-32, 2018 Week 33-35)
> FEEL Parser: `not` breaks with `list contains`
> -----------------------------------------------
>
> Key: DROOLS-2823
> URL: https://issues.jboss.org/browse/DROOLS-2823
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Reporter: Edoardo Vacchi
> Assignee: Edoardo Vacchi
>
> *list contains([1,2,3,4,5,6], 3)* returns true
> *not(list contains([1,2,3,4,5,6], 3))* returns “list contains([1,2,3,4,5,6], 3)”, it should return false
> Most likely related to an issue with the parse tree branches
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 8 months
[JBoss JIRA] (DROOLS-2794) [DMN Designer] Data-types: Support usage in grids
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2794?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-2794:
-----------------------------------
Sprint: 2018 Week 30-32, 2018 Week 33-35, 2018 Week 36-38 (was: 2018 Week 30-32, 2018 Week 33-35)
> [DMN Designer] Data-types: Support usage in grids
> -------------------------------------------------
>
> Key: DROOLS-2794
> URL: https://issues.jboss.org/browse/DROOLS-2794
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Affects Versions: 7.9.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> Listing requirements here; and then possibly move this to an EPIC and add smaller tasks.
> *_General_*
> - (x) {{<< Back to XXX}} does not update if name changed in Properties panel
> - (x) "TypeRef" on Properties panel should show "Output Data Type"
> *_Literal Expression_*
> - (x) Grid header _could_ show Output Data Type
> - (/) Editing Output Data Type is possible via Properties panel
> - (x) Update header when Output Data Type is changed via Properties panel
> *_Decision Table_*
> - (x) Grid header _could_ show Output Data Type
> - (/) Editing Output Data Type is possible via Properties panel
> - (x) Hide Output Data Type in header when there are multiple {{OutputClause}} columns
> - (x) {{InputClause}} columns header should show Input Data Type
> - (x) {{InputClause}} columns should support changing the Input Data Type
> - (x) {{OutputClause}} columns header should show Output Data Type
> - (x) {{OutputClause}} columns should support changing the Output Data Type
> *_Context_*
> - (x) Grid header _could_ show Output Data Type (for Decision/BKM)
> - (/) Editing Output Data Type (for Decision/BKM) is possible via Properties panel
> - (x) {{ContextEntry}} should show Output Data Type (for {{ContextEntry}})
> - (x) {{ContextEntry}} should support changing the Output Data Type (for {{ContextEntry}})
> *_Relation_*
> - (x) Grid header _could_ show Output Data Type
> - (/) Editing Output Data Type is possible via Properties panel
> - (x) {{InformationItem}} column should show Input Data Type
> - (x) {{InformationItem}} column should support changing Input Data Type
> *_Invocation_*
> - (x) Grid header _could_ show Output Data Type
> - (/) Editing Output Data Type is possible via Properties panel
> *_Function_*
> - (x) Grid header _could_ show Output Data Type
> - (/) Editing Output Data Type is possible via Properties panel
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 8 months
[JBoss JIRA] (DROOLS-2777) Guided Decision Table is changing date field value based on the timezone
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2777?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-2777:
-----------------------------------
Sprint: 2018 Week 30-32, 2018 Week 33-35, 2018 Week 36-38 (was: 2018 Week 30-32, 2018 Week 33-35)
> Guided Decision Table is changing date field value based on the timezone
> ------------------------------------------------------------------------
>
> Key: DROOLS-2777
> URL: https://issues.jboss.org/browse/DROOLS-2777
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor
> Reporter: Michael Anstis
> Assignee: Guilherme Carreiro
> Labels: drools-tools
>
> If I set a Date Field in Guided Decision Table, then change the timezone, restart the server, log in again, the Date Field has *different* value
> Expected: decision-central should never attempt to change the rules automatically without user's knowledge
> h3. Acceptance test
> - Check opening of old asset, created before this change (/)
> - Run server on linux machine (timezone a)
> -- run host on win machine (timezone b) and create [#Assets] (/)
> -- run host on win machine (timezone c) and check [#Assets] (/)
> h4. Assets
> - guided template
> - guided rule
> - guided table simple column
> - guided table brl column
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 8 months