Skip to content
This repository has been archived by the owner on Dec 13, 2020. It is now read-only.

Not saved indicator for records #437

Closed
metas-mk opened this issue Feb 25, 2017 · 4 comments
Closed

Not saved indicator for records #437

metas-mk opened this issue Feb 25, 2017 · 4 comments

Comments

@metas-mk
Copy link
Member

Type of issue

Feature request

Current behavior

The user does not recognize if something she/ he has recorded has been saved in the backend. When saving, then a gray and green line occurs during saving as save indicator. As soon as the save process is finished in the background the indicator disappears.

Expected behavior

When a user opens a window and the data is not saved yet, then the save indicate shall be shown in red color. As soon as save has happened then the already existing behavior kicks in again.

Steps to reproduce

As example. Open A Sales Order Window and start recording. As long as not all mandatory fields are filled, the save process is not possible.

@metas-mk
Copy link
Member Author

Raised to high Priority because we need a solution for unsaved/ dangling records.

@teosarca
Copy link
Member

See:
image

@metas-mk
Copy link
Member Author

metas-mk commented Mar 7, 2017

@damianprzygodzki thanks ... but ... no thanks ;-)
image

we have a very beautiful save indicator w/ gray and green movement and for "not saved" it could just look terrific if that's then a static thin red line between first save try until saved.

@metas-dh
Copy link
Member

Results of IT 2
tested on w101

  • when editing a window and the data is not saved yet, a thin static red line is displayed in document header: OK
  • when editing was done and the data is saved, the grey/green line movement is displayed in document header: OK
    (tested in sales & purchase order, with editing bpartner field & product field in orderline)

@metas-dh metas-dh self-assigned this Mar 15, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants