Portal Config
...
PACKAGED_BOV3_DashboardWidgets
Default configuration of this plugin
...
title | See changes in plugin.xml |
---|
Parameters:
UPDATED configured_widgets:
default value:
Old:
...
language | json |
---|
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 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.
plugin.xml
Expand | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||
|
...
PACKAGED_BOV3_Extensions (ADDED)
plugin.xml
Parameters:
list.display.config:
...
type: json
...
mandatory: true
...
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:
Code Block language json [ { "families": [ "dam.metadata.opened" ], "i18n": "pkg.bov3.manage-opened-list" }, { "families": [ "dam.metadata.closed" ], "i18n": "pkg.bov3.manage-closed-list" } ]
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:
Code Block language json asset
New:
Code Block language json #damobject
...
PACKAGED_Faces (ADDED)
This plugin
...
Parameters:
provides 2 Faces
One that make fields with tag
pkg/wediaconfig/custom/archived
non editable, non visible and compulsoryOne 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 mandatorydefault 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
tagdefault 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_PROJECTdefault 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
:
PACKAGED_Security
Code Block |
---|
type:
int
mandatory:
false
description: Level of priority for the faces created by the program.
Set to 1000 by default equals to LEVEL_PROJECTdefault value:
1000
| ||
{
"class": "com.wedia.packaged.security.inferring.impl.ApplicationsInferenceProvider",
"init": {
"": [
"v1/applications/isavailable/wedia-config"
]
}
} |
plugin.xml
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
...
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
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.