Skip to main content
Version: 8.2

Model & view management

Models​

info

In AOS, a model corresponds to a template.

Access: Administration → Model management → All models / custom models

In the Model menu, you will find the list of models.

Model: a model is an object. For example, the financial account is an object at the model level. If you click on the model, you will find all the fields that make up the object on the model record.

Access: Administration → Model management → Custom models

tip

Custom model: custom models must be created from the Studio.

Custom field​

Access: Administration → Model management → Custom fields

You can also create custom fields (options, conditions, etc.). In addition, you can add widgets to them.

View management​

In the view management, you will find all the elements of the Axelor ERP. Namely the list, form, tree, graphic, etc. views. You can search from the object (model) or from the module.

For your information, these menus are widely used by customers to understand the operations carried out in the application or the conditions of a field (if it is required and why, etc.).

Access: Administration → View Management → All views

In the ‘All views’ menu, you will find a list of all views: the calendar view, the order view, the form view, etc.

For example:

  1. In the Sales orders menu (Sales → Sales orders), enter ‘sale-order-form’ in the Name field in order to display the different types of sale order form.

  2. You will notice that the list is made up of sale order forms in different colours.

  • The views in black are ‘initial’ views.

  • The orange views are view extensions. When you create view extensions, they will not disappear after a software update.

  • The blue views are ‘calculation’ views (calculated from the initial view). This allows you to make changes.

caution

The changes will not be updated.

They will be lost after a software update.

info

How do I access technical information as an Administrator?

Access: Administration → User management → Groups → click on the Administrator's file

Technical staff: on the file, check the ‘Technical staff’ box. When this option is enabled, you can see all technical elements in each field.

Customize view​

Access: Administration → View management → All custom views

Custom view: a custom view is a view that the user has been able to modify.

Can customize: for the view to be customisable, on the group record (for example, the Administrator) in the ‘View customisation’ field, enter the value ‘Can customize’.

Customisation includes:

  • The user can change the order of the columns.

  • The user can add additional fields.

  1. For example, open the list of Invoices (Invoicing → Customer Invoices).

  2. Then click on the ‘Company’ field and select ‘Customise’. For example, you will be able to customise columns by selecting other fields at the same time. In addition, you can drag and drop the fields to define the order. Following these changes, the view will be updated.

  3. Custom view: open the customised view which can be found in the list of all customised views (Administration → View Management → All custom views).

  4. Shared: when the ‘Shared’ box is ticked, it means that the custom view has been shared with everyone.

Access: Administration → View management → All Menus

In the ‘All Menus’ menu, consult a wide range of information: the name, title, parent, action, etc.

For example, enter the title ‘User Management’ in the ‘Title’ field. User Management will have ‘Administration’ as its Parent, the name is ‘menu-auth’, and the module is axelor-core.

You will also be able to define which menu it is by ticking the corresponding boxes: Left menu / Mobile menu / Hidden menu.

Actions​

Access: Administration → View management → All Actions

In the Actions list, find all the actions of application. You can sort the actions by name, type, model and module.

When you open the file for an action, you will find the actions that are contained within it (in the ‘Definition’ table). You will also be able to see what type of action is called.

Access: Administration → View management → Actions Menus

Actions Menus must be created via the Studio. These actions are associated with menus.

Selections​

Access: Administration → View management → All Selects

In the ‘All selects’ menu search selections by name. For example: sale%order%status.

If you open the order status file (sale%order%status), you will find the selection and its values (for example, a Draft has the value of 1, a Finalized quotation has the value of 2, a Confirmed sale order has the value of 3, etc.). The values can be reused in queries. For example, if you only want to view cancelled orders, you can sort them by the value of 5 (saleorder=5).

Translations​

Access: Administration → View management → All translations

Find the list of translations in the translations menu. Please note that the translations are in source code.

If you wish to modify a translation, you can do so in an Excel file and then import it into the application.

caution

If you modify the translation directly in the ‘All translations’ menu, the new translation will not be taken into account. Therefore, translations must be modified in an Excel file and imported into the application.

View attributes​

Access: Administration → View management → View attributes

View attributes allow you to add additional elements to fields. For example, when you open the form for a view attribute, you can define a default value for a field, as well as define associated roles.

Graphs​

Access: Administration → View management → All charts

In the ‘All charts’ menu, you will find a list of all charts in the application. On a chart form, you will find SQL queries that have been configured for the management of chart-type views.

Technical Staff​

When a user has ‘Technical Staff’ access in his group, he has access to several technical informations, namely:

  1. Viewing objects and the names of fields when you hover the mouse over them, such as:

  • Model (Object).

  • Field name.

  • Field type.

  • Field reference.

  • Original value (selection value).

  1. Being able to access technical modifications from any view, with:

  • The model: list of the object's fields.

  • The action: action that has been generated from this menu.

  • View: the XML view in question.

caution

Be aware that any changes that were made in the app, will be deleted when a new version is updated.

Custom views​

Users can be given access to customise list views, with three levels of access (on the ‘Group’ tab), namely:

  • Not allowed: it means that a user cannot customise.

  • Can customize: customisable.

  • Can share: if the user shares a customisation, all users will inherit this modification.

To customise a view, simply go to a list view and click on any of the arrows of any column to customise it. A list of actions will appear, then select ‘Customize’.

Once customised, it is possible to:

  1. Drag and drop columns to change their position.

  2. Select existing fields on the object.

  3. Save the width of the columns created by the user.

  4. Apply it by default to all users (if the customisation group is ‘can share’).

  5. Once the customisation has been validated, you will find these in the ‘customised views’ menu. Here you will find the name of the user who customised the view and whether or not the view is shared. You can easily duplicate the view for multiple users if necessary.