Page tree
Skip to end of metadata
Go to start of metadata

The PrimaryDOAutorization is now supported for ribbons and toolbars.
For blocks, visibilityRules can be specified on the MenuStructure level and for items it can be defined in the MenuFunction visibilityRules.

The provided list of tokens is handled like any other OpenEdge CAN-DO list.

Examples
{ "PrimaryDOAuthorization": "CanCreate" }
{ "PrimaryDOAuthorization": "CanDelete" }
{ "PrimaryDOAuthorization": "CanModify" }
{ "PrimaryDOAuthorization": "CanFetch" }
{ "PrimaryDOAuthorization": "CanSaveChanges" }
{ "PrimaryDOAuthorization": "Can*" }

It will check for the TABLEIO:SRC, which could be the form, and from that form it will read the DISPLAY or DATA link of that form.
From the BE of the form it will read the catalog SecurityRestrictions and apply the visibiltyRules based on that.
There is one limitation in this version, it only works with one BusinessEntity.

Requirement: Setting in SCL configuration file, ( .applicationsettings, .restapplicationsettings files) "UseDetailedRequestAuthorizationOnUpdate": true

Steps to follow

Step 1:
In SCL Menu Function maintenance, select a menu function and in the Visibility rules add {"PrimaryDOAuthorization":"CanCreate"} or {"PrimaryDOAuthorization":"CanCreate,CanDelete,CanModify"} (based on the needs)

Step 2:
From the designer, Links tab, create a TabelIO link from the Ribbon to Form (the form must be linked to a data source so it gets the security restrictions from the catalog)

Step 3:
In the Smart Security Object Maintenance
Create a new record with the name of the BE and add the Tokens for the needed actions

Step 4:
Create a Security Assignment Maintenance new record, new SOT, select the defined records from step 3


Note

restart PASOE (after each change)

  • No labels