[JBoss JIRA] (WFCORE-3977) Changing multicast address in socket binding does not trigger server to set reload-required
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3977?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-3977:
------------------------------------------
[~pferraro] So the ON_DEMAND socket binding service is UP even though Service<TransportConfiguration> is DOWN?
If it's not UP the service would be reinstalled with the current config.
I haven't thought hard about it (I'll leave that to others ;) ) but I can see how the 'bound' check might be more trouble than it's worth. But it seems like a piece is missing somewhere for this particular case.
> Changing multicast address in socket binding does not trigger server to set reload-required
> -------------------------------------------------------------------------------------------
>
> Key: WFCORE-3977
> URL: https://issues.jboss.org/browse/WFCORE-3977
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Affects Versions: 6.0.0.Alpha3
> Reporter: Richard Achmatowicz
> Assignee: Jeff Mesnil
>
> Found this by accident when debugging a clustering test case.
> If I start a server with profile standalone-full-ha and then modify the multicast address of a clustering related socket-binding, in this case, jgroups-mping, the server is not put into state reload-required.
> This causes a lot of problems in the testsuite which depends on configuring servers after startup and then restarting if necessary to pull in the changes.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-2787) "Data Type" tree-grid table interactions.
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2787?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-2787:
-------------------------------------
[~karreiro] [~manstis] [~tirelli] I created an initial Draft click-thru trying to cover the first 3 use cases listed in the description. Please post comments, or I believe you can add comments directly to the click-thru as well:
https://redhat.invisionapp.com/share/5WN6YR57PBV#/311029291_Start
(p.s. it's a little rough, but wanted to get something out quickly for feedback, will refine if this is a good direction.)
> "Data Type" tree-grid table interactions.
> -----------------------------------------
>
> Key: DROOLS-2787
> URL: https://issues.jboss.org/browse/DROOLS-2787
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: DROOLS-2738.bmpr, Screen Shot 2018-07-24 at 3.51.03 PM.png, treegrid.png
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> As a user I want to:
> * *Edit* the list of Data Types, using the appropriate type considering the DMN model (eg: in the age line, we need to select "Numeric" in the combobox.)
> * *Add* a new data type, which might be a nested or otherwise complex object as defined by the (ItemDefinition.)
> * *Remove* Data Types from the list of available selections.
> * be prevented from making selections that are not valid or would cause an error.
> * know that when I edit a data type the changes will be updated in the DMN model.
> Functional considerations/ pre conditions:
> * Outside of simple view/select, Data Types list (and options) will be presented as a tree-grid within a modal dialog. Discussed in detail within Epic subtask for the same.
> * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (WFLY-10588) System property -Djboss.server.log.dir ignored
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFLY-10588?page=com.atlassian.jira.plugin... ]
James Perkins commented on WFLY-10588:
--------------------------------------
Before WildFly 11 you were able to override some of the {{jboss.server.*}} properties. However that could create problems especially for the {{jboss.server.log.dir}} see WFCORE-350 for the reasons it was changed. You should still be able to use the {{jboss.domain.log.dir}} to change where the host-controller and process-controller logs go however.
> System property -Djboss.server.log.dir ignored
> ----------------------------------------------
>
> Key: WFLY-10588
> URL: https://issues.jboss.org/browse/WFLY-10588
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Affects Versions: 13.0.0.Final
> Environment: java version "9.0.1"
> Java(TM) SE Runtime Environment (build 9.0.1+11)
> Java HotSpot(TM) 64-Bit Server VM (build 9.0.1+11, mixed mode)
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "linux", version: "3.13.0-93-generic", arch: "amd64", family: "unix"
> Reporter: Gunther v. Wolffersdorff
> Assignee: Bartosz Baranowski
>
> When starting a doman host node with jvm parameter -Djboss.server.log.dir this parameter will not be set for the subsequent server processes.
> This was correct in WildFly 10.1.0.Final
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-2564) [DMN Editor] Add support to use data-types on applicable Expression types
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2564?page=com.atlassian.jira.plugi... ]
Michael Anstis edited comment on DROOLS-2564 at 7/26/18 11:19 AM:
------------------------------------------------------------------
Listing requirements here; and then possibly move this to an EPIC and add smaller tasks.
*_General_*
- (x) {{<< Back to XXX}} does not update if name changed in Properties panel
- (x) "TypeRef" on Properties panel should show "Output Data Type"
*_Literal Expression_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) Update header when Output Data Type is changed via Properties panel
*_Decision Table_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) Hide Output Data Type in header when there are multiple {{OutputClause}} columns
- (x) {{InputClause}} columns header should show Input Data Type
- (x) {{InputClause}} columns should support changing the Input Data Type
- (x) {{OutputClause}} columns header should show Input Data Type
- (x) {{OutputClause}} columns should support changing the Input Data Type
*_Context_*
- (x) Grid header _could_ show Output Data Type (for Decision/BKM)
- (/) Editing Output Data Type (for Decision/BKM) is possible via Properties panel
- (x) {{ContextEntry}} should show Output Data Type (for {{ContextEntry}})
- (x) {{ContextEntry}} should support changing the Output Data Type (for {{ContextEntry}})
*_Relation_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) {{InformationItem}} column should show Input Data Type
- (x) {{InformationItem}} column should support changing Input Data Type
*_Invocation_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
was (Author: manstis):
Listing requirements here; and then possibly move this to an EPIC and add smaller tasks.
*_General_*
- (x) {{<< Back to XXX}} does not update if name changed in Properties panel
- (x) "TypeRef" on Properties panel should show "Output Data Type"
*_Literal Expression_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) Update header when Output Data Type is changed via Properties panel
*_Decision Table_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) Hide Output Data Type in header when there are multiple {{OutputClause}} columns
- (x) {{InputClause}} columns header should show Input Data Type
- (x) {{InputClause}} columns should support changing the Input Data Type
- (x) {{OutputClause}} columns header should show Input Data Type
- (x) {{OutputClause}} columns should support changing the Input Data Type
*_Context_*
- (x) Grid header _could_ show Output Data Type (for Decision/BKM)
- (/) Editing Output Data Type (for Decision/BKM) is possible via Properties panel
- (x) {{ContextEntry}} should show Output Data Type (for {{ContextEntry}})
- (x) {{ContextEntry}} should support changing the Output Data Type (for {{ContextEntry}})
*_Relation_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) {{InformationItem}} column should show Input Data Type
- (x) {{InformationItem}} column should support changing Input Data Type
*_Invocation_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
> [DMN Editor] Add support to use data-types on applicable Expression types
> -------------------------------------------------------------------------
>
> Key: DROOLS-2564
> URL: https://issues.jboss.org/browse/DROOLS-2564
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> Different types of Expression (the grid-view) should support defining the input and output data-types. I am leaving implementation of this until the ability to use and define data-types at the graph-view is fully complete; as the scenarios required by this JIRA will re-use the same components.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-2564) [DMN Editor] Add support to use data-types on applicable Expression types
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2564?page=com.atlassian.jira.plugi... ]
Michael Anstis edited comment on DROOLS-2564 at 7/26/18 11:18 AM:
------------------------------------------------------------------
Listing requirements here; and then possibly move this to an EPIC and add smaller tasks.
*_General_*
- (x) {{<< Back to XXX}} does not update if name changed in Properties panel
- (x) "TypeRef" on Properties panel should show "Output Data Type"
*_Literal Expression_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) Update header when Output Data Type is changed via Properties panel
*_Decision Table_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) Hide Output Data Type in header when there are multiple {{OutputClause}} columns
- (x) {{InputClause}} columns header should show Input Data Type
- (x) {{InputClause}} columns should support changing the Input Data Type
- (x) {{OutputClause}} columns header should show Input Data Type
- (x) {{OutputClause}} columns should support changing the Input Data Type
*_Context_*
- (x) Grid header _could_ show Output Data Type (for Decision/BKM)
- (/) Editing Output Data Type (for Decision/BKM) is possible via Properties panel
- (x) {{ContextEntry}} should show Output Data Type (for {{ContextEntry}})
- (x) {{ContextEntry}} should support changing the Output Data Type (for {{ContextEntry}})
*_Relation_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) {{InformationItem}} column should show Input Data Type
- (x) {{InformationItem}} column should support changing Input Data Type
*_Invocation_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
was (Author: manstis):
Listing requirements here; and then possibly move this to an EPIC and add smaller tasks.
*_General_*
- (x) {{<< Back to XXX}} does not update if name changed in Properties panel
- (x) "TypeRef" on Properties panel should show "Output Data Type"
*_Literal Expression_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) Update header when Output Data Type is changed via Properties panel
*_Decision Table_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) Hide Output Data Type in header when there are multiple {{OutputClause}} columns
- (x) {{InputClause}} columns header should show Input Data Type
- (x) {{InputClause}} columns should support changing the Input Data Type
- (x) {{OutputClause}} columns header should show Input Data Type
- (x) {{OutputClause}} columns should support changing the Input Data Type
*_Context_*
- (x) Grid header _could_ show Output Data Type (for Decision/BKM)
- (/) Editing Output Data Type (for Decision/BKM) is possible via Properties panel
- (x) {{ContextEntry}} should show Output Data Type (for {{ContextEntry}})
- (x) {{ContextEntry}} should support changing the Output Data Type (for {{ContextEntry}})
*_Relation_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) {{InformationItem}} column should show Input Data Type
- (x) {{InformationItem}} column should support changing Input Data Type
> [DMN Editor] Add support to use data-types on applicable Expression types
> -------------------------------------------------------------------------
>
> Key: DROOLS-2564
> URL: https://issues.jboss.org/browse/DROOLS-2564
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> Different types of Expression (the grid-view) should support defining the input and output data-types. I am leaving implementation of this until the ability to use and define data-types at the graph-view is fully complete; as the scenarios required by this JIRA will re-use the same components.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-2564) [DMN Editor] Add support to use data-types on applicable Expression types
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2564?page=com.atlassian.jira.plugi... ]
Michael Anstis edited comment on DROOLS-2564 at 7/26/18 11:12 AM:
------------------------------------------------------------------
Listing requirements here; and then possibly move this to an EPIC and add smaller tasks.
*_General_*
- (x) {{<< Back to XXX}} does not update if name changed in Properties panel
- (x) "TypeRef" on Properties panel should show "Output Data Type"
*_Literal Expression_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) Update header when Output Data Type is changed via Properties panel
*_Decision Table_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) Hide Output Data Type in header when there are multiple {{OutputClause}} columns
- (x) {{InputClause}} columns header should show Input Data Type
- (x) {{InputClause}} columns should support changing the Input Data Type
- (x) {{OutputClause}} columns header should show Input Data Type
- (x) {{OutputClause}} columns should support changing the Input Data Type
*_Context_*
- (x) Grid header _could_ show Output Data Type (for Decision/BKM)
- (/) Editing Output Data Type (for Decision/BKM) is possible via Properties panel
- (x) {{ContextEntry}} should show Output Data Type (for {{ContextEntry}})
- (x) {{ContextEntry}} should support changing the Output Data Type (for {{ContextEntry}})
*_Relation_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) {{InformationItem}} column should show Input Data Type
- (x) {{InformationItem}} column should support changing Input Data Type
was (Author: manstis):
Listing requirements here; and then possibly move this to an EPIC and add smaller tasks.
*_General_*
- (x) {{<< Back to XXX}} does not update if name changed in Properties panel
- (x) "TypeRef" on Properties panel should show "Output Data Type"
*_Literal Expression_*
- (x) Grid header should show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) Update header when Output Data Type is changed via Properties panel
*_Decision Table_*
- (x) Grid header should show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) Hide Output Data Type in header when there are multiple {{OutputClause}} columns
- (x) {{InputClause}} columns header should show Input Data Type
- (x) {{InputClause}} columns should support changing the Input Data Type
- (x) {{OutputClause}} columns header should show Input Data Type
- (x) {{OutputClause}} columns should support changing the Input Data Type
*_Context_*
- (x) Grid header should show Output Data Type (for Decision/BKM)
- (/) Editing Output Data Type (for Decision/BKM) is possible via Properties panel
- (x) {{ContextEntry}} should show Output Data Type (for {{ContextEntry}})
- (x) {{ContextEntry}} should support changing the Output Data Type (for {{ContextEntry}})
*_Relation_*
- (x) Grid header should show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) {{InformationItem}} column should show Input Data Type
- (x) {{InformationItem}} column should support changing Input Data Type
> [DMN Editor] Add support to use data-types on applicable Expression types
> -------------------------------------------------------------------------
>
> Key: DROOLS-2564
> URL: https://issues.jboss.org/browse/DROOLS-2564
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> Different types of Expression (the grid-view) should support defining the input and output data-types. I am leaving implementation of this until the ability to use and define data-types at the graph-view is fully complete; as the scenarios required by this JIRA will re-use the same components.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-2564) [DMN Editor] Add support to use data-types on applicable Expression types
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2564?page=com.atlassian.jira.plugi... ]
Michael Anstis edited comment on DROOLS-2564 at 7/26/18 11:11 AM:
------------------------------------------------------------------
Listing requirements here; and then possibly move this to an EPIC and add smaller tasks.
*_General_*
- (x) {{<< Back to XXX}} does not update if name changed in Properties panel
- (x) "TypeRef" on Properties panel should show "Output Data Type"
*_Literal Expression_*
- (x) Grid header should show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) Update header when Output Data Type is changed via Properties panel
*_Decision Table_*
- (x) Grid header should show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) Hide Output Data Type in header when there are multiple {{OutputClause}} columns
- (x) {{InputClause}} columns header should show Input Data Type
- (x) {{InputClause}} columns should support changing the Input Data Type
- (x) {{OutputClause}} columns header should show Input Data Type
- (x) {{OutputClause}} columns should support changing the Input Data Type
*_Context_*
- (x) Grid header should show Output Data Type (for Decision/BKM)
- (/) Editing Output Data Type (for Decision/BKM) is possible via Properties panel
- (x) {{ContextEntry}} should show Output Data Type (for {{ContextEntry}})
- (x) {{ContextEntry}} should support changing the Output Data Type (for {{ContextEntry}})
*_Relation_*
- (x) Grid header should show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) {{InformationItem}} column should show Input Data Type
- (x) {{InformationItem}} column should support changing Input Data Type
was (Author: manstis):
Listing requirements here; and then possibly move this to an EPIC and add smaller tasks.
- General
-- (x) {{<< Back to XXX}} does not update if name changed in Properties panel
-- (x) "TypeRef" on Properties panel should show "Output Data Type"
- Literal Expression
-- (x) Header should show Output Data Type
-- (/) Editing Output Data Type is possible via Properties panel
-- (x) Update header when Output Data Type is changed via Properties panel
- Decision Table
-- (x) Header should show Output Data Type
-- (/) Editing Output Data Type is possible via Properties panel
-- (x) Hide Output Data Type in header when there are multiple {{OutputClause}} columns
-- (x) {{InputClause}} columns header should show Input Data Type
-- (x) {{InputClause}} columns should support changing the Input Data Type
-- (x) {{OutputClause}} columns header should show Input Data Type
-- (x) {{OutputClause}} columns should support changing the Input Data Type
- Context
-- (x) Header should show Output Data Type (for Decision/BKM)
-- (/) Editing Output Data Type (for Decision/BKM) is possible via Properties panel
-- (x) {{ContextEntry}} should show Output Data Type (for {{ContextEntry}})
-- (x) {{ContextEntry}} should support changing the Output Data Type (for {{ContextEntry}})
> [DMN Editor] Add support to use data-types on applicable Expression types
> -------------------------------------------------------------------------
>
> Key: DROOLS-2564
> URL: https://issues.jboss.org/browse/DROOLS-2564
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> Different types of Expression (the grid-view) should support defining the input and output data-types. I am leaving implementation of this until the ability to use and define data-types at the graph-view is fully complete; as the scenarios required by this JIRA will re-use the same components.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-2564) [DMN Editor] Add support to use data-types on applicable Expression types
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2564?page=com.atlassian.jira.plugi... ]
Michael Anstis edited comment on DROOLS-2564 at 7/26/18 11:03 AM:
------------------------------------------------------------------
Listing requirements here; and then possibly move this to an EPIC and add smaller tasks.
- General
-- (x) {{<< Back to XXX}} does not update if name changed in Properties panel
-- (x) "TypeRef" on Properties panel should show "Output Data Type"
- Literal Expression
-- (x) Header should show Output Data Type
-- (/) Editing Output Data Type is possible via Properties panel
-- (x) Update header when Output Data Type is changed via Properties panel
- Decision Table
-- (x) Header should show Output Data Type
-- (/) Editing Output Data Type is possible via Properties panel
-- (x) Hide Output Data Type in header when there are multiple {{OutputClause}} columns
-- (x) {{InputClause}} columns header should show Input Data Type
-- (x) {{InputClause}} columns should support changing the Input Data Type
-- (x) {{OutputClause}} columns header should show Input Data Type
-- (x) {{OutputClause}} columns should support changing the Input Data Type
- Context
-- (x) Header should show Output Data Type (for Decision/BKM)
-- (/) Editing Output Data Type (for Decision/BKM) is possible via Properties panel
-- (x) {{ContextEntry}} should show Output Data Type (for {{ContextEntry}})
-- (x) {{ContextEntry}} should support changing the Output Data Type (for {{ContextEntry}})
was (Author: manstis):
Listing requirements here; and then possibly move this to an EPIC and add smaller tasks.
- General
-- (x) {{<< Back to XXX}} does not update if name changed in Properties panel
-- (x) "TypeRef" on Properties panel should show "Output Data Type"
- Literal Expression
-- (x) Header should show Output Data Type
-- (/) Editing Output Data Type is possible via Properties panel
-- (x) Update header when Output Data Type is changed via Properties panel
- Decision Table
-- (x) Header should show Output Data Type
-- (x) Hide Output Data Type in header when there are multiple {{OutputClause}} columns
-- (x) {{InputClause}} columns header should show Input Data Type
-- (x) {{InputClause}} columns should support changing the Input Data Type
-- (x) {{OutputClause}} columns header should show Input Data Type
-- (x) {{OutputClause}} columns should support changing the Input Data Type
> [DMN Editor] Add support to use data-types on applicable Expression types
> -------------------------------------------------------------------------
>
> Key: DROOLS-2564
> URL: https://issues.jboss.org/browse/DROOLS-2564
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> Different types of Expression (the grid-view) should support defining the input and output data-types. I am leaving implementation of this until the ability to use and define data-types at the graph-view is fully complete; as the scenarios required by this JIRA will re-use the same components.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-2791) Test DMN Import with 3 layers of antipattern of importing Decision and InputData
by Matteo Mortari (JIRA)
Matteo Mortari created DROOLS-2791:
--------------------------------------
Summary: Test DMN Import with 3 layers of antipattern of importing Decision and InputData
Key: DROOLS-2791
URL: https://issues.jboss.org/browse/DROOLS-2791
Project: Drools
Issue Type: Task
Components: dmn engine
Reporter: Matteo Mortari
Assignee: Matteo Mortari
Priority: Optional
Attachments: image-2018-07-26-16-53-59-141.png, image-2018-07-26-16-54-21-700.png, image-2018-07-26-16-55-16-778.png, image-2018-07-26-16-55-58-807.png
Given a "base" model (named _Say hello 1ID1D_, referred as _model A_):
!image-2018-07-26-16-53-59-141.png!
Given a B model which imports the base decision:
!image-2018-07-26-16-54-21-700.png!
Given a model B2 which is basically analogous.
Given a model C which imports model B and model B2, so to form an analogous of a "diamond":
!image-2018-07-26-16-55-16-778.png!
Atlhought technically not a proper diamond, because Model A is imported both in the scope of Model B, and Model B2, so something like:
!image-2018-07-26-16-55-58-807.png!
Demonstrate despite antipattern of importing Decision and InputData from imported model, codebase supports the execution.
[ For completeness: antipattern in the sense is expected from good design/blueprint to actually import BKMs or Decision Service(s), and not really Decisions or InputDatas ]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months