...
PACKAGED_RegistrationEmails
| Warning |
|---|
BREAKING CHANGESNEW PROCESS In order to simplify the configuration of portal, some changes were introduced in the JSON configuration. Please read carefully |
dam.explore.workflows.statusesConfig
| Status | ||||
|---|---|---|---|---|
|
Statuses don’t need to be configured anymore. A status can be retrieved from the server
dam.explore.workflows.statusesSources
| Status | ||||
|---|---|---|---|---|
|
Statuses sources cannot be configured anymore. You still have the choice to display the status or not, but you cannot define from which metadata it is defined
dam.explore.indicators
| Status | ||||
|---|---|---|---|---|
|
Allows to configure icons that you want to display for an asset.
dam.explore.statusesOverride
| Status | ||||
|---|---|---|---|---|
|
Allows to override config received from the server
Example to override the color of the duplicate status :
| Code Block |
|---|
| [
address a security issue, the PACKAGED_RegistrationEmails plugin has evolved and might cause issue on your platform depending on your configuration and usage |
If your previous integration relied on workflow to create a user account (user) from a userrequest, you will need to adapt your workflow so that :
From the initial status (default value of property status in userrequest), there is an action “validate” that does not create the user, but moves the userrequest to a status “verified”, and changes the activated property to 1 (Published property of the workflow state)
From the “verified” step, there is an action that will trigger the user creation.
Portal config changes
| Warning |
|---|
BREAKING CHANGES In order to simplify the configuration of portal, some changes were introduced in the JSON configuration. Please read carefully |
dam.explore.workflows.statusesConfig
| Status | ||||
|---|---|---|---|---|
|
Statuses don’t need to be configured anymore. A status can be retrieved from the server
dam.explore.workflows.statusesSources
| Status | ||||
|---|---|---|---|---|
|
Statuses sources cannot be configured anymore. You still have the choice to display the status or not, but you cannot define from which metadata it is defined
dam.explore.indicators
| Status | ||||
|---|---|---|---|---|
|
Allows to configure icons that you want to display for an asset.
dam.explore.statusesOverride
| Status | ||||
|---|---|---|---|---|
|
Allows to override config received from the server
Example to override the color of the duplicate status :
| Code Block |
|---|
[
{
"rule": {
"operator": "in",
"path": "status.id",
"priority": 10,
"value": [14]
},
"status": {
"color": {
"name": "rgb(253, 217, 0)"
}
}
}
] |
...
rest_api_etag/staticStatus colour Green title ADDED
New Dataview Analytics view
The analytics view that you can reach from the dataview has been remodeled so that the design is now matching with the new Analytics view. On top of that, some graphics have been added so you can access more information now.
...
If you are on a video, the tabs on the left will change and you will be able to see other information such as the number of plays and it’s evolution through the period you selected.
...
New Analytics features
The overall performance of the Analytics has been greatly improved which lead to faster response times in the AnalyticsV2 screen.
In the “Internal Usage” section, many tabs has been added. Those tabs give you information about the different actions that have been performed in your DAM such as the creations of new assets, the modifications or the suppressions. All those tabs have the same structure :
...
New filters and graphics had beend added to the “Back-Office Search” dashboard.
New Back-office features
The expiration message of a session has been remodeled
When your session expired, a pop-up is now displayed and enables you to connect again directly by clicking on it.
...
New Boards features
Addition of a parameter to delay cart objects deletion
As now, as soon as a cart expired, there were a trigger that would delete the cart and all it’s linked objects (wxmcartshare and wxmcartlink). This behaviour led to the loss of many carts and linked objects, and it’s an huge work to rebuild all those objetcs. In order to avoid such situations we added a new parameter called deleteDelayAfterExpiration which enables you to delay the deletion of those objects.
...
Internationalisation of all the metadata from a cart
In the 2021.6 version, we added the internationalisation of the label of the assets in a cart. From now on, all the metadata from an asset which is included in a cart according to the current surfer.
Display the status of an asset in the cart
It’s now possible to display the current status of an asset in a cart. To achieve such an operation, you should add the wxmcart tag to the status field in the admin view
...
WXM_CART2
Now, when sendfile.security.enabled = true and security.share.impersonateAsUserId is set, the variations used to build the file are filtered by object.sendFile and the user identified by impersonateAsUserId when the user requesting the zip isn’t identified ( surfer.isConnected = false : the usual case for external shared zip ).
...
That was not the case before this release. object.sendFile was applied with the user requesting the zip.