Translations by Victor Yu

like buttons, “group by” are organized in context.

The first group is related to human resources, the second group is related to the state of the document. The third group is related to a place, and finally the last group is related to dates.

A separator is defined between each group. For example : Salesman Partner | Stage State | Shop Company | Day Month Year

Use appropriate icons as defined in :ref:`button-icon-list-link`.

In all search views, except for report's search view, groups by must be folded. The goal is to have simple view by default.

There are extended filters only in extended interface because it complicates the views. In the simplified interface, the user can use optional filters.

By default, extended filters are folded.

Generally, the user can find important fields in extended filters, but it is possible that no column is linked to the field.

Extended filters also give you the possibility to add columns that users might need.

Adapted title to each application : as introduced, chosen application leads to one configuration wizard. Then the configuration wizard has to have a title related to the application.

Picture and information on the left : all wizards have to have one business picture and an explanation text regarding the business application to configure.

Objects (Documents) to configure on the right : all objects related to the application must be chosen with selection box. And have to be placed on the right

Allow user to Skip or Configure : each wizard has to have 2 buttons, one to Skip and one to configure. These buttons have to be placed below on the right.

Progress bar : to allow user see where he is in configuration, all wizards have to have a progress bar with the percentage of completion of database. Separators : Each parts of the wizard has to be separated by a separator bar

Configuration wizards are optional. The system must be usable and configured by default even if the administrator skips all steps during the configuration process. Configuration wizards are available only to:

Propose new features to install (a set of modules)

Change the default configuration of the system (and not configure the system !)

Most of the application wizards must be part of one application. Be sure that:

The application this configuration wizard belongs to is explicit

Terminology are dedicated to the application context. As an example, in a project management application, don't talk about analytic account or entries but talk about projects and timesheets. Avoid configuration wizards that are related to several applications.

Be sure you use extended/simplified views features also in configuration wizards. In order to simplify the configuration process, some options or wizards must be available in extended views only.

Most of the icons are laid in search view. All of the buttons have to have an icon relevant to the function. OpenERP uses a range of predefined icons. Here are the most frequent icons (all icons are in annexe) :

When buttons refer to states :

When buttons refer to a today,meeting, events

When buttons refer to a week

When buttons refer to a date,month and all date when data sorts by month (scheduled date, period, invoice date, due date, <30 days, period of move line),write date, create date, date run

When buttons refer to a Year,<365 days ,fiscal position

When buttons refer to a close, done, expected closing, Uninstalled

When buttons refer to a Cancel, refused, mark lost

When buttons refer to a late, overdue, urgent, very urgent, deadline

When buttons refer to a yesterday

When buttons refer to a Confirm, to validate (tomorrow (timesheet), to do, to fix, force period, to invoice, to approve, To ..., make payment, to be upgraded, Next

When buttons refer to a sign in, go to, destination location

When buttons refer to a sign out, origin, source location, reason

When buttons refer to something inactive

When buttons refer to a plan, task, type, routing

When buttons refer to an exception, shipping exception, invoice exception, unanswered