[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:comment-tabpanel&focusedCommentId=13650006#comment-13650006 ] 

Gabriele Cardosi edited comment on DROOLS-3095 at 10/18/18 10:13 AM:
---------------------------------------------------------------------

Modification after https://github.com/kiegroup/drools-wb/pull/963#pullrequestreview-165590336

1 User may map a property *even before* its instance; in that case, the instance header is automatically set to the property' containing data object.
2 Right/left clicking on a "property" header should insert a column with the "same" instance header, immediately at its right/left (verify that all the properties of the same instance are always grouped together)
3 Right/left clicking on a "instance" header should insert a column to the right/left of the "instance" group (verify that all the properties of the same instance are always grouped together)



was (Author: gabriolo):
Modification after https://github.com/kiegroup/drools-wb/pull/963#pullrequestreview-165590336

1 User may map a property *even before* its instance; in that case, the instance header is automatically set to the property' containing data object.


> 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: 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



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