[jboss-jira] [JBoss JIRA] (DROOLS-3095) Grid with multiple data/domain object instances

[Gabriele Cardosi (Jira)]

     [ https://issues.jboss.org/browse/DROOLS-3095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gabriele Cardosi updated DROOLS-3095:
-------------------------------------
    Description: 
As user I want to use multiple instances of my DO in a test scenario.

*Implementation specs:*
Implement "Instance" concept on the GIVEN/EXPECTED columns.
Given/Expected columns should have three headers: 
# the top one is the group (GIVEN/EXPECTED),
#  the second one is the actual instance of a given type (ex Person1, Person2, Dispute)
# the third one is the specific property of the instance.
Below every instance header there could be one ore more property header - each of them belonging to that instance.

The workflow to define template creation is going to change because of the new header level:  the user may define the type/name of the instance *before* mapping the final properties, *OR* s/he may define directly a property, in which case the instance is automatically inferred and populated.

When clicking on a GIVEN "Instance" header, user should see only first-level data objects in the right panel.
When clicking on an EXPECT "Instance" header, user should see only first-level data objects in the right panel *AND* the GIVEN instances.

When clicking on a Property header, *if* the instance is already defined, user should see only first-level properties of the instance it belongs to; *otherwise* s/he should see every properties of every data objects. 

Changing Instance type is not allowed (dose not makes sense): only "DELETE" is possible at "Instance" level. Deleting an Instance header(column) recursively delete all the properties.

These issue is related to https://issues.jboss.org/browse/DROOLS-2788

  was:
As user I want to use multiple instances of my DO in a test scenario.

*Implementation specs:*
Implement "Instance" concept on the GIVEN/EXPECTED columns.
Given/Expected columns should have three headers: 
# the top one is the group (GIVEN/EXPECTED),
#  the second one is the actual instance of a given type (ex Person1, Person2, Dispute)
# the third one is the specific property of the instance.
Below every instance header there could be one ore more property header - each of them belonging to that instance.

The workflow to define template creation is going to change because of the new header level: now user must define the type/name of the instance *before* mapping the final properties.

When clicking on a GIVEN "Instance" header, user should see only first-level data objects in the right panel.
When clicking on a Property header, user should see only first-level properties of the Instance it belongs to.
When clicking on an EXPECT "Instance" header, user should see only first-level data objects in the right panel *AND* the GIVEN instances.

Changing Instance type is not allowed (dose not makes sense): only "DELETE" is possible at "Instance" level. Deleting an Instance header(column) recursively delete all the properties.

These issue is related to https://issues.jboss.org/browse/DROOLS-2788



> Grid with multiple data/domain object instances
> -----------------------------------------------
>
>                 Key: DROOLS-3095
>                 URL: https://issues.jboss.org/browse/DROOLS-3095
>             Project: Drools
>          Issue Type: Task
>          Components: Scenario Simulation and Testing
>            Reporter: Gabriele Cardosi
>            Assignee: Gabriele Cardosi
>            Priority: Major
>
> As user I want to use multiple instances of my DO in a test scenario.
> *Implementation specs:*
> Implement "Instance" concept on the GIVEN/EXPECTED columns.
> Given/Expected columns should have three headers: 
> # the top one is the group (GIVEN/EXPECTED),
> #  the second one is the actual instance of a given type (ex Person1, Person2, Dispute)
> # the third one is the specific property of the instance.
> Below every instance header there could be one ore more property header - each of them belonging to that instance.
> The workflow to define template creation is going to change because of the new header level:  the user may define the type/name of the instance *before* mapping the final properties, *OR* s/he may define directly a property, in which case the instance is automatically inferred and populated.
> When clicking on a GIVEN "Instance" header, user should see only first-level data objects in the right panel.
> When clicking on an EXPECT "Instance" header, user should see only first-level data objects in the right panel *AND* the GIVEN instances.
> When clicking on a Property header, *if* the instance is already defined, user should see only first-level properties of the instance it belongs to; *otherwise* s/he should see every properties of every data objects. 
> Changing Instance type is not allowed (dose not makes sense): only "DELETE" is possible at "Instance" level. Deleting an Instance header(column) recursively delete all the properties.
> These issue is related to https://issues.jboss.org/browse/DROOLS-2788



--
This message was sent by Atlassian Jira
(v7.12.1#712002)