Features

A "feature" is a collection of menu items, model actions, role types and global screen elements which you can create through studio. Enterprises can then be subscribed to certain features, and then non-subscribed elements will be hidden from the user interface.

images/download/attachments/144835293/FeatureDefinitions-version-1-modificationdate-1645044120000-api-v2.png


When referencing menus/actions/etc in a feature, you can define the exact entity name, or you can provide a "glob" pattern.

Please note that in the case of menus, providing permission to a menu will automatically give permission to all menu actions within that menu. For menu(s) to be visible on UI, either menu or at least one menu action under the menu should have permission. Let's take an example of menus:

Exact Pattern Example: In the screen below, we are adding the exact menu "SampleURL" for ZBKS module.

images/download/attachments/144835293/Add_Exact_Menus-version-1-modificationdate-1645044128000-api-v2.png


Glob Pattern Example: In the screen below, we are adding all menus which contain the word "Book" for modules matching with ZBKS, ZBTS ...

images/download/attachments/144835293/Add_Menus_Using_Pattern-version-1-modificationdate-1645044136000-api-v2.png

You can add model actions, role types and global screen elements to features in the same way you add menus.

If you provide * as both module and name pattern, this will match against all entities.

For accessing all menus, actions, role types and screen elements, you can subscribe an Enterprise to the PLT.All feature provided by platform.