Upgrading to 2022.5

Portal configuration for upload feature

The upload feature can now be handled by the security. To use this mechanism, the $feature.action must be configured with an object instead of a boolean.

Model of the configuration object :

// With a named shema
{
  "schemaSecurity": {
    name: "damImportTarget",
    security: "objectactions/create"
  }
}

// Without named schema
{
  "schemaSecurity": {
    name: "dam/asset",
    security: "objectactions/create"
  }
}

We’ve added the possibility to create namedSchemas for reusability purpose.

security value is the rule you want to test to enable (or disable) the feature.

This configuration enable the possibility to control more precisely who can access to the feature. A user without access to the upload feature will not see the link to the upload page in the menu, nor in the header.

This method will now be recommended instead of the usage of onlyForUserGroups in the configuration of the upload link in the menu ($menu.actionsAvailabled).