[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
*- XSS, SQL, JavaScript, HTML injections.
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.
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
*- XSS, SQL, JavaScript, HTML injections.
> [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
>
> 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
> *- XSS, SQL, JavaScript, HTML injections.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
- 1
- 0
[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
*- XSS, SQL, JavaScript, HTML injections.
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
*- XSS, SQL, JavaScript, HTML injections.
> [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
>
> 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
> *- XSS, SQL, JavaScript, HTML injections.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
- 1
- 0
[JBoss JIRA] (DROOLS-4059) Unable to test dmn context
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4059?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4059:
--------------------------------
Fix Version/s: 7.23.0.Final
> Unable to test dmn context
> --------------------------
>
> Key: DROOLS-4059
> URL: https://issues.jboss.org/browse/DROOLS-4059
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.22.0.Final
> Reporter: Jozef Marko
> Assignee: Daniele Zonca
> Priority: Major
> Labels: ScenarioSimulation
> Fix For: 7.23.0.Final
>
> Attachments: Screenshot from 2019-05-21 10-37-01.png, Screenshot from 2019-05-21 10-37-22.png, dmn.zip
>
>
> There is issue with scenario, that verifies dmn context. The attached scenario was created in the way shown in the picture. From the dialog with expected and actual value I clicked *Apply* button to fix scenarios. However after rerun, there is exception that value can not be parsed.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
- 1
- 0
[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.
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
*- XSS, SQL, JavaScript, HTML injections.
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.
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:
*- d
> [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
>
> 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.
> 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
> *- XSS, SQL, JavaScript, HTML injections.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
- 1
- 0
[JBoss JIRA] (DROOLS-2992) Can't compile the kie module which has guided scorecard
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-2992?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-2992:
-------------------------------------
[~pikachu] Hi, could you please clarify if the issue is just if the scorecard uses data object field named *score* inside? Or had you troubles with any guided scorecard?
> Can't compile the kie module which has guided scorecard
> -------------------------------------------------------
>
> Key: DROOLS-2992
> URL: https://issues.jboss.org/browse/DROOLS-2992
> Project: Drools
> Issue Type: Bug
> Components: Guided Score Card Editor
> Affects Versions: 7.11.0.Final
> Environment: All in one jbpm server 7.11 Final
> Mac Oracle jdk 1.8
> Maven 3.5.3
> Reporter: yi gong
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
> Attachments: sandbox1.zip
>
>
> Can't compile the kie module which has guided scorecard by maven plugin
> There are a lot of error
> [ERROR] Message [id=1, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=447, column=0
> [ERROR] text=New declaration of org.kie.pmml.pmml_4_2.model.scorecard.Score redeclared field value :
> [ERROR] existing : java.lang.Double vs declared : double]
> [ERROR] Message [id=2, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=447, column=0
> [ERROR] text=New declaration of org.kie.pmml.pmml_4_2.model.scorecard.Score does not include field scoreCard]
> [ERROR] Message [id=3, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=447, column=0
> [ERROR] text=New declaration of org.kie.pmml.pmml_4_2.model.scorecard.Score can't declare a different set of fields
> [ERROR] existing : [scoreCard, value]
> [ERROR] declared : [displayValue, tgtValue, value, weight]
> [ERROR] diff : [--scoreCard, ++displayValue, ++tgtValue, ++weight]]
> [ERROR] Message [id=4, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=92, column=0
> [ERROR] text=Unable to process type DataField]
> [ERROR] Message [id=5, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=1020, column=0
> [ERROR] text=Unable to process type ScardOutput]
> [ERROR] Message [id=6, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=104, column=0
> [ERROR] text=Unable to process type OutputField]
> [ERROR] Message [id=7, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=132, column=0
> [ERROR] text=Unable to process type Scorecard__calculatedScore]
> [ERROR] Message [id=8, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=196, column=0
> [ERROR] text=Unable to process type Age]
> [ERROR] Message [id=9, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=89, column=0
> [ERROR] text=Unable to process type PMML4AbstractField]
> [ERROR] Message [id=10, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=447, column=0
> [ERROR] text=Unable to process type Score]
> [ERROR] Message [id=11, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=814, column=0
> [ERROR] text=Unable to process type Scard]
> [ERROR] Message [id=12, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=580, column=0
> [ERROR] text=Unable to Analyse Expression context == ctx:
> [ERROR] [Error: unable to resolve method using strict-mode: org.kie.pmml.pmml_4_2.model.scorecard.Score.context()]
> [ERROR] [Near : {... context == ctx ....}]
> [ERROR] ^
> [ERROR] [Line: 580, Column: 4]]
> [ERROR] Message [id=13, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=677, column=0
> [ERROR] text=Unable to resolve ObjectType 'Scorecard__calculatedScore']
> [ERROR] Message [id=14, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=288, column=0
> [ERROR] text=Unable to resolve ObjectType 'DataField']
> [ERROR] Message [id=15, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=864, column=0
> [ERROR] text=Unable to resolve ObjectType 'Scorecard__calculatedScore']
> [ERROR] Message [id=16, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=865, column=0
> [ERROR] text=Unable to resolve ObjectType 'Scard']
> [ERROR] Message [id=17, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=-1, column=0
> [ERROR] text=Unable to Analyse Expression boundInput == $x:
> [ERROR] [Error: unable to resolve method using strict-mode: org.kie.pmml.pmml_4_2.ModelMarker.$x()]
> [ERROR] [Near : {... boundInput == $x ....}]
> [ERROR] ^]
> [ERROR] Message [id=18, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=1052, column=0
> [ERROR] text=Unable to resolve ObjectType 'ScardOutput']
> [ERROR] Message [id=19, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=832, column=0
> [ERROR] text=Unable to resolve ObjectType 'Scard']
> [ERROR] Message [id=20, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=694, column=0
> [ERROR] text=Unable to resolve ObjectType 'Scorecard__calculatedScore']
> [ERROR] Message [id=21, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=695, column=0
> [ERROR] text=Unable to resolve ObjectType 'Scorecard__calculatedScore']
> [ERROR] Message [id=22, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=521, column=0
> [ERROR] text=Unable to resolve ObjectType 'Scorecard__calculatedScore']
> [ERROR] Message [id=23, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=849, column=0
> [ERROR] text=Unable to resolve ObjectType 'Scard']
> [ERROR] Message [id=24, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=742, column=0
> [ERROR] text=Unable to resolve ObjectType 'Age']
> [ERROR] Message [id=25, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=743, column=0
> [ERROR] text=Unable to Analyse Expression (mAge == true && mAge != $m) || vAge != $v:
> [ERROR] [Error: unable to resolve method using strict-mode: org.kie.pmml.pmml_4_2.model.ScardScoreCardData.$m()]
> [ERROR] [Near : {... (mAge == true && mAge != $m) || vAge != $v ....}]
> [ERROR] ^
> [ERROR] [Line: 743, Column: 4]]
> [ERROR] Message [id=26, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=1045, column=0
> [ERROR] text=Rule Compilation error $x cannot be resolved to a variable
> [ERROR] The method setScore(Double) is undefined for the type Object]
> [ERROR] Message [id=27, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=513, column=0
> [ERROR] text=Rule Compilation error $val cannot be resolved to a variable
> [ERROR] $m cannot be resolved to a variable
> [ERROR] $v cannot be resolved to a variable
> [ERROR] The method setName(String) is undefined for the type Score
> [ERROR] $ctx cannot be resolved to a variable
> [ERROR] $wgt cannot be resolved to a variable]
> [ERROR] Message [id=28, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=1030, column=0
> [ERROR] text=Rule Compilation error ScardOutput cannot be resolved to a type]
> [ERROR] Message [id=29, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=843, column=0
> [ERROR] text=Rule Compilation error $obj cannot be resolved to a variable]
> [ERROR] Message [id=30, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=686, column=0
> [ERROR] text=Rule Compilation error $tgt cannot be resolved to a variable]
> [ERROR] Message [id=31, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=670, column=0
> [ERROR] text=Rule Compilation error $tgt cannot be resolved to a variable]
> [ERROR] Message [id=32, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=826, column=0
> [ERROR] text=Rule Compilation error _age cannot be resolved to a variable]
> [ERROR] Message [id=33, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=653, column=0
> [ERROR] text=Rule Compilation error Scorecard__calculatedScore cannot be resolved to a type
> [ERROR] Scorecard__calculatedScore cannot be resolved to a type]
> [ERROR] Message [id=34, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=284, column=0
> [ERROR] text=Rule Compilation error $data cannot be resolved to a variable]
> [ERROR] Message [id=35, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=736, column=0
> [ERROR] text=Rule Compilation error $m cannot be resolved to a variable
> [ERROR] $v cannot be resolved to a variable]
> [ERROR] Message [id=36, kieBase=defaultKieBase, level=ERROR, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=858, column=0
> [ERROR] text=Rule Compilation error $x cannot be resolved to a variable
> [ERROR] $val cannot be resolved to a variable]
> [ERROR] ---
> [ERROR] Warning Messages:
> [ERROR] Message [id=37, kieBase=defaultKieBase, level=WARNING, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=653, column=0
> [ERROR] text=Both an agenda-group ( ) and a ruleflow-group ( ) are defined for rule Scorecard Scard output - Scorecard__calculatedScore. Since version 6.x the two concepts have been unified, the ruleflow-group name will override the agenda-group. ]
> [ERROR] Message [id=38, kieBase=defaultKieBase, level=WARNING, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=772, column=0
> [ERROR] text=Both an agenda-group ( ) and a ruleflow-group ( ) are defined for rule Init ScoreCard Scard. Since version 6.x the two concepts have been unified, the ruleflow-group name will override the agenda-group. ]
> [ERROR] Message [id=39, kieBase=defaultKieBase, level=WARNING, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=670, column=0
> [ERROR] text=Both an agenda-group ( ) and a ruleflow-group ( ) are defined for rule Add PMMLResult with Scorecard output Scard - Scorecard__calculatedScore. Since version 6.x the two concepts have been unified, the ruleflow-group name will override the agenda-group. ]
> [ERROR] Message [id=40, kieBase=defaultKieBase, level=WARNING, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=790, column=0
> [ERROR] text=Both an agenda-group ( ) and a ruleflow-group ( ) are defined for rule Scoring Complete. Since version 6.x the two concepts have been unified, the ruleflow-group name will override the agenda-group. ]
> [ERROR] Message [id=41, kieBase=defaultKieBase, level=WARNING, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=980, column=0
> [ERROR] text=Both an agenda-group ( ) and a ruleflow-group ( ) are defined for rule Init ScoreCard Params Scard. Since version 6.x the two concepts have been unified, the ruleflow-group name will override the agenda-group. ]
> [ERROR] Message [id=42, kieBase=defaultKieBase, level=WARNING, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=225, column=0
> [ERROR] text=Both an agenda-group ( ) and a ruleflow-group ( ) are defined for rule Valid_PMML4DataUnrestricted_Values_Age-null. Since version 6.x the two concepts have been unified, the ruleflow-group name will override the agenda-group. ]
> [ERROR] Message [id=43, kieBase=defaultKieBase, level=WARNING, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=626, column=0
> [ERROR] text=Both an agenda-group ( ) and a ruleflow-group ( ) are defined for rule RemoveMissing_PMML4Data_Scard_Age. Since version 6.x the two concepts have been unified, the ruleflow-group name will override the agenda-group. ]
> [ERROR] Message [id=44, kieBase=defaultKieBase, level=WARNING, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=610, column=0
> [ERROR] text=Both an agenda-group ( ) and a ruleflow-group ( ) are defined for rule InitAsMissing_PMML4Data_Scard_Age. Since version 6.x the two concepts have been unified, the ruleflow-group name will override the agenda-group. ]
> [ERROR] Message [id=45, kieBase=defaultKieBase, level=WARNING, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=161, column=0
> [ERROR] text=Both an agenda-group ( ) and a ruleflow-group ( ) are defined for rule Valid_PMML4DataUnrestricted_Values_Scorecard__calculatedScore-null. Since version 6.x the two concepts have been unified, the ruleflow-group name will override the agenda-group. ]
> [ERROR] Message [id=46, kieBase=defaultKieBase, level=WARNING, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=954, column=0
> [ERROR] text=Both an agenda-group ( ) and a ruleflow-group ( ) are defined for rule PartialScore_Scard_age_14. Since version 6.x the two concepts have been unified, the ruleflow-group name will override the agenda-group. ]
> [ERROR] Message [id=47, kieBase=defaultKieBase, level=WARNING, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=858, column=0
> [ERROR] text=Both an agenda-group ( ) and a ruleflow-group ( ) are defined for rule Link Scard Predicted Fields scorecard__calculatedScore . Since version 6.x the two concepts have been unified, the ruleflow-group name will override the agenda-group. ]
> [ERROR] Message [id=48, kieBase=defaultKieBase, level=WARNING, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=927, column=0
> [ERROR] text=Both an agenda-group ( ) and a ruleflow-group ( ) are defined for rule PartialScore_Scard_age_13. Since version 6.x the two concepts have been unified, the ruleflow-group name will override the agenda-group. ]
> [ERROR] Message [id=49, kieBase=defaultKieBase, level=WARNING, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=900, column=0
> [ERROR] text=Both an agenda-group ( ) and a ruleflow-group ( ) are defined for rule PartialScore_Scard_age_12. Since version 6.x the two concepts have been unified, the ruleflow-group name will override the agenda-group. ]
> [ERROR] Message [id=50, kieBase=defaultKieBase, level=WARNING, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=1045, column=0
> [ERROR] text=Both an agenda-group ( ) and a ruleflow-group ( ) are defined for rule Link Scard Output Fields score . Since version 6.x the two concepts have been unified, the ruleflow-group name will override the agenda-group. ]
> [ERROR] Message [id=51, kieBase=defaultKieBase, level=WARNING, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=826, column=0
> [ERROR] text=Both an agenda-group ( ) and a ruleflow-group ( ) are defined for rule Link Scard Bean Input. Since version 6.x the two concepts have been unified, the ruleflow-group name will override the agenda-group. ]
> [ERROR] Message [id=52, kieBase=defaultKieBase, level=WARNING, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=686, column=0
> [ERROR] text=Both an agenda-group ( ) and a ruleflow-group ( ) are defined for rule Update PMMLResult containing Scorecard output Scard - Scorecard__calculatedScore. Since version 6.x the two concepts have been unified, the ruleflow-group name will override the agenda-group. ]
> [ERROR] Message [id=53, kieBase=defaultKieBase, level=WARNING, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=1030, column=0
> [ERROR] text=Both an agenda-group ( ) and a ruleflow-group ( ) are defined for rule Create Scard Output Bean. Since version 6.x the two concepts have been unified, the ruleflow-group name will override the agenda-group. ]
> [ERROR] Message [id=54, kieBase=defaultKieBase, level=WARNING, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=513, column=0
> [ERROR] text=Both an agenda-group ( ) and a ruleflow-group ( ) are defined for rule simpleOutput_Scorecard__calculatedScore_to_Score. Since version 6.x the two concepts have been unified, the ruleflow-group name will override the agenda-group. ]
> [ERROR] Message [id=55, kieBase=defaultKieBase, level=WARNING, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=596, column=0
> [ERROR] text=Both an agenda-group ( ) and a ruleflow-group ( ) are defined for rule miningPmml4Data_Scard_Age. Since version 6.x the two concepts have been unified, the ruleflow-group name will override the agenda-group. ]
> [ERROR] Message [id=56, kieBase=defaultKieBase, level=WARNING, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=538, column=0
> [ERROR] text=Both an agenda-group ( ) and a ruleflow-group ( ) are defined for rule Update PMML4Result with aliased output Score. Since version 6.x the two concepts have been unified, the ruleflow-group name will override the agenda-group. ]
> [ERROR] Message [id=57, kieBase=defaultKieBase, level=WARNING, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=719, column=0
> [ERROR] text=Both an agenda-group ( ) and a ruleflow-group ( ) are defined for rule Bind_Scorecard_PMML4Data_Scard_Age. Since version 6.x the two concepts have been unified, the ruleflow-group name will override the agenda-group. ]
> [ERROR] Message [id=58, kieBase=defaultKieBase, level=WARNING, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=843, column=0
> [ERROR] text=Both an agenda-group ( ) and a ruleflow-group ( ) are defined for rule Own Scard. Since version 6.x the two concepts have been unified, the ruleflow-group name will override the agenda-group. ]
> [ERROR] Message [id=59, kieBase=defaultKieBase, level=WARNING, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=360, column=0
> [ERROR] text=Both an agenda-group ( ) and a ruleflow-group ( ) are defined for rule Sort Scorecard Reason Codes. Since version 6.x the two concepts have been unified, the ruleflow-group name will override the agenda-group. ]
> [ERROR] Message [id=60, kieBase=defaultKieBase, level=WARNING, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=474, column=0
> [ERROR] text=Both an agenda-group ( ) and a ruleflow-group ( ) are defined for rule update_Score_Scard. Since version 6.x the two concepts have been unified, the ruleflow-group name will override the agenda-group. ]
> [ERROR] Message [id=61, kieBase=defaultKieBase, level=WARNING, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=377, column=0
> [ERROR] text=Both an agenda-group ( ) and a ruleflow-group ( ) are defined for rule Integrate Scorecard ReasonCode Map. Since version 6.x the two concepts have been unified, the ruleflow-group name will override the agenda-group. ]
> [ERROR] Message [id=62, kieBase=defaultKieBase, level=WARNING, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=736, column=0
> [ERROR] text=Both an agenda-group ( ) and a ruleflow-group ( ) are defined for rule Bind_Scorecard_Scard_Age. Since version 6.x the two concepts have been unified, the ruleflow-group name will override the agenda-group. ]
> [ERROR] Message [id=63, kieBase=defaultKieBase, level=WARNING, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=346, column=0
> [ERROR] text=Both an agenda-group ( ) and a ruleflow-group ( ) are defined for rule Detect Scorecard ReasonCode Change. Since version 6.x the two concepts have been unified, the ruleflow-group name will override the agenda-group. ]
> [ERROR] Message [id=64, kieBase=defaultKieBase, level=WARNING, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=304, column=0
> [ERROR] text=Both an agenda-group ( ) and a ruleflow-group ( ) are defined for rule Score Card Scard. Since version 6.x the two concepts have been unified, the ruleflow-group name will override the agenda-group. ]
> [ERROR] Message [id=65, kieBase=defaultKieBase, level=WARNING, path=Users/gongyi/src/sandbox/sandbox1/src/main/resources/com/myspace/sandbox1/scard.scgd, line=324, column=0
> [ERROR] text=Both an agenda-group ( ) and a ruleflow-group ( ) are defined for rule Cumulate Code Scores. Since version 6.x the two concepts have been unified, the ruleflow-group name will override the agenda-group. ]
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
- 1
- 0
[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.
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:
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.
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:
> [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
>
> 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.
> 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:
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
- 1
- 0
[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.
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:
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.
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:
> [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
>
> 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.
> 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:
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
- 1
- 0
[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.
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:
* - d
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.
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:
> [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
>
> 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.
> 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:
> * - d
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
- 1
- 0
[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.
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:
*- d
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.
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:
* - d
> [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
>
> 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.
> 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:
> *- d
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
- 1
- 0
[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.
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:
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?
-
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
> [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
>
> 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.
> 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:
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
- 1
- 0