[JBoss JIRA] (DROOLS-4895) Backport RuleUnitComponentFactory#createRuleUnitDescription( KiePackage, String );
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-4895?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-4895:
-----------------------------------
Sprint: 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10) (was: 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20))
> Backport RuleUnitComponentFactory#createRuleUnitDescription( KiePackage, String );
> ----------------------------------------------------------------------------------
>
> Key: DROOLS-4895
> URL: https://issues.redhat.com/browse/DROOLS-4895
> Project: Drools
> Issue Type: Bug
> Reporter: Edoardo Vacchi
> Assignee: Edoardo Vacchi
> Priority: Major
> Labels: drools-core
>
> add {{RuleUnitDescription createRuleUnitDescription( KiePackage pkg, String ruleUnitSimpleName );}} it should be a no-op because it is only used in Kogito
> also {{RuleUnitDescriptionLoader}} may use this method in case {{createRuleUnitDescription( KiePackage pkg, Class<?> ruleUnit );} fails. However, this cannot happen in Drools 7, as the RuleUnit is always described by a Class, so it will always return null (it's a no-op after all). Reasons for backport are only code alignment.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (DROOLS-4584) Scrolling during editing mode move cell in new position on the screen
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-4584?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-4584:
-----------------------------------
Sprint: 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10) (was: 2020 Week 04-06 (from Jan 20))
> Scrolling during editing mode move cell in new position on the screen
> ---------------------------------------------------------------------
>
> Key: DROOLS-4584
> URL: https://issues.redhat.com/browse/DROOLS-4584
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.28.0.Final
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Major
> Labels: CustomerFocus, drools-tools
> Attachments: ScrollIssue.webm, image-2019-10-01-11-24-36-774.png
>
>
> !image-2019-10-01-11-24-36-774.png|thumbnail!
> Cell moves unexpectedly in editing mode
> {color:red}*Failure*{color}
> If you start edit any cell of a big grid and then scroll the input would move not in the right cell.
> *Expected*
> Input element moves with entire table
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (DROOLS-3879) Create Kogito version of Test Scenarios designer
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-3879?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-3879:
-----------------------------------
Sprint: 2019 Week 41-43 (from Okt 7), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10) (was: 2019 Week 41-43 (from Okt 7), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20))
> Create Kogito version of Test Scenarios designer
> ------------------------------------------------
>
> Key: DROOLS-3879
> URL: https://issues.redhat.com/browse/DROOLS-3879
> Project: Drools
> Issue Type: Feature Request
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
>
> Scope of this PR is to create a *Kogito/client-side only* versions of scesim editor.
> From an architectural point of view, the actual implementation has been moved (in the past) inside a common module: `drools-wb-scenario-simulation-editor-client`.
> Access to it has been "hided" behind a wrapper interface with three actual implementations:
> * `drools-wb-scenario-simulation-editor-businesscentral-client` for BusinessCentral environment
> * `drools-wb-scenario-simulation-editor-kogito-testing` to provide a development/debugging setup for the *Kogito/client-side only* environment
> * `drools-wb-scenario-simulation-editor-kogito-runtime` that should be the one deployed in actual client-side only containers (e.g. VSCode).
> As agreed upon in the last summer (https://issues.redhat.com/browse/AF-2041), the kogito editors should depend upon a common library, `org.kie.workbench:kie-wb-common-kogito-webapp-base` to put all the code/maven configuration shared by the different editors in one single place.
> Currently, only the two kogito-related scesim modules fulfill that requirement; all other editors, starting from DMN, should be adapted to this approach.
> Kogito-testing module is a standalone showcase that provides some minimum interaction to:
> * load DMN files
> * create DMN-related scesim assets, selecting one of the imported DMN.
> Currently - RULE/data object model scesim is disabled.
> Kogito-runtime module is the version that should run purely client side. It does not provide any graphical widget to load/create/save asset.
> Some minimal tests may be done in the following way:
> # full compilation (i.e. included GWT compilation) of the runtime module
> # open the `drools-wb/drools-wb-screens/drools-wb-scenario-simulation-editor/drools-wb-scenario-simulation-editor-kogito-runtime/target/drools-wb-scenario-simulation-editor-kogito-runtime/index.html` file inside Chrome
> # inside the Chrome dev console, issue the command `window.gwtEditorBeans.get("ScenarioSimulationEditorKogitoRuntimeScreen").get().setContent("")`; this will show the "New Scesim" popup, where user may choose to create a DMN or RULE scesim; of course, inside Chrome it is not possible to have a reference to other resources, so only "Rule" will work; at the same time, no Data model is available inside Chrome, so the right panel will be empty and the only expected result is an empty grid.
> # edit the asset
> # invoke window.gwtEditorBeans.get("ScenarioSimulationEditorKogitoRuntimeScreen").get().getContent() and store the returned xml
> # invoke window.gwtEditorBeans.get("ScenarioSimulationEditorKogitoRuntimeScreen").get().setContent method with the stored xml
> Some tricks: to avoid CORS and other policy-related issues:
> # set chrome://flags/#allow-insecure-localhost for invalid certificates error
> # start chrome from cli with the command `chrome --allow-file-access-from-files` to allow loading from file.
> /----/
> The "run scenario" functionality won't be implemented by this PR.
> All the functionalities related to file system/resource access will be simulated in the testing modules (but only for the DMN models), and for the runtime module will depend on the API/environment provided by VSCode
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (DROOLS-4905) [DMN Designer] Code Completion - Index all elements named by users
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-4905?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-4905:
-----------------------------------
Sprint: 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10) (was: 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20))
> [DMN Designer] Code Completion - Index all elements named by users
> ------------------------------------------------------------------
>
> Key: DROOLS-4905
> URL: https://issues.redhat.com/browse/DROOLS-4905
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
> Attachments: pick-option-move-to-other-grid.webm
>
>
> Create the infrastructure code that provided all elements named by the user. It will be called by the suggestion component. So users will be able to see as suggestions DRG Elements and Data Types.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (DROOLS-4584) Scrolling during editing mode move cell in new position on the screen
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-4584?page=com.atlassian.jira.plug... ]
Anna Dupliak updated DROOLS-4584:
---------------------------------
Attachment: ScrollIssue.webm
> Scrolling during editing mode move cell in new position on the screen
> ---------------------------------------------------------------------
>
> Key: DROOLS-4584
> URL: https://issues.redhat.com/browse/DROOLS-4584
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.28.0.Final
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Major
> Labels: CustomerFocus, drools-tools
> Attachments: ScrollIssue.webm, image-2019-10-01-11-24-36-774.png
>
>
> !image-2019-10-01-11-24-36-774.png|thumbnail!
> Cell moves unexpectedly in editing mode
> {color:red}*Failure*{color}
> If you start edit any cell of a big grid and then scroll the input would move not in the right cell.
> *Expected*
> Input element moves with entire table
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months