Versions Compared

Old Version 6

changes.mady.by.user Pavel Matyasko (Deactivated)

Saved on

compared with

New Version 7

changes.mady.by.user Pavel Matyasko (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Use Case Example

You have some Model Objects, which would be normally listed under Optimization › Models, but because they are strongly related to your functionality configured in another application module (e.g. Actionable Insights), you would like to provide easy access to users by providing special menu item under your module, which would display list of the objects you need.

Fields

uniqueName*

(String) Name of this category. Must be unique within the partition.

module

(Application Module) Under which module menu will this menu item appear.

label

(String) Label of the menu item, as displayed to the end-user.

objectsTypeCode

TypeCode of the objects, which will be listed on the list page. Supported types are Model Object and Custom Form.

path

(String) Path to be used in the URL. Can be also used to refer this menu item from links. Limit chars used to lower case letters, no spaces, possibly "" and "-". For example, if you define the value as "cfo_mca", and module to _Pricefx Processes, then the URL will contain "/processes/cfo_mca".

elementsUserGroupViewDetails

Controls access of users to the page with list of objects. (Comma separated list of user group groups unique names.) Users can view elements in this category but not edit them.

elementsUserGroupEdit

Controls access of users to the page with list of objects. (Comma separated list of user groups unique names.) Users can edit elements in this category but not create/delete them.

elementsUserGroupManage

(Comma separated list of user group groups unique names.

elementsUserGroupManage

Controls access of users to the page with list of objects. Comma separated list of user group unique names) User can create/edit/delete elements in this category.

Access Rights Details

Effective user access rights for objects like Model or Custom Form are evaluated from top to bottom:

  1. Role

  2. Module Category groups

  3. Custom Form Type groups

  4. Custom Form groups (coming in version 11.x)

The lower you go, the more restrictive the access rights are, because the effective rights of certain level are an intersection of the level rights with the righs of the upper levels too.

For example, if you will have a Module Category page with list of Custom Forms of certain Custom Form Type, then the access to the particular Custom Form will be driven by intersection of all the rights, i.e. Role, Module Category groups, Custom Form Type groups and also by the groups of Custom Form itself.