[JBoss JIRA] (DROOLS-3216) Async dependencies resolution or add loading indicator during scesim creation
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-3216?page=com.atlassian.jira.plugi... ]
Daniele Zonca closed DROOLS-3216.
---------------------------------
Resolution: Done
> Async dependencies resolution or add loading indicator during scesim creation
> -----------------------------------------------------------------------------
>
> Key: DROOLS-3216
> URL: https://issues.jboss.org/browse/DROOLS-3216
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Daniele Zonca
> Priority: Major
> Labels: ScenarioSimulation
>
> When user create the first scesim file in the project, the system creates the JUnit activator file and it adds the needed dependencies.
> After that the system takes several seconds (5-6) to retrieve all the dependencies.
> During this time the editor still blank without any indicator or information to the user about what is going on.
> This happens only for the first scesim creation in the project
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (DROOLS-1958) [DMN Editor] Support use of imported models (7.4)
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-1958?page=com.atlassian.jira.plugi... ]
Jozef Marko resolved DROOLS-1958.
---------------------------------
Fix Version/s: 7.23.0.Final
Resolution: Done
> [DMN Editor] Support use of imported models (7.4)
> -------------------------------------------------
>
> Key: DROOLS-1958
> URL: https://issues.jboss.org/browse/DROOLS-1958
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Reporter: Jozef Marko
> Assignee: Guilherme Gomes
> Priority: Critical
> Labels: drools-tools, reported-by-qe
> Fix For: 7.23.0.Final
>
>
> DMN supports referencing other DMN files, for reusing Data Types and nodes (Decisions, Input Data, BKMs, etc).
> This is an umbrella for all JIRAs (target to 7.4) related to the Included Models feature.
> It comprehends:
> - Supporting the use of _included_ data-types;
> - Supporting the use of _included_ nodes (their properties and their boxed expressions).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (DROOLS-3480) [DMN Designer] Improve the Data Types support (7.4)
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3480?page=com.atlassian.jira.plugi... ]
Jozef Marko resolved DROOLS-3480.
---------------------------------
Fix Version/s: 7.23.0.Final
Resolution: Done
> [DMN Designer] Improve the Data Types support (7.4)
> ---------------------------------------------------
>
> Key: DROOLS-3480
> URL: https://issues.jboss.org/browse/DROOLS-3480
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
> Fix For: 7.23.0.Final
>
>
> 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.12.1#712002)
5 years, 7 months
[JBoss JIRA] (DROOLS-4086) [GSS-RFE] Search feature in GDST
by Yevgeniy Fomin (Jira)
[ https://issues.jboss.org/browse/DROOLS-4086?page=com.atlassian.jira.plugi... ]
Yevgeniy Fomin commented on DROOLS-4086:
----------------------------------------
Hi [~manstis] I assigned on you according on components in this Epic
> [GSS-RFE] Search feature in GDST
> --------------------------------
>
> Key: DROOLS-4086
> URL: https://issues.jboss.org/browse/DROOLS-4086
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Affects Versions: 7.23.0.Final
> Reporter: Yevgeniy Fomin
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Attachments: Example.png, Screen Shot 2019-05-30 at 5.14.30 PM.png
>
>
> This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation.
> h1. Requirement
> - The user would like to have additional search for text in *Guided Decision Table* and *Decision Model and Notation (DMN)* editor because standard browser search not allows to do it.
> - We may add auto-suggestion mechanism
> - Do we need search history?
> - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
> - The example text in the input field disappears when you enter the first character, and appears again, if the input field is empty.
> h1. UX design
> - Add magnifying-glass icon.
> - Search-box can be popup window after clicking on icon or just pop field
> - The simple way is just create search inside of "Expression editor" or we can make search from "Graph editor" which return result from both "Expression editor" and "Graph editor" as a list, so it may looks as search we do in DMN data types tab. Also we can make separate search for both.
> h1. Documentation
> - Replace picture of GDT and DMN editor where they become obsolete
> h1. Acceptance test
> - Enter to large amount of data in search box
> - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
> - Searching for non-existing result
> - Result appearing once
> - Result appearing multiple times
> - Set of inputs:
> *- A-Z
> *- a-z
> *- 0-9
> *- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +
> *- Blank spaces
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (DROOLS-4086) [GSS-RFE] Search feature in GDST
by Yevgeniy Fomin (Jira)
[ https://issues.jboss.org/browse/DROOLS-4086?page=com.atlassian.jira.plugi... ]
Yevgeniy Fomin reassigned DROOLS-4086:
--------------------------------------
Assignee: Michael Anstis (was: Yevgeniy Fomin)
> [GSS-RFE] Search feature in GDST
> --------------------------------
>
> Key: DROOLS-4086
> URL: https://issues.jboss.org/browse/DROOLS-4086
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Affects Versions: 7.23.0.Final
> Reporter: Yevgeniy Fomin
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Attachments: Example.png, Screen Shot 2019-05-30 at 5.14.30 PM.png
>
>
> This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation.
> h1. Requirement
> - The user would like to have additional search for text in *Guided Decision Table* and *Decision Model and Notation (DMN)* editor because standard browser search not allows to do it.
> - We may add auto-suggestion mechanism
> - Do we need search history?
> - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
> - The example text in the input field disappears when you enter the first character, and appears again, if the input field is empty.
> h1. UX design
> - Add magnifying-glass icon.
> - Search-box can be popup window after clicking on icon or just pop field
> - The simple way is just create search inside of "Expression editor" or we can make search from "Graph editor" which return result from both "Expression editor" and "Graph editor" as a list, so it may looks as search we do in DMN data types tab. Also we can make separate search for both.
> h1. Documentation
> - Replace picture of GDT and DMN editor where they become obsolete
> h1. Acceptance test
> - Enter to large amount of data in search box
> - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
> - Searching for non-existing result
> - Result appearing once
> - Result appearing multiple times
> - Set of inputs:
> *- A-Z
> *- a-z
> *- 0-9
> *- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +
> *- Blank spaces
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (DROOLS-4086) [GSS-RFE] Search feature in GDST
by Yevgeniy Fomin (Jira)
[ https://issues.jboss.org/browse/DROOLS-4086?page=com.atlassian.jira.plugi... ]
Yevgeniy Fomin updated DROOLS-4086:
-----------------------------------
Description:
This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation.
h1. Requirement
- The user would like to have additional search for text in *Guided Decision Table* and *Decision Model and Notation (DMN)* editor because standard browser search not allows to do it.
- We may add auto-suggestion mechanism
- Do we need search history?
- Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
- The example text in the input field disappears when you enter the first character, and appears again, if the input field is empty.
h1. UX design
- Add magnifying-glass icon.
- Search-box can be popup window after clicking on icon or just pop field
- The simple way is just create search inside of "Expression editor" or we can make search from "Graph editor" which return result from both "Expression editor" and "Graph editor" as a list, so it may looks as search we do in DMN data types tab. Also we can make separate search for both.
h1. Documentation
- Replace picture of GDT and DMN editor where they become obsolete
h1. Acceptance test
- Enter to large amount of data in search box
- Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
- Searching for non-existing result
- Result appearing once
- Result appearing multiple times
- Set of inputs:
*- A-Z
*- a-z
*- 0-9
*- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +
*- Blank spaces
was:
This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation.
h1. Requirement
- The user would like to have additional search for text in *Guided Decision Table* and *Decision Model and Notation (DMN)* editor because standard browser search not allows to do it.
- We may add auto-suggestion mechanism
- Do we need search history?
- Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
- The example text in the input field disappears when you enter the first character, and appears again, if the input field is empty.
h1. UX design
- Add magnifying-glass icon.
- Search-box can be popup window after clicking on icon or just pop field
- The simple way is just create search inside of "Expression editor" or we can make search from "Graph editor" which return result from both "Expression editor" and "Graph editor" as a list, so it may looks as search we do in DMN data types tab. Also we can make separate search for both.
h1. Documentation
- Replace picture of GDT and DMN editor where they become obsolete
h1. Acceptance test
- Enter to large amount of data in search box
- Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
- Set of inputs:
*- A-Z
*- a-z
*- 0-9
*- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +
*- Blank spaces
*-
> [GSS-RFE] Search feature in GDST
> --------------------------------
>
> Key: DROOLS-4086
> URL: https://issues.jboss.org/browse/DROOLS-4086
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Affects Versions: 7.23.0.Final
> Reporter: Yevgeniy Fomin
> Assignee: Yevgeniy Fomin
> Priority: Major
> Labels: drools-tools
> Attachments: Example.png, Screen Shot 2019-05-30 at 5.14.30 PM.png
>
>
> This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation.
> h1. Requirement
> - The user would like to have additional search for text in *Guided Decision Table* and *Decision Model and Notation (DMN)* editor because standard browser search not allows to do it.
> - We may add auto-suggestion mechanism
> - Do we need search history?
> - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
> - The example text in the input field disappears when you enter the first character, and appears again, if the input field is empty.
> h1. UX design
> - Add magnifying-glass icon.
> - Search-box can be popup window after clicking on icon or just pop field
> - The simple way is just create search inside of "Expression editor" or we can make search from "Graph editor" which return result from both "Expression editor" and "Graph editor" as a list, so it may looks as search we do in DMN data types tab. Also we can make separate search for both.
> h1. Documentation
> - Replace picture of GDT and DMN editor where they become obsolete
> h1. Acceptance test
> - Enter to large amount of data in search box
> - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
> - Searching for non-existing result
> - Result appearing once
> - Result appearing multiple times
> - Set of inputs:
> *- A-Z
> *- a-z
> *- 0-9
> *- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +
> *- Blank spaces
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (DROOLS-4086) [GSS-RFE] Search feature in GDST
by Yevgeniy Fomin (Jira)
[ https://issues.jboss.org/browse/DROOLS-4086?page=com.atlassian.jira.plugi... ]
Yevgeniy Fomin updated DROOLS-4086:
-----------------------------------
Description:
This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation.
h1. Requirement
- The user would like to have additional search for text in *Guided Decision Table* and *Decision Model and Notation (DMN)* editor because standard browser search not allows to do it.
- We may add auto-suggestion mechanism
- Do we need search history?
- Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
- The example text in the input field disappears when you enter the first character, and appears again, if the input field is empty.
h1. UX design
- Add magnifying-glass icon.
- Search-box can be popup window after clicking on icon or just pop field
- The simple way is just create search inside of "Expression editor" or we can make search from "Graph editor" which return result from both "Expression editor" and "Graph editor" as a list, so it may looks as search we do in DMN data types tab. Also we can make separate search for both.
h1. Documentation
- Replace picture of GDT and DMN editor where they become obsolete
h1. Acceptance test
- Enter to large amount of data in search box
- Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
- Set of inputs:
*- A-Z
*- a-z
*- 0-9
*- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +
*- Blank spaces
*-
was:
This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation.
h1. Requirement
- The user would like to have additional search for text in *Guided Decision Table* and *Decision Model and Notation (DMN)* editor because standard browser search not allows to do it.
- We may add auto-suggestion mechanism
- Do we need search history?
- Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
- The example text in the input field disappears when you enter the first character, and appears again, if the input field is empty.
h1. UX design
- Add magnifying-glass icon.
- Search-box can be popup window after clicking on icon or just pop field
- The simple way is just create search inside of "Expression editor" or we can make search from "Graph editor" which return result from both "Expression editor" and "Graph editor" as a list, so it may looks as search we do in DMN data types tab. Also we can make separate search for both.
h1. Documentation
- Replace picture of GDT and DMN editor where they become obsolete
h1. Acceptance test
- Enter to large amount of data in search box
- Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
- Set of inputs:
*- A-Z
*- a-z
*- 0-9
*- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +
*- Blank spaces
> [GSS-RFE] Search feature in GDST
> --------------------------------
>
> Key: DROOLS-4086
> URL: https://issues.jboss.org/browse/DROOLS-4086
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Affects Versions: 7.23.0.Final
> Reporter: Yevgeniy Fomin
> Assignee: Yevgeniy Fomin
> Priority: Major
> Labels: drools-tools
> Attachments: Example.png, Screen Shot 2019-05-30 at 5.14.30 PM.png
>
>
> This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation.
> h1. Requirement
> - The user would like to have additional search for text in *Guided Decision Table* and *Decision Model and Notation (DMN)* editor because standard browser search not allows to do it.
> - We may add auto-suggestion mechanism
> - Do we need search history?
> - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
> - The example text in the input field disappears when you enter the first character, and appears again, if the input field is empty.
> h1. UX design
> - Add magnifying-glass icon.
> - Search-box can be popup window after clicking on icon or just pop field
> - The simple way is just create search inside of "Expression editor" or we can make search from "Graph editor" which return result from both "Expression editor" and "Graph editor" as a list, so it may looks as search we do in DMN data types tab. Also we can make separate search for both.
> h1. Documentation
> - Replace picture of GDT and DMN editor where they become obsolete
> h1. Acceptance test
> - Enter to large amount of data in search box
> - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
> - Set of inputs:
> *- A-Z
> *- a-z
> *- 0-9
> *- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +
> *- Blank spaces
> *-
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (DROOLS-4089) EvaluatedExpression not well resolved with JIT during race
by vincent palau (Jira)
[ https://issues.jboss.org/browse/DROOLS-4089?page=com.atlassian.jira.plugi... ]
vincent palau commented on DROOLS-4089:
---------------------------------------
Wonderful!
No problem for the reproducer, we are glad to contribute to this project.
Thanks again :)
> EvaluatedExpression not well resolved with JIT during race
> ------------------------------------------------------------
>
> Key: DROOLS-4089
> URL: https://issues.jboss.org/browse/DROOLS-4089
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.20.0.Final, 7.22.0.Final
> Reporter: vincent palau
> Assignee: Mario Fusco
> Priority: Major
> Attachments: debugging-1.png
>
>
> We recently moved from Drools 7.9.0 to 7.20.
> Some errors started appearing in ours tests when calling static methods in LHS drools.
> This started happening when all tests were run simultaneously.
> It seems the mvel JIT compiler kicks in and it incorrectly evaluates the property name:
> A simple call to {noformat}ValidationUtils.isNullOrEmpty(interestedPartyNumber){noformat} ends up with this kind of error:
> {noformat}
> "java.lang.RuntimeException: Unknown property 'nullOrEmpty' on class tech.stage.utils.cwr.model.PublisherRecord"
> {noformat}
> Debugging info:
> Related source-code: https://github.com/kiegroup/drools/blob/7.20.0.Final/drools-core/src/main...
> !debugging-1.png|full!
> 1) is the current evaluated property
> 2) Should be the right property of WriterRecord
> 3) Perhaps the expression which should be executed instead of invocations.get(0)
> We fixed that somehow disabling JIT with {noformat}ConstraintJittingThresholdOption{noformat}
> Is there any chance to this bug fixed?
> Do you need more info?
> Thanks in advance for your support.
> {panel:title=Reproducer}
> https://github.com/vp-stage/evaluatedexpressionandjit
> {panel}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months