Overview

Portal Config

All portal configs from portal/src/wedia-plugin-template/res have been moved to portal/src/wedia-portal-apps-configs

Therefore all project configs directories MUST be moved to the new directory (portal/src/wedia-portal-apps-configs) too

Portal server-side’s style

This upgrade will allow portal to have a server-side generated style. This will be used to switch portal colors from wedia-config.

New “default” configuration for the detail page of an asset in Portal

Portal detail pages can now display metadatas based on the configured structure of the asset library.

Then, the display in Portal becomes the same as in Back-Office : all fields of the library where the asset is attached and that have its property visible set to true will be displayed in the order defined by their property"“index"”.

Section titles are defined by a field with name starting by “separator_”.

To enable this behaviour, you have to set $dam.details.defaultCursorConfig.defaultAssetDetailMeta.column[].tabs[].auto to true and $dam.details.defaultCursorConfig.defaultAssetDetailMeta.column[].tabs[].config should not be an array anymore (this becomes the default configuration in starter-kit).

In both modes (auto or manual) only metadatas with corresponding data are displayed.

Reference page : Asset details page

Back-Office changes in starter-kit

starter-kit settings for the Back Office have changed :

• Menu entries (rubrique) for DAM and Administration have been deactivated as we now provide an automatically generated menu based on permissions. (it is still possible to contribute and use rubrique)

• Back-Office default widgets have been re-worked

Reference page: Backoffice - Widgets and menus

Emails

An important upgrade has been made for all the emails sent by the application. Existing projects should not be affected.

Here is the link to the page which explains the upgrade, the new behaviour and how it’s working with the old way of customizing emails : Email templates & customization

Security

Domain objectactions

This domain is now activated by default. It is recommended to activate it.

An action view has been added. Its purpose is similar to other objectactions’s actions: define if a user is granted to view a type of object. This action is used to generate the menu.

Domain objectstruct

This domain is now activated by default. It is recommended to activate it. It is mandatory to activate it to enable structures management from the wedia-config interface.

Default NAR changes

Structures changes

asset

Field dteendrights no longer has pkg/wediaconfig/custom tag as it is considered as a system property

Fields changes

• dteendrights

  • Tags:

    • Removed: pkg/wediaconfig/custom

• source

  • Tags:

    • Added: rest_api_include

pimasset

Fields changes

• source

  • Tags:

    • Added: rest_api_include

pkgsecugroup

The rule that was setting object selector as mandatory has been removed as more permissions are not object related.

Faces

pkgsecupermission

Permission added to list as list of permission is only accessed by developers who are keen to see the permission technical definition

Fields changes

• permission

  • In list:
    false --> true

lang

Added tag so lang object is accessible through wedia-config screens

Tags

Added

• rest_api_include/appsettings

Instances changes

pkgroletemplate

resolution

Resolution instances were lacking translations.

role

Default menu has changed for many roles

rubrique

BO menu has been reorganized and many instances deactivated because menu is now automatically generated based on permissions

Plugins changes

PACKAGED_Appearance_Config (ADDED)

This plugin will bring new endpoints allowing to read and write logos and colors in the san

PACKAGED_BOV3_DashboardWidgets

Default configuration of this plugin has changed since last version :

• configured_widgets A new syntax is available to define criteria for querying instances to display inside a widget.
  Before, you would define a query entry. This property is deprecated, but is still understood by the plugin.
  Now, you will define a filters entry. Filters entry uses the same syntax as /bov3/datalist/preload.jsp uses.
  It is recommended to update your current configuration so that links are available within each widgets.

• remove_widgets By default, listAssetsCall2Action widget is now removed:

  • It came with an image that was not configurable easily

  • It didn’t bring much business value

• default_widgets Roles no longer include listAssetsCall2Action widget

• default_roletemplate_widgets: Role templates no longer include listAssetsCall2Action widget

See Backoffice - Widgets and menus for detailed explanations.

plugin.xml

PACKAGED_BOV3_Extensions (ADDED)

This plugin provides 2 features:

• A new form_action=managelists (without form_object parameter). The related page will display the list of data-types the connected user is allowed to take actions on. Data-types are organized per familly.

• The ability to generate the BO menu for dam domain automatically based on user’s permissions.

This plugin is required when some business users are allowed to make changes to the data model: it will adapt the menu for each connected user based on his granted permissions.

plugin.xml

• Parameters:

  • list.display.config:

    • type: json

    • mandatory: true

    • description: Configuration of lists to display.
      families parameter can take following values : objectfamily.id, objectfamily.name, or a sql query on name field (eg: dam.metadata.%).
      Families can be combined to be displayed in the same table.

    • default value:

  • list.security.actions:

    • type: string

    • mandatory: false

    • description: Define actions of domain objectactions used to apply security rules on list families content.
      Actions can be multiple and separated by a comma.
      A list object will be displayed if it is authorized by any action
      No security rule will be applied if parameter is empty or action is unknown.

    • default value: create,multiupdate

  • enable_auto_menu:

    • type: boolean

    • mandatory: false

    • description: Enable auto generated menu

    • default value: true

  • auto_menu_items:

    • type: string

    • mandatory: false

    • description:

    • default value: dam,admin,analytics

PACKAGED_DAM_DashboardWidgets

Widgets provided by this plugin (including listAssetsCall2Action) now support multiple objects through wedia_packaged_dam_dashboard_asset_objectname parameter.

This will make sure every dam collection can be handled by the widgets.

plugin.xml

• Parameters:

  • UPDATED wedia_packaged_dam_dashboard_asset_objectname:

    • default value:

      • Old:

      • New:

PACKAGED_Faces (ADDED)

This plugin provides 2 Faces

• One that make fields with tag pkg/wediaconfig/custom/archived non editable, non visible and compulsory

• One that make fields with tag pkg/wediaconfig/custom/mandatory mandatory

This plugin is required if business users are allowed to manage the data-model: Fields created through the new wedia-config data-model screens are made mandatory only with the tag pkg/wediaconfig/custom/mandatory

plugin.xml

• Parameters:

  • apply_archived_tag_faces:

    • type: boolean

    • mandatory: true

    • description: If set to true, the program will apply hide fields wearing
      pkg/wediaconfig/custom/archived tag by making them non visible, non editable and non mandatory

    • default value: true

  • apply_mandatory_tag_faces:

    • type: boolean

    • mandatory: true

    • description: If set to true, the program will apply mandatory faces on field wearing
      pkg/wediaconfig/custom/mandatory tag

    • default value: true

  • face_level:

    • type: int

    • mandatory: false

    • description: Level of priority for the faces created by the program.
      Set to 1000 by default equals to LEVEL_PROJECT

    • default value: 1000

PACKAGED_Security

The plugin default configuration for property permissions_inferring has been update to add infered permissions to wedia-config application based on user’s permission (if the user has permission to manage one feature that is available in wedia-config screens, then he is granted access to the interface).

Added item in permissions_inferring:

plugin.xml

security.xml

WXM_BO_Options

plugin.xml

• Parameters:

  • ADDED com.noheto.waf.DetectSlowPostHttpServletRequest.Options.MaxMilliseconds:

    • type: integer

    • mandatory: false

    • description: Maximum number of milliseconds that file reception can take in POST. If 0 then no limit.

    • default value: 0

  • ADDED com.noheto.waf.DetectSlowPostHttpServletRequest.Options.MaxMillisecondsBetweenTwoCall:

    • type: integer

    • mandatory: false

    • description: Maximum number of milliseconds between two byte receptions during a POST. If between two bytes, the time is exceeded then it is considered an attempt to ''deny'' service. If 0 then no limit.

    • default value: 5000

  • ADDED com.noheto.waf.DetectSlowPostHttpServletRequest.Options.MinOctetsBySecond:

    • type: integer

    • mandatory: false

    • description: Minimum bandwidth in bytes/seconds below which the connection will be considered as a service ''deny'' attempt and therefore cut. If 0 then no limit.

    • default value: 100

WXM_IA_CUSTOM_LABELS

plugin.xml

• Parameters:

  • ADDED mappingPresenceIdentifiable:

    • type: string

    • mandatory: false

    • description: Liste des labels ,en anglais, qui indiquent une présence identifiable

    • default value: Face

  • UPDATED variation:

    • default value:

      • Old:

      • New:

security.xml

WXM_MEDIACLOUD_V2 (ADDED)

plugin.xml

• Services:

  • com.wedia.mediacloud.LifeCycle (com.noheto.extensions.interfaces.services.IPluginLifeCycleBusinessService)

  • com.wedia.mediacloud.cloudApi.CloudRestAPI (com.noheto.extensions.interfaces.services.AbstractPluginApiService)

Plugins Config changes

PACKAGED_Appearance_Config

• Activated:

  • true

PACKAGED_BASES

This plugin HAS to be activated if business users are to configure portal through wedia-config

• Activated:

  • true

PACKAGED_BOV3_Extensions

• Activated:

  • true

PACKAGED_CONFIGS

This plugin HAS to be activated if business users are to configure portal through wedia-config

• Activated:

  • true

PACKAGED_Faces

• Activated:

  • true

Security changes

Domains changes

objectactions

• Enabled: false --> true

objectstruct

delete

• Rules:

  • WEDIA Packaged - Default rule

insert

• Rules:

  • WEDIA Packaged - Default rule

update

• Rules:

  • WEDIA Packaged - Default rule

RESTAPI DAM/DATA & metadata configuration in wedia-config

When using metadata editing in wedia-config on a production server, in order for the DAM & DATA API configurations to synchronize with the structure changes, it is necessary to activate the automatic hot update of the API configurations by setting the lazyDeployDamServicesInProd parameter of the WXM_RESTAPI plugin to true. Otherwise, the API configurations will reflect the metadata changes only after restarting the WXM_RESTAPI plugin.