Upgrading to 2022.5
- Lucas CORSINI
- Jill POUCHAIN
- Guillaume LEPICARD
- 1 NAR updates
- 1.1 Security changes
- 1.1.1.1 objectdata/update
- 1.1.1.2 objectactions domain
- 1.1.1.2.1 i18nFieldsTranslate(ADDED)
- 1.1.1.3 applications
- 1.1.2 Domains changes
- 1.1.2.1.1 isAvailable
- 1.1.2.2 boards
- 1.1.2.2.1 makePublicBoard
- 1.1.2.2.2 shareBoard
- 1.1.2.3 objectactions
- 1.1.2.3.1 broadcastVideo
- 1.1.2.3.2 create
- 1.1.2.3.3 damimport
- 1.1.2.3.4 datavaluespicker
- 1.1.2.3.5 defineVideoPoster
- 1.1.2.3.6 delete
- 1.1.2.3.7 editPicture
- 1.1.2.3.8 editVideoChapters
- 1.1.2.3.9 editVideoSubtitles
- 1.1.2.3.10 embed
- 1.1.2.3.11 manageVideoCallToActions
- 1.1.2.3.12 manageVideoRolls
- 1.1.2.3.13 massimport
- 1.1.2.3.14 multiupdate
- 1.1.2.3.15 order
- 1.1.2.3.16 shareSocialNetworks
- 1.1.2.3.17 sliceVideo
- 1.1.2.3.18 view
- 1.1.2.4 objectdata
- 1.1.2.4.1 broadcastVideo
- 1.1.2.4.2 changestatus
- 1.1.2.4.3 defineVideoPoster
- 1.1.2.4.4 delete
- 1.1.2.4.5 editPicture
- 1.1.2.4.6 editVideoChapters
- 1.1.2.4.7 editVideoSubtitles
- 1.1.2.4.8 embed
- 1.1.2.4.9 i18nFieldsTranslate
- 1.1.2.4.10 insert
- 1.1.2.4.11 manageVideoCallToActions
- 1.1.2.4.12 manageVideoRolls
- 1.1.2.4.13 order
- 1.1.2.4.14 retrieveCaption
- 1.1.2.4.15 shareSocialNetworks
- 1.1.2.4.16 sliceVideo
- 1.1.2.4.17 update
- 1.1.2.4.18 view
- 1.1.2.5 objectstruct
- 1.1.3 Macros changes
- 1.2 Structures changes
- 1.2.1 lang
- 1.2.1.1 Fields changes
- 1.2.2 objectfamily
- 1.2.2.1 Fields changes
- 1.2.3 pimasset
- 1.2.3.1 Object family
- 1.2.3.2 Tags
- 1.2.4 pimassettype
- 1.2.4.1 Object family
- 1.2.5 pkgroletemplate
- 1.2.5.1 Fields changes
- 1.2.5.2 Tags
- 1.2.6 product
- 1.2.6.1 Object family
- 1.2.7 productcategory
- 1.2.7.1 Object family
- 1.2.8 role
- 1.2.8.1 Fields changes
- 1.2.8.2 Tags
- 1.2.9 user
- 1.2.9.1 Fields changes
- 1.2.10 resolution
- 1.2.10.1 Tags
- 1.2.11 rubrique
- 1.2.11.1 Tags
- 1.2.12 vueapphomewidgettype
- 1.2.12.1 Tags
- 1.2.13 wkfmassimportitem
- 1.2.13.1 Tags
- 1.2.14 wkfmassimportjob
- 1.2.14.1 Tags
- 1.2.1 lang
- 1.3 Instances changes
- 1.3.1 In a nutshell
- 1.3.2 assetrighttype
- 1.3.2.1 assetrighttype/1
- 1.3.2.2 assetrighttype/2
- 1.3.2.3 assetrighttype/3
- 1.3.3 objectfamily
- 1.3.3.1 objectfamily/9999 (ADDED)
- 1.3.4 pkgroletemplate
- 1.3.4.1 pkgroletemplate/997 (ADDED)
- 1.3.4.2 pkgroletemplate/998 (ADDED)
- 1.3.4.3 pkgroletemplate/999 (ADDED)
- 1.3.5 role
- 1.3.6 rubrique
- 1.3.6.1 rubrique/10001
- 1.3.6.2 rubrique/10003
- 1.3.6.3 rubrique/10004
- 1.3.6.4 rubrique/10005
- 1.3.6.5 rubrique/10007
- 1.3.6.6 rubrique/10008
- 1.3.6.7 rubrique/10009
- 1.3.6.8 rubrique/10014
- 1.3.6.9 rubrique/10016
- 1.3.6.10 rubrique/10019
- 1.3.6.11 rubrique/10023
- 1.3.6.12 rubrique/10025
- 1.3.6.13 rubrique/10036
- 1.3.6.14 rubrique/10038
- 1.3.6.15 rubrique/10047
- 1.3.6.16 rubrique/10048
- 1.3.6.17 rubrique/10049
- 1.3.6.18 rubrique/10050
- 1.3.6.19 rubrique/10051
- 1.3.6.20 rubrique/10054
- 1.3.6.21 rubrique/10057
- 1.3.6.22 rubrique/10059
- 1.3.6.23 rubrique/10063
- 1.3.6.24 rubrique/10064
- 1.3.6.25 rubrique/10065
- 1.3.6.26 rubrique/10066
- 1.3.6.27 rubrique/10068
- 1.3.6.28 rubrique/10100
- 1.3.6.29 rubrique/10103
- 1.3.6.30 rubrique/10104
- 1.3.6.31 rubrique/10105
- 1.3.6.32 rubrique/10109
- 1.3.6.33 rubrique/10110
- 1.3.6.34 rubrique/10111
- 1.3.6.35 rubrique/10112
- 1.3.6.36 rubrique/10113
- 1.3.6.37 rubrique/10138
- 1.3.6.38 rubrique/10139
- 1.3.6.39 rubrique/10141
- 1.3.6.40 rubrique/10142
- 1.3.6.41 rubrique/10143
- 1.3.6.42 rubrique/10144
- 1.3.6.43 rubrique/10145
- 1.3.6.44 rubrique/10146
- 1.3.6.45 rubrique/10167
- 1.3.6.46 rubrique/10169
- 1.3.6.47 rubrique/10170
- 1.3.6.48 rubrique/10171
- 1.4 Plugins changes
- 1.4.1 In a nutshell:
- 1.4.2 PACKAGED_BOV3_DashboardWidgets
- 1.4.3 plugin.xml
- 1.4.4 PACKAGED_PortalAssetPickerSandbox (ADDED)
- 1.4.5 plugin.xml
- 1.4.6 PACKAGED_Security
- 1.4.7 plugin.xml
- 1.4.8 security.xml
- 1.4.9 WXM_ANALYTICS_V2
- 1.4.10 plugin.xml
- 1.4.11 WXM_Multiupload_Config
- 1.4.12 plugin.xml
- 1.1 Security changes
- 2 Portal upgrades
NAR updates
Security changes
FIX Security issue!
Previous rule WEDIA Packaged - Self user in objectdata/update did not prevent a user from changing its role. Find below new rule implementation
objectdata/update
WEDIA Packaged - Self user
Rule details
Description: A surfer can update its own user --> A surfer can update its own user as long as he doesn't change its role or role type
Old Expression:
@pkgIsSurferSelfUser()New Expression:
@pkgIsSurferSelfUser() AND object.role = surfer.roleid AND object.pkgroletemplate = surfer.pkgroletemplate
New objectactions domain action created: i18nFieldsTranslate
objectactions domain
i18nFieldsTranslate(ADDED)
Action description
Description:
Enabled: true
Action parameters:
objectname:
wsnoheto.securite.parameter.LowerStringParametersurfer:
wsnoheto.securite.parameter.SurferParameter
Rules:
WEDIA Packaged - Default rule
Rule details
Description: Relies on permissions granted to role
Enabled: true
Blocking: false
Expression:
@pkgV1ObjectActions('i18nFieldsTranslate')WEDIA Packaged - Developper
Rule details
Description: Developers can do everything
Enabled: true
Blocking: false
Expression:
Â
applications domain is now activated by default
applications
Enabled: false --> true
Â
Structures changes
Instances changes
In a nutshell
assetrighttypeinstances are now delivered with status 6 - so they are immediately visible by all usersobjectfamilyof ID 9999 is created → this will force families created by project to have a greater ID and leaves room for future product entries without conflictspkgroletemplateif IDs 1, 2 and 3 have been moved to IDs 997, 998 and 999. Again, this leaves room for future product entries.Some
rubriqueinstances have been deactivated (to keep only dam related menus)rubriqueof ID 10047 has its URL property change to access the wedia-config interfacerolehave been updated according to rubrique deactivations
Â
Plugins changes
In a nutshell:
PACKAGED_Security is configured to have parameter
enable_role_type_managementtotrue. This is required to enable role management UIWXM_RESTAPI is configured to have parameter
applyAggFieldBaseWherestotrue. This is required in regard to portal new security policy.UPDATE PACKAGED_BOV3_DashboardWidgets (So default pkgroletemplate widgets are matching new IDs)
ADDED PACKAGED_PortalAssetPickerSandbox (Sandbox for picker)
UPDATED PACKAGED_Security
role_template_default_permissions parameter default value updates
permissions_inferring parameter default value update
macro pkgV1ObjectActions(action) updated
Â
Portal upgrades
Important note : If you use a higher version of node v16.14.x, you must use npm i --legacy-peer-deps to update portal dependencies. If you still experience errors doing so, try to remove your package-lock.json file and re run the dependencies installation.
Disabling number of retrieved boards
Before 2022.5.0, it was not possible to retrieve more than 1000 shared boards and 5000 public boards. Even more, the limit had been set to 1000 shared boards and 1000 public boards.
It is now possible to bypass those limitations by setting some special values to /src/common/wedia-vue-helpers/initWediaVue/legacy.js
Future version of portal may change this default configuration, but as of 2022.5.0, it is an opt-in action.
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 :
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).
Â
Configuration to use new Profile form
You can now use a new form component in profile page, this component use faces and consistent form validation. This form is driven by the user object structure AND the portal configuration file. That means that all fields set as editable in structure will be retrieve by the form but this list will be filtered by what you specified in $profile.editablefields. If no editable fields are provided, all the field defined in structure will be displayed.
All other configurations are still used. If you want to keep the old form you’ll have nothing to do, to use the new form you’ll have to add $profile.useLegacy and set it to true.
If you use the new form you can configure your fields like any other fields in the portal application (by setting and customize $edit.profil.fields either by field names or by field types.
Â
New block layout replaces list layout
A new layout has been created for one of our clients and has now replaced the list layout in the search results page and on the board’s detail page (when displaying assets of a board).
The layout displays 4 assets each with metadata underneath but it can display up to 6 assets on very large screens.
A default metadata configuration has been created but this can be changed under $.common.namedDisplays.assetBlock.
If you would like to add the list layout in the search results page, you can configure it in $.dam.explore.layouts.defaultCursorConfig.defaultResourceConfig.
If you would like to add the list layout in the board’s detail page, you can configure it in $.board.explore.layout.available.