...
...
Overview
Portal Config
Warning |
---|
BREAKING CHANGE |
...
This upgrade will allow portal to have a server-side generated style. This wil will be used to switch portal colors from wedia-config.
...
New “default” configuration for the detail page of an asset in Portal
The configuration entry $dam.details.defaultCursorConfig.defaultAssetDetailMeta.column[i].tabs[n].auto
is introduced and allow to handle the displayed fields automaticallyPortal 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"“inde“index"”. Therefore the configuration entry $dam.details.defaultCursorConfig.defaultAssetDetailMeta.column[i].tabs[n].config
is not taken into account anymore when auto = true.
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[i].tabs[n].auto
is set to true
by default to true
and $dam.details.defaultCursorConfig.defaultAssetDetailMeta.column[].tabs[].config
should not be an array anymore (this becomes the default configuration in starter-kit configuration).
In both modes (auto or manual) only metadatas with corresponding data are displayed.
...
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
Structures changes
...
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 | ||||
---|---|---|---|---|
| ||||
WEDIA Packaged - Default rule
WEDIA Packaged - Developper
Macro |
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 | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
objectstruct/deleteWEDIA Packaged - Default rule
WEDIA Packaged - Developper
objectstruct/insertWEDIA Packaged - Default rule
WEDIA Packaged - Developper
objectstruct/updateWEDIA Packaged - Default rule
WEDIA Packaged - Developper
|
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
...
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
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||
pkgroletemplate/997
pkgroletemplate/998
pkgroletemplate/999
|
...
resolution
Resolution instances were lacking translations.
Expand | ||
---|---|---|
| ||
resolution/1
resolution/2
resolution/3
resolution/4
resolution/5
resolution/6
resolution/7
resolution/8
resolution/9
resolution/10
resolution/11
resolution/12
resolution/13
resolution/15
resolution/16
resolution/17
resolution/18
resolution/19
resolution/20
resolution/21
resolution/22
resolution/23
resolution/24
resolution/25
|
...
role
Default menu has changed for many roles
Expand | ||
---|---|---|
| ||
role/4
role/27
role/28
|
...
configured_widgets A new syntax is available to define criteria for querying instances to display inside a widget.
Before, you would define aquery
entry. This property is deprecated, but is still understood by the plugin.
Now, you will define afilters
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
widgetdefault_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.