[JBoss JIRA] (DROOLS-4216) Create runtime and testing version of kogito webapp
by Gabriele Cardosi (Jira)
Gabriele Cardosi created DROOLS-4216:
----------------------------------------
Summary: Create runtime and testing version of kogito webapp
Key: DROOLS-4216
URL: https://issues.jboss.org/browse/DROOLS-4216
Project: Drools
Issue Type: Sub-task
Components: Scenario Simulation and Testing
Reporter: Gabriele Cardosi
Assignee: Gabriele Cardosi
For each asset there should be two *kogito* webapp:
# a **development/testing** one, that should provide **VS CODE** funtionalities,
# a **runtime** one, without the above, to be used inside **VS CODE**
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-3879) Create Submarine version of Scesim editor
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3879?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi updated DROOLS-3879:
-------------------------------------
Description:
Create the *Kogito* (standalone) version of scesim editor.
No Home Page, no Library, No preferences, no other editors.
was:
Create the *Submarine* (standalone) version of scesim editor.
No Home Page, no Library, No preferences, no other editors.
> Create Submarine version of Scesim editor
> -----------------------------------------
>
> Key: DROOLS-3879
> URL: https://issues.jboss.org/browse/DROOLS-3879
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Major
>
> Create the *Kogito* (standalone) version of scesim editor.
> No Home Page, no Library, No preferences, no other editors.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-4195) [DMN Designer] PMML: Update Document value when Import alias changes
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-4195?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-4195:
-----------------------------------
Description:
When a PMML document is imported it is given an alias.
When the PMML document is used in a {{Function}} the alias is used as the document name.
When the import alias is changed {{Function}}'s referencing the old alias should be updated.
*Acceptance tests*
Document name updates in the following scenarios:-
# (?) Top level {{Decision}} defined as a PMML {{FunctionDefinition}}
# (?) Top level {{BusinessKnowledgeModel}} defined as a PMML {{FunctionDefinition}}
# (?) {{Decision}} with nested PMML {{FunctionDefinition}} (i.e. within a {{Context}})
# (?) {{BKM}} with nested PMML {{FunctionDefinition}} (i.e. {{BKM}}s expression is a {{Context}} holding the PMML {{FunctionDefinition}})
Document name is not updated in the following scenarios:-
# (?) Top level {{Decision}} defined as a FEEL {{Context}} with an {{InformationItem}} (variable) name "document"
# (?) Top level {{BKM}} defined similarly to the foregoing {{Decision}}
# (?) Nested variant for {{Decision}}
# (?) Nested variant for {{BKM}}
was:
When a PMML document is imported it is given an alias.
When the PMML document is used in a {{Function}} the alias is used as the document name.
When the import alias is changed {{Function}}'s referencing the old alias should be updated.
*Acceptance tests*
Document name updates in the following scenarios:-
# Top level {{Decision}} defined as a PMML {{FunctionDefinition}}
# Top level {{BusinessKnowledgeModel}} defined as a PMML {{FunctionDefinition}}
# {{Decision}} with nested PMML {{FunctionDefinition}} (i.e. within a {{Context}})
# {{BKM}} with nested PMML {{FunctionDefinition}} (i.e. {{BKM}}s expression is a {{Context}} holding the PMML {{FunctionDefinition}})
Document name is not updated in the following scenarios:-
# Top level {{Decision}} defined as a FEEL {{Context}} with an {{InformationItem}} (variable) name "document"
# Top level {{BKM}} defined similarly to the foregoing {{Decision}}
# Nested variant for {{Decision}}
# Nested variant for {{BKM}}
> [DMN Designer] PMML: Update Document value when Import alias changes
> --------------------------------------------------------------------
>
> Key: DROOLS-4195
> URL: https://issues.jboss.org/browse/DROOLS-4195
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.24.0.Final
> Reporter: Edson Tirelli
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
>
> When a PMML document is imported it is given an alias.
> When the PMML document is used in a {{Function}} the alias is used as the document name.
> When the import alias is changed {{Function}}'s referencing the old alias should be updated.
> *Acceptance tests*
> Document name updates in the following scenarios:-
> # (?) Top level {{Decision}} defined as a PMML {{FunctionDefinition}}
> # (?) Top level {{BusinessKnowledgeModel}} defined as a PMML {{FunctionDefinition}}
> # (?) {{Decision}} with nested PMML {{FunctionDefinition}} (i.e. within a {{Context}})
> # (?) {{BKM}} with nested PMML {{FunctionDefinition}} (i.e. {{BKM}}s expression is a {{Context}} holding the PMML {{FunctionDefinition}})
> Document name is not updated in the following scenarios:-
> # (?) Top level {{Decision}} defined as a FEEL {{Context}} with an {{InformationItem}} (variable) name "document"
> # (?) Top level {{BKM}} defined similarly to the foregoing {{Decision}}
> # (?) Nested variant for {{Decision}}
> # (?) Nested variant for {{BKM}}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-4195) [DMN Designer] PMML: Update Document value when Import alias changes
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-4195?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-4195:
-----------------------------------
Description:
When a PMML document is imported it is given an alias.
When the PMML document is used in a {{Function}} the alias is used as the document name.
When the import alias is changed {{Function}}'s referencing the old alias should be updated.
*Acceptance tests*
Document name updates in the following scenarios:-
# Top level {{Decision}} defined as a PMML {{FunctionDefinition}}
# Top level {{BusinessKnowledgeModel}} defined as a PMML {{FunctionDefinition}}
# {{Decision}} with nested PMML {{FunctionDefinition}} (i.e. within a {{Context}})
# {{BKM}} with nested PMML {{FunctionDefinition}} (i.e. {{BKM}}s expression is a {{Context}} holding the PMML {{FunctionDefinition}})
Document name is not updated in the following scenarios:-
# Top level {{Decision}} defined as a FEEL {{Context}} with an {{InformationItem}} (variable) name "document"
# Top level {{BKM}} defined similarly to the foregoing {{Decision}}
# Nested variant for {{Decision}}
# Nested variant for {{BKM}}
was:
When a PMML document is imported it is given an alias.
When the PMML document is used in a {{Function}} the alias is used as the document name.
When the import alias is changed {{Function}}'s referencing the old alias should be updated.
> [DMN Designer] PMML: Update Document value when Import alias changes
> --------------------------------------------------------------------
>
> Key: DROOLS-4195
> URL: https://issues.jboss.org/browse/DROOLS-4195
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.24.0.Final
> Reporter: Edson Tirelli
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
>
> When a PMML document is imported it is given an alias.
> When the PMML document is used in a {{Function}} the alias is used as the document name.
> When the import alias is changed {{Function}}'s referencing the old alias should be updated.
> *Acceptance tests*
> Document name updates in the following scenarios:-
> # Top level {{Decision}} defined as a PMML {{FunctionDefinition}}
> # Top level {{BusinessKnowledgeModel}} defined as a PMML {{FunctionDefinition}}
> # {{Decision}} with nested PMML {{FunctionDefinition}} (i.e. within a {{Context}})
> # {{BKM}} with nested PMML {{FunctionDefinition}} (i.e. {{BKM}}s expression is a {{Context}} holding the PMML {{FunctionDefinition}})
> Document name is not updated in the following scenarios:-
> # Top level {{Decision}} defined as a FEEL {{Context}} with an {{InformationItem}} (variable) name "document"
> # Top level {{BKM}} defined similarly to the foregoing {{Decision}}
> # Nested variant for {{Decision}}
> # Nested variant for {{BKM}}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months