[ https://issues.jboss.org/browse/DROOLS-2788?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-2788: --------------------------------------- [~uxdlc] I think that your proposal is covering only a specific use case that is "create new instance with all the fields mapped to columns". I'm sure that is not the most common workflow because you could have a lot of fields and also nested fields. I think it is more simple and clear just to change expression builder component to have two different behaviour: - List of Data Objects (only top level like: Dispute, Account and Amount) - List of fields (also the nested ones like now) of a specific Data Object The workflow I have in mind is: - User create a new instance via contextual menu (so it will have "new column" and "new instance" in that menu) - User select second level header and the expression builder (right panel) will let him choose the type of the instance (i.e. Dispute) - User select third level header and the expression builder will let him navigate and select only Dispute's fields (exactly like now but without the possibility to open/use another type) - User can add as many third level headers as he wants via same existing mechanism "new column" We can probably add also a "Duplicate Instance" to help the user and block third level editing until the instance type has been defined WDYT? -- This message was sent by Atlassian Jira (v7.12.1#712002)