[JBoss JIRA] (DROOLS-4117) [DMN Designer] Documentation tab - Simple Stunner infrastructure setup
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-4117?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-4117:
-----------------------------------
Sprint: 2019 Week 23-25, 2019 Week 26-28 (was: 2019 Week 23-25)
> [DMN Designer] Documentation tab - Simple Stunner infrastructure setup
> ----------------------------------------------------------------------
>
> Key: DROOLS-4117
> URL: https://issues.jboss.org/browse/DROOLS-4117
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
>
> This initial setup aims to show the documentation tab with some static content (using Mustache template).
> Implementation of the {{DocumentationView}}, and a simple DMN version of the {{DiagramDocumentationService}}.
> h2. Acceptance test
> Firefox (/) and Chrome (/)
> - Content differs if multiple diagrams opened (/)
> - BPMN not affected (/)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-4118) [DMN Designer] Documentation tab - Show information from the DMN diagram in the documentation tab
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-4118?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-4118:
-----------------------------------
Sprint: 2019 Week 23-25, 2019 Week 26-28 (was: 2019 Week 23-25)
> [DMN Designer] Documentation tab - Show information from the DMN diagram in the documentation tab
> -------------------------------------------------------------------------------------------------
>
> Key: DROOLS-4118
> URL: https://issues.jboss.org/browse/DROOLS-4118
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
>
> This JIRA refers to the DMN version of the {{ClientBPMNDocumentationService}} class.
> This module creates the data model used by the template engine classes. In the DMN version, we can split it into multiple sub-classes.
> This JIRA covers only general information about the diagram, and its visual representation (not including DRD components).
> h2. Acceptance test
> Firefox (/) and Chrome (/)
> - Multiple data types (/)
> - Data types with constraints (/)
> - List data types (/)
> - Connected nodes (/)
> - Separated nodes (/)
> - Nodes exceeding canvas size (/)
> - Fonts (/)
> - Colors (/)
> Linux/Windows
> - Download and open (/)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-4042) [DMN Designer] Add support for importing and consuming PMML models 7.5
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-4042?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-4042:
-----------------------------------
Sprint: 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28 (was: 2019 Week 20-22, 2019 Week 23-25)
> [DMN Designer] Add support for importing and consuming PMML models 7.5
> ----------------------------------------------------------------------
>
> Key: DROOLS-4042
> URL: https://issues.jboss.org/browse/DROOLS-4042
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Affects Versions: 7.24.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
> Fix For: 7.24.0.Final
>
>
> We need the ability to import PMML _documents_. This should be via the "Imported models" tab. Once a _document_ has been imported (and an alias assigned) selection of the _document_ and a _model_ held therein should be possible via the PMML Function boxed expression editor.
> h2. Requirement
> - As user, via included models tab, remove included pmml model, even if used somewhere
> - As user, via included models tab, rename included pmml model, even if used somewhere
> - As user, via included models tab, include multiple pmml models
> - As user, via included models tab, include multiple pmml models at the same time eternal dmn
> - As user, via included models tab, include multiple pmml models at the same time external dmn, kinds are visually distinguished
> - As user, via dmn designer, if Document or Model of included pmml was changed, the lisboxes in dmn offers new values
> - As user, via included models tab, no restriction for included pmml model name
> - As user, via new test scenarios, test dmn model that uses pmml inside
> - As user, via kie-server, query kie container that has dmn model with pmml
> - As user, via included models tab, I want to have just unique aliases of imported models
> h2. UX design
> - Selectbox in place of Document and Model selection
> h2. Documentation
> - Mention what pmml model can be imported into dmn
> - Mention where it can be used
> - Mention if something more needed to dpeloy such project on kie server
> h2. Acceptance test
> - Include two pmml models
> - In dmn, select one in function grid
> - Change the selected one to second
> - Finish the dmn model
> - build deploy on kie-server
> - Interact with kie container via rest
> - Create new test scenario for created dmn model
> - In included models tab, try to include one pmml and one dmn with same alias, it shouldn't be possible
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-4102) Persist/reload Test Scenario table width/height
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-4102?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-4102:
-----------------------------------
Sprint: 2019 Week 23-25, 2019 Week 26-28 (was: 2019 Week 23-25)
> Persist/reload Test Scenario table width/height
> -----------------------------------------------
>
> Key: DROOLS-4102
> URL: https://issues.jboss.org/browse/DROOLS-4102
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Yeser Amer
> Priority: Major
> Labels: ScenarioSimulation
>
> Implement a mechanism to store/restore column width ({{FactMapping}}) and row height ({{Scenario}}) for the table in Test Scenario.
> Please consider:
> - Create/save a simulation (default column width/row height in scesim)
> - Rename a simulation (it perform a save/reload)
> - Change column type (recreate the column)
> - Duplicate column (preserve same size)
> - Duplicate row (preserve same size)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months