[jboss-jira] [JBoss JIRA] (DROOLS-4651) Scenario: Review Save interaction in Settings panel.
Gabriele Cardosi (Jira)
issues at jboss.org
Wed Oct 16 09:45:00 EDT 2019
[ https://issues.jboss.org/browse/DROOLS-4651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13800447#comment-13800447 ]
Gabriele Cardosi commented on DROOLS-4651:
------------------------------------------
Hi [~uxdlc] [~porcelli]!
All the informations related to the ScenarioSimulation asset are stored inside the "scesim" file.
Those informations are both data structure/model *and* settings needed to run the scenario (imported DMN for DMN-related scesim, execution settings, etc).
It seems very possible that while the user is editing the data (i.e. whatever is written in the grid) he/she decide to change something in the setting *but* without saving the data.
We needed a way - for the user - to separate *settings* saving from *data* saving.
As far as we know, the common "Save" button is meant to store everything that is present in the editor to the edited file, so we decided to create a specific button and to give it the required logic.
If it is possible to achieve the same result in a different way, we will be happy to implement that.
Cheers
> Scenario: Review Save interaction in Settings panel.
> -----------------------------------------------------
>
> Key: DROOLS-4651
> URL: https://issues.jboss.org/browse/DROOLS-4651
> Project: Drools
> Issue Type: Enhancement
> Components: Test Scenarios Editor
> Reporter: Elizabeth Clayton
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
>
> The use of a Save button in the Settings panel is inconsistent with other "properties" panel in the overall application. The purpose of this jira is to revisit the use case scenarios to determine if the inclusion of the Save button here is appropriate.
> Verification conditions:
> * Documented rationale for the keeping the Save button, as is, with Team acceptance.
> or
> * Documented rationale for removing the Save button, with Team acceptance, in addition to any design changes needed as a result of its removal.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
More information about the jboss-jira
mailing list