User can start editing enabled datasource. However datasource has to be disabled in order to save the configuration successfully. Consequently user is not able to save the configuration. For is switched back to view mode and all entered data is lost. User should be either prevented to enter edit mode or there should be an option to disable the datasource on configuration save.
In agreement with Catherine we've decided that UX issues will be tracked separately.
Issue moved under the UX component. Also moved to 6.4 as this issue is still valid for 6.3. Use ack flags to decide whether we want to go through with it or not.
If the "Edit" button was disabled, would the user be able to make the connection that they need to disable the Datasource to be able to edit the configuration? If not, then it might be best to avoid using that solution. Another possibility: A dialog could be presented when the user hits the "Edit" button, which would inform them and provide actions, for example: ------------------------------------------------- “To edit the configuration, the datasource must be disabled. Disable the datasource?” [Cancel] [Confirm] - If the select "Confirm", the datasource is disabled and then they can proceed with editing as expected. - If they select "Cancel", then they return to the screen and perhaps then the Edit button is disabled. ------------------------------------------------- (*Note: actual wording is TBD...)