Browsing Spanish translation

Don't show this notice anymore
Before translating, be sure to go through Odoo Translators (MOVED TO TRANSIFEX) instructions and Spanish guidelines.
110 of 52 results
Search views in OpenERP allow the responsible user to search in only one view. Indeed, a Sales Responsible user, can see, in the same view, his created documents (sale orders) and, if he is allowed, the one created by his colleagues. So, in Sales Order menuitem, he can see all quotations, current sales and sales to invoice.
(no translation yet)
Located in ../../source/usability_book/3. OpenERP's Views/Search Views.rst:11
The terminology used to qualify each element of the search view are related to the application and also to the business context of use. For example, in sale order, there are buttons to filter different states. Instead of using a state label “Draft”, we use a label more explicit for the sales context which is “Quotations”.
(no translation yet)
Located in ../../source/usability_book/3. OpenERP's Views/Search Views.rst:17
Many options are given to users to optimize their searches. Buttons are used to quickly filter groups of important documents. Usually, a button is chosen following the importance of the document's type. We can take a look at an example, in sale order, it is important that the user can quickly see only the quotations that he needs.
(no translation yet)
Located in ../../source/usability_book/3. OpenERP's Views/Search Views.rst:22
In all search views there are also some selected search fields. These fields are usually chosen regarding the importance of the object (related to column of list view). An example of this would be, in sale order search view, the salesman should be able to see current sales regarding only one customer.
(no translation yet)
Located in ../../source/usability_book/3. OpenERP's Views/Search Views.rst:24
Finally, OpenERP allows users to search following most of the elements we can find in form view with personal filter. Thanks to these filters, we can lighten and clear the view. If users want see all leads that come from one state in the United-States, they can add a filter easily and then save it as a preference, this is especially useful if they have to use it often.
(no translation yet)
Located in ../../source/usability_book/3. OpenERP's Views/Search Views.rst:36
In extended view, in some search views, there are extended filters. These are used to allow user filtering on important elements but are not specific to a list view. For example, in Leads, there is not the Lead's country in the Lead list view, but, it regularly happens that Salesman want to filter all Leads by a specific country. It also allows you to modify columns of the list view by adding one. This kind of field is only on the extended interface and not in all search views. Our goal is to simplify, so if it is not necessary, there are no extended filters. A user can always use a personal filter.
(no translation yet)
Located in ../../source/usability_book/3. OpenERP's Views/Search Views.rst:44
OpenERP allows users to configure their installation to their business's needs. When a user creates a database they can choose one or more applications. They will then see some configuration wizards to add modules related to the chosen application(s) and so, their needs. For example, if the user has chosen “Project” they will see a wizard to configure Project Management.
(no translation yet)
Located in ../../source/usability_book/4.Configuration/Configuration_wizards.rst:18
We usually try to define new business applications related to job positions in the enterprise. These are good examples of applications : Purchase, Sales, Accounting, Project, etc. Don't create business application by features. These are wrong examples of business applications : lunch orders management, expenses sheets, etc.
(no translation yet)
Located in ../../source/usability_book/7.Guidelines/1business applications.rst:9
One user/role must be able to perform most of his tasks from one business application. He should not be forced to switch to another application to perform the tasks of the same role. Example, a salesman should see in his menu: Leads, Opportunities, Meetings, Sales Orders, Sales to Invoice, etc. He should not be forced to go to the accounting application to invoice the sales.
(no translation yet)
Located in ../../source/usability_book/7.Guidelines/1business applications.rst:31
Some features should be accessible by all users, not depending on the application they usually works in. As an example, most of the users should have an access to: Partners, Agenda of Meetings, Products. In that case, you put the menu in the applications that needs these features more. (Example: the address book is in the sales, purchases and accounting application) And, these features must be set as shortcuts for every user in the system by default, at the creation of the user.
(no translation yet)
Located in ../../source/usability_book/7.Guidelines/1business applications.rst:36
110 of 52 results

This translation is managed by OpenERP Spain Team, assigned by Odoo Translators (MOVED TO TRANSIFEX).

You are not logged in. Please log in to work on translations.

Contributors to this translation: Alexandro Colorado, Angel Rivas, Xavier (Open ERP).