[
https://issues.redhat.com/browse/DROOLS-4799?page=com.atlassian.jira.plug...
]
Jozef Marko commented on DROOLS-4799:
-------------------------------------
[~yamer] I think we should save just the the picked option and even do not inform user
about losing some values from the unpicked option. For me it seems quite common in this
kind of forms . (Radio button group, according your choice subform is changed).
[~uxdlc] hello, I think theoretically both has same expressing power, however technically
not sure if we will implement parsing on both in the way, user can express the same in
both options. For example, I can imagine, in both options user can create list of string,
but just in one list of persons, do you see my point?
Adding "expression" type handling for Collection type
propereties
-----------------------------------------------------------------
Key: DROOLS-4799
URL:
https://issues.redhat.com/browse/DROOLS-4799
Project: Drools
Issue Type: Feature Request
Components: Scenario Simulation and Testing, Test Scenarios Editor
Reporter: Yeser Amer
Assignee: Elizabeth Clayton
Priority: Major
Labels: UX, UXTeam, drools-tools
Attachments: Screen Shot 2019-11-26 at 1.26.54 PM.png,
dmn-dt-enumeration-constraint.png, dmn-dt-expression-constraint.png,
expression-list_error.png, scesim-list.png
I need a clarification regarding the behaviour of the updated Collection Editor, in
particular for this section
-->https://marvelapp.com/5ab248j/screen/62093042/layer/102496330.
Considering the editor introduces a new way to handle a Collection ("Define
List"), can you please give us detailed behaviour for the following case:
- What happen if a user starts to input data inside a section (Define List/Create List)
and then switch on the other one?
eg. if I start to define a List using "Define List" option (i.e. an expression)
and then I change to "Create List" case. What should happen?
- Currently, after adding a Collection, the Grid cell will show "List (1)". It
should be the same for "Define list" (i.e. Expression) case?
In case of additional clarificaiton, I'll update this ticket.
Hope it's clear, if not you can contact me anytime.
Thanks
--
This message was sent by Atlassian Jira
(v7.13.8#713008)