Functional Profile

The definition of the functional authorisations is made by entering pairs (profile codes, function codes) in a record. When the authorisation with a function requires no further information, there is nothing else to do. But when the restrictions by site exist, or when the additional options are associated with the functions, this information is to be entered in the grid present in the tab.

This entry can be tedious, but it will be seen later that several more rapid methods exist to select a group of functions to attribute authorisations to them. These possibilities are accessible using the buttons at the bottom of the screen described in this documentation ( , which can be called by right click from the Function field, and the button  ).

To directly enter an authorisation for a single function, it is sufficient to enter the function profile code then the function code. If the access to this function is modulated as a function of the site (that is to say a site field exists in the tables generated by the function and that this field is used to filter a limitation access to the information). This grid is used to enter the following elements :

    a type that can be Site or Grouping, with the associated site or group of sites code. The group is a group of sites that corresponds to a legal company (in this case, the group is automatically updated if the new sites are created in this company). It is possible to give an empty group code ; this case corresponds to all the other sites not explicitly defined by the list of the sites or groups in the grid.

    an Access flag (yes/no). It is thus possible to define for each site, the different authorisations, remembering that a line with an empty group code is used to define the default authorisations for all the other sites not explicitly named.

    an Optionsfiled that can be entered once the additional authorisations are attached to the function. These authorisations are used in general to give access to a button or a menu and to trigger the access to a process or to an additional window. Each option is symbolised by a character. By default, all the characters associated with the existing options are proposed, but it is possible to delete some or all of them. These options are contextual (for example, the access to the open items, symbolised by E that exists in the invoice management), but "standard" options exist accessible when the function is an object management. These options are as follows :

The option U, when it exists, is used to define a filter by user : it is used once a function must be used to process either only the data attached to a user or all (this last choice is only possible if the option U has been activated for the user) the data

It is important to note that a coherency check is made on the sites and groups listed in the authorisations grid. Thus, if two sites belonging to different groups to which distinct authorisations have been accorded, an error message will be displayed and the entry will not be possible.

When the function is not modelled by site, but options exist, the first line in the grid is entered without giving a site code, but only by entering the yes/no flag and the options.

On saving it, the table storing the authorisation definitions, but the authorisation cross reference table is not updated (see below). This update will be made on exiting the function, if the response is Yes to the question Update the table AFCTFCY.