]
Jozef Marko commented on DROOLS-4799:
-------------------------------------
[~uxdlc] Hello, thank you for your comment. I agree with first two points. I think I am
different opinion about "We don't try to convert values from expression to
form-based.", because we do (try to do) conversion in DMN constraints. However it may
me difficult to implement it. If [~yamer] say it is too big task, then I am fine with your
proposal.
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