View source | Discuss this page | Page history | Printable version   

User Manual/Window Personalization



Bulbgraph.png   This is a Premium functionality. Learn more about the benefits of Openbravo's commercial editions

The window personalization function makes it possible to store and retrieve customized views and settings on both grid and form level. This will include default sorting, querying and filter settings.

Window personalization is available in 2 modes:

Window personalization is completed in Openbravo 3.0 MP4. The earlier MP2 contained basic grid and form personalization.

The following sections describe how to personalize the form and the grid. Then the next step is to store the personalization settings using a certain name on a certain level (client/org/role).

The personalized window settings for all users can be accessed through the Window Personalization window by an administrator. The administrator can delete settings or change the level on which the settings apply.

Form Personalization

The form personalization can be started from the tab itself, so a form can be directly personalized. This function is available if user-level personalization is not explicitly disabled (see a later section on this page on the preference which can be used for that).

The form personalization button is available in the toolbar.

WIK FormPersonalization.png

Clicking on the button will start the Form Personalizer or Form Builder.

Form Personalizer/Builder

The Form Personalizer allows you to change the order and visibility of fields, and several other settings:

Form personalizer.png

The Form Personalizer consists of 4 main sections:

Toolbar and Statusbar

The toolbar shows the following buttons:

The close button in the status bar will close the Form Personalizer and go back to the previous view.

Fields Section

In this section you can:

Form personalization right click.png

The icons in front of a field gives hints on some field properties:

Note, fields which are mandatory and do not have a default can't be hidden.

Preview Section

The preview sections illustrates the changes you make through the fields and properties section. Note that the preview will also show fields which have so-called display logic. These fields may be hidden in the real form.

Properties Section

The properties section can be expanded/collapsed by clicking the Fields or Properties tab header. The properties section allows you to define extra layout-oriented properties:

Grid Personalization

The grid personalization settings which are stored are:

Grid personalization columns.png

Window Layout Personalization

The following parts of the window layout are also stored in the window personalization settings:

Saved and Named Views

After changing/customizing the window personalization a user or administrator can save the current view state using a certain name. A view can be set as the default to apply when the window is opened.

Saving a view, deleting, set as default

To save a view click the pop-down menu button in the top-right of the window (note if the button is disabled, this is premium functionality and see the section below on the preference disabling window personalization).

Window personalization button.png

Initially the pop-down menu will only show a 'Save View' option. Click it to store the current personalization settings using a certain name.

After saving a first view you will see 2 additional menu options:

Select a view

When opening a window the default view (if set) is applied. The selected view is denoted with a small arrow on the left side. You can select a view by clicking on the view name.

Window personalization selectedview.png

Storing views at different levels

The Window Personalization function makes it possible to store/maintain views at different levels:

Window personalization levels.png

If the current user is an administrator then the Save View dialog will show additional comboboxes to select the desired level to store the view. The view will then be available to all users for the selected level (and the particular client/organization/role). The user at that level can not change the personalized view, only select it or set it as the default to use.

A user is defined as an administrator for different levels:

User admin client.png
User admin role.png
User admin org.png

Window Personalization Maintenance

The window personalization maintenance window can be reached through the application menu (General Setup > Application > Window Personalization) or through quick launch. Depending on your role it shows the window personalizations records on system or client level.

The window personalization records can be deleted or assigned to a different level.

Default Form/Grid Personalization (without saved views)

When not saving a view the form/grid personalization settings are still stored at user level (if not prevented by the user preference see the next section). So a user can make changes to the form and grid layout and they are automatically persisted without saving a view. These grid/form settings work as a default.

Note: if there is at least one saved view for a window then these default grid/form settings are not used anymore. So they only apply when working in completely no-view mode.

These non-view settings are stored in 2 locations:

Window pers form settings.png
Window pers grid settings.png

These records can be removed by an administrator to restore the default behavior for a user.

Preference to prevent user level personalization

Window personalization supports a special preference which makes it possible to disable user-level personalization, to prevent:

The preference is the 'Allow Window Personalization by User' property, set it to N or false and choose the visibility level to apply this preference.

If this preference is N or false then the personalization button is disabled for the tab's within the levels defined in the preference (client, organization, role, user, window).

Retrieved from ""

This page has been accessed 23,855 times. This page was last modified on 22 February 2012, at 10:58. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.