[JBoss JIRA] (DROOLS-4395) [DMN Designer] Validation fails for included models
by Edson Tirelli (Jira)
[ https://issues.jboss.org/browse/DROOLS-4395?page=com.atlassian.jira.plugi... ]
Edson Tirelli commented on DROOLS-4395:
---------------------------------------
[~tari_manga] are you aware of this issue?
> [DMN Designer] Validation fails for included models
> ---------------------------------------------------
>
> Key: DROOLS-4395
> URL: https://issues.jboss.org/browse/DROOLS-4395
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.25.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
> Attachments: Screenshot from 2019-08-02 14-01-32.png, error.log
>
>
> The attached screenshot shows an error coming from a dmn file that has a imported another dmn model. All dmn models with imported other models (dmn or pmml) throws an error during validation.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (DROOLS-4395) [DMN Designer] Validation fails for included models
by Edson Tirelli (Jira)
[ https://issues.jboss.org/browse/DROOLS-4395?page=com.atlassian.jira.plugi... ]
Edson Tirelli reassigned DROOLS-4395:
-------------------------------------
Assignee: Matteo Mortari (was: Michael Anstis)
> [DMN Designer] Validation fails for included models
> ---------------------------------------------------
>
> Key: DROOLS-4395
> URL: https://issues.jboss.org/browse/DROOLS-4395
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.25.0.Final
> Reporter: Jozef Marko
> Assignee: Matteo Mortari
> Priority: Critical
> Labels: drools-tools
> Attachments: Screenshot from 2019-08-02 14-01-32.png, error.log
>
>
> The attached screenshot shows an error coming from a dmn file that has a imported another dmn model. All dmn models with imported other models (dmn or pmml) throws an error during validation.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (DROOLS-4393) Expired events can be present in the collect result
by Mario Fusco (Jira)
[ https://issues.jboss.org/browse/DROOLS-4393?page=com.atlassian.jira.plugi... ]
Mario Fusco updated DROOLS-4393:
--------------------------------
Issue Type: Bug (was: Feature Request)
> Expired events can be present in the collect result
> ---------------------------------------------------
>
> Key: DROOLS-4393
> URL: https://issues.jboss.org/browse/DROOLS-4393
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.24.0.Final
> Reporter: Alberto Fanjul Alonso
> Assignee: Mario Fusco
> Priority: Major
> Attachments: reproducer-02425402.zip
>
>
> Is there any option to expire the facts before fireAllRules()?
> A reproducer for drools 6.5.0.Final-redhat-25 (tested too on 7.23.0.Final-redhat-00002 and 7.24.0.Final) shows that facts are not expired until we run fireAllRules().
> Trying reproducer:
> Show facts are expired after fireAllRules():
> ```
> unzip -d reproducer reproducer-02425402.zip
> cd reproducer
> git checkout master
> ./run.sh
> ```
> Show facts are not expired before fireAllRules():
> ```
> git checkout original
> ./run.sh
> ```
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (DROOLS-4245) [DMN Designer] Documentation - Enhance presentation
by Brian Dellascio (Jira)
[ https://issues.jboss.org/browse/DROOLS-4245?page=com.atlassian.jira.plugi... ]
Brian Dellascio edited comment on DROOLS-4245 at 8/6/19 1:56 PM:
-----------------------------------------------------------------
I don't think leaving branding off completely is an option (given the conversation up until this point). I'd say the safest bet is to co-brand in both cases (assuming no conditional control) with community on the left, Red Hat on the right. I don't think anyone internally would have a problem with that approach since it would align with Red Hat's pro-community culture.
was (Author: bdellasc):
I don't think leaving branding off completely is an option (given the conversation up until this point). I'd say the safest bet is to co-brand in both cases (assuming no conditional control) with community on the left, Red Hat on the right.
> [DMN Designer] Documentation - Enhance presentation
> ---------------------------------------------------
>
> Key: DROOLS-4245
> URL: https://issues.jboss.org/browse/DROOLS-4245
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Brian Dellascio
> Priority: Major
> Labels: UX, UXTeam, VisualDesign, drools-tools
> Attachments: RedHat_KIE_logo.eps, RedHat_KIE_logo.png, RedHat_KIE_logo.svg, doc.pdf, new_doc.pdf
>
>
> Enhance styles and presentation of the Documentation output.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (DROOLS-4245) [DMN Designer] Documentation - Enhance presentation
by Brian Dellascio (Jira)
[ https://issues.jboss.org/browse/DROOLS-4245?page=com.atlassian.jira.plugi... ]
Brian Dellascio commented on DROOLS-4245:
-----------------------------------------
I don't think leaving branding off completely is an option (given the conversation up until this point). I'd say the safest bet is to co-brand in both cases (assuming no conditional control) with community on the left, Red Hat on the right.
> [DMN Designer] Documentation - Enhance presentation
> ---------------------------------------------------
>
> Key: DROOLS-4245
> URL: https://issues.jboss.org/browse/DROOLS-4245
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Brian Dellascio
> Priority: Major
> Labels: UX, UXTeam, VisualDesign, drools-tools
> Attachments: RedHat_KIE_logo.eps, RedHat_KIE_logo.png, RedHat_KIE_logo.svg, doc.pdf, new_doc.pdf
>
>
> Enhance styles and presentation of the Documentation output.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months