[JBoss JIRA] (DROOLS-4195) [DMN Designer] PMML: Update Document value when Import alias changes
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4195?page=com.atlassian.jira.plugi... ]
Jozef Marko 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)
7 years
[JBoss JIRA] (DROOLS-4195) [DMN Designer] PMML: Update Document value when Import alias changes
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4195?page=com.atlassian.jira.plugi... ]
Jozef Marko 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)
7 years
[JBoss JIRA] (DROOLS-4195) [DMN Designer] PMML: Update Document value when Import alias changes
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4195?page=com.atlassian.jira.plugi... ]
Jozef Marko 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)
7 years
[JBoss JIRA] (DROOLS-3731) DMN UX - More info overlaid on models.
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3731?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton commented on DROOLS-3731:
-------------------------------------------
fyi [~tirelli] ^^
> DMN UX - More info overlaid on models.
> --------------------------------------
>
> Key: DROOLS-3731
> URL: https://issues.jboss.org/browse/DROOLS-3731
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Tao Zhu
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam, drools-tools
> Attachments: Screen Shot 2019-05-29 at 2.49.21 PM.png, colors.png, download (1).png, download.png, multi.gif, single.gif, tmp.png, 屏幕快照 2019-06-11 下午3.02.19.png, 屏幕快照 2019-06-11 下午3.10.26.png
>
>
> As a practitioner, there are situations where I need to show additional information about a model... for instance: test coverage report: I need to draw a model and color code the nodes to show which nodes were executed by tests, or which rows on a DT were a match. Or when I execute a single test, what was the actual value of a given node or expression.
> Note: Maybe in read-only mode with an "overlay" on top of the model the additional metadata information. See process instance diagram design examples.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (DROOLS-4195) [DMN Designer] PMML: Update Document value when Import alias changes
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4195?page=com.atlassian.jira.plugi... ]
Jozef Marko 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)
7 years
[JBoss JIRA] (DROOLS-4195) [DMN Designer] PMML: Update Document value when Import alias changes
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4195?page=com.atlassian.jira.plugi... ]
Jozef Marko 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)
7 years
[JBoss JIRA] (DROOLS-3731) DMN UX - More info overlaid on models.
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3731?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton commented on DROOLS-3731:
-------------------------------------------
[~zhutaojiajia] If the new jiras cover what's needed, then please feel free to close this one. Thanks
> DMN UX - More info overlaid on models.
> --------------------------------------
>
> Key: DROOLS-3731
> URL: https://issues.jboss.org/browse/DROOLS-3731
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Tao Zhu
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam, drools-tools
> Attachments: Screen Shot 2019-05-29 at 2.49.21 PM.png, colors.png, download (1).png, download.png, multi.gif, single.gif, tmp.png, 屏幕快照 2019-06-11 下午3.02.19.png, 屏幕快照 2019-06-11 下午3.10.26.png
>
>
> As a practitioner, there are situations where I need to show additional information about a model... for instance: test coverage report: I need to draw a model and color code the nodes to show which nodes were executed by tests, or which rows on a DT were a match. Or when I execute a single test, what was the actual value of a given node or expression.
> Note: Maybe in read-only mode with an "overlay" on top of the model the additional metadata information. See process instance diagram design examples.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (ELY-1836) KeyStoreCredentialStore does not support PrivateKey alone
by Darran Lofthouse (Jira)
Darran Lofthouse created ELY-1836:
-------------------------------------
Summary: KeyStoreCredentialStore does not support PrivateKey alone
Key: ELY-1836
URL: https://issues.jboss.org/browse/ELY-1836
Project: WildFly Elytron
Issue Type: Enhancement
Components: Credential Store
Reporter: Darran Lofthouse
There may be some history to this to consider but it appears it could be useful to support this, data could be encrypted using a server's public key but if contents of the store are to be used to decrypt it we likely would want just the private key.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years