2015-07-07 0:50 GMT+02:00 Albert Cervera i Areny alb...@nan-tic.com:
So here is a screenshot of such invalid form with missing required field
and wrong value because of domain.
I think it is really an improvement because now we explain to the user
what is wrong and experienced user can
2015-07-06 23:36 GMT+02:00 Cédric Krier cedric.kr...@b2ck.com:
On 2015-07-04 08:58, Cédric Krier wrote:
Hi,
For now, we put a blue color on entries when they are required (and
switch to red when validated as empty).
I think it is a bad practice for 2 reasons:
- the colors are not
On 2015-07-07 20:04, Jordi Esteve wrote:
In sale and purchase modules the functional sales and purchases fields are
defined on invoice model with a searcher method.
If these fields are added in the invoice tree view and we search the
invoices related to the SO001 sale, for example, I get
On 2015-07-07 22:35, Albert Cervera i Areny wrote:
2015-07-06 23:36 GMT+02:00 Cédric Krier cedric.kr...@b2ck.com:
On 2015-07-04 08:58, Cédric Krier wrote:
Hi,
For now, we put a blue color on entries when they are required (and
switch to red when validated as empty).
I think it is a
On 2015-07-07 23:38, Cédric Krier wrote:
On 2015-07-07 20:04, Jordi Esteve wrote:
In sale and purchase modules the functional sales and purchases fields are
defined on invoice model with a searcher method.
If these fields are added in the invoice tree view and we search the
invoices
On 2015-07-06 23:36, Cédric Krier wrote:
On 2015-07-04 08:58, Cédric Krier wrote:
Hi,
For now, we put a blue color on entries when they are required (and
switch to red when validated as empty).
I think it is a bad practice for 2 reasons:
- the colors are not custumizable and
