Skip to end of banner
Go to start of banner

User Profiles and Metadata Integration

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

User Profiles for Confluence is integrated with Metadata for Confluence. Therefore you can use the following functionality when both add-ons are installed on your Confluence.

Expert Filter Criteria (deprecated)

Whenever you can define expert filter criteria in Metadata for Confluence, you can get the value of certain user profile fields by using the placeholder upc.currentUser.<FIELDNAME>. This parameter works for all field types except multiselect and the About me field.

The following example shows the basic structure:

  •  metadatafield.site:upc.currentUser.Location

Here the field "Site" is managed in Metadata for Confluence, while the values of that field are stored in the field "Location" provided by User Profiles for Confluence (and most likely this will be synchronized from the user directory).

This way you can tailor the results of a Metadata Overview macro to the location the logged-in user is working at.

For more information on expert filter criteria, please refer to the documentation.

 

User Profile CQL integration (since Metadata Addon version 3.0.4 and User Profiles Addon 2.1.0)

The macros metadata-overview and content-by-metadata have a new parameter "User Profile Field Mapping". This parameter is shown if there is at least one metadatafield of type USERPROFILE assigned to a set in the confluence system. By selecting a field the macro automatically matches content with the same value as it is defined in the current users profile.

 

The new parameter "Expert filter criteria (CQL)" in the metadata-overview and content-by-metadata macro is now able to handle a metadatafield mapping with the current users profile. Here is an example

 MYEXAMPLESPACE.metadatafield.metadataprofilefield = upc.currentUser 

MYEXAMPLESPACE ist the spacekey of a metadatafield in side of this space. Because the metadatafield is mapped to a profile field CQL knows how to match these two.

 

 

 

  • No labels