Versions Compared

Key

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

...

...

Overview

Portal Config

Warning

BREAKING CHANGE
All portal apps related JSON configs have been moved to another directory.

...

  • 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: BO Configuration checklist

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

  • permissions. (it is still possible to contribute and use rubrique)

  • Back-Office default widgets have been re-worked

Reference page: BO Configuration checklist

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.

Expand
titleSee default rules implementation in starter-kit for objectactions/view

WEDIA Packaged - Default rule

Code Block
@pkgV1ObjectActions('view')

WEDIA Packaged - Developper

Code Block
@pkgIsSurferDeveloper()

Macro @pkgV1ObjectActions('view') will grant users if they have at least one permission on the objectname

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.

Expand
titleSee default rules implementation in starter-kit for objectstruct/delete objectstruct/insert and objectstruct/update

objectstruct/delete

WEDIA Packaged - Default rule
Code Block
@pkgV1ObjectStruct('delete')
WEDIA Packaged - Developper
Code Block
@pkgIsSurferDeveloper()

objectstruct/insert

WEDIA Packaged - Default rule
Code Block
@pkgV1ObjectStruct('insert')
WEDIA Packaged - Developper
Code Block
@pkgIsSurferDeveloper()

objectstruct/update

WEDIA Packaged - Default rule
Code Block
@pkgV1ObjectStruct('update')
WEDIA Packaged - Developper
Code Block
@pkgIsSurferDeveloper()

Default NAR changes

Structures changes

asset

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

...

  • 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 BO Configuration checklist for detailed explanations.

...

  • 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.