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.
Metadata Fields of Type User Profile Element
since Metadata version 3.0.4 since User Profiles version 2.1
If the Metadata and User Profiles add-ons are both installed, you can use existing single- and multi-select user profile elements for metadata fields. This, for example, allows you to create a multi-select profile element "location" that holds all your company's locations and reuse it in a metadata field that defines which locations the information on a page is relevant to. When adding a new location, you only have to do it in the user profile element. It will be automatically available as a value for the metadata field.
To create such a metadata field, choose "User Profile Element" as the type. Afterward, select one of the suggested single- and multi-select user profile elements. If you don't see any suggestions, you will need to add a user profile element first. The created metadata field can be used in metadata sets like any other field. When assigning a value, you will see the options for the user profile element. If the user profile element is single-select, the metadata field will be single-select too.
To prevent unintentional data loss, it is not possible to delete a user profile element used in a metadata field. You will receive an error message when trying to do so. For the removal to work, you will have to delete the metadata field first.
Caution should be taken when editing user profile elements used in metadata fields when the metadata add-on is disabled or uninstalled. In this scenario, modifications such as deleting options or the entire element won't be tracked. This can lead to inconsistent metadata values if the metadata add-on is re-enabled or reinstalled later on.
User Profile CQL Integration
since Metadata version 3.0.4 since User Profiles version 2.1
The macros metadata-overview and content-by-metadata now include a new parameter, "User Profile Field Mapping". This parameter is displayed when at least one metadata field of type "User Profile Element" is assigned to a set in the Confluence instance. By selecting a field, the macro automatically matches content with the same value as it is defined in the current user's profile.
Alternatively, the Metadata fields of type “User Profile Element” can also be used in CQL conditions (for example, in the "Expert filter criteria (CQL)" option of macros metadata-overview and content-by-metadata), as shown in the following example:
MYEXAMPLESPACE.metadatafield.metadataprofilefield = "upc.currentUser"
MYEXAMPLESPACE is the key of a space in which a metadata field of type "User Profile Element" is defined. By using the special value “upc.currentUser”, the search will only return content with a metadata field value that matches the current user’s value of the user profile element linked to the metadata field. For more information about metadata CQL conditions, please refer to Searching with Metadata.
Related Articles
- SubSpace and Metadata Integration
- Query Page Status (Comala Workflows) alongside Metadata
- Import Fails: It is not possible to import metadata from space A into space B
- REST API, common errors and examples:
- Bulk change of global Metadata sets and fields.
- How to show all pages where Metadata field is empty
- We are getting too many Metadata notifications
- Configure the “Search Macro” from “Refined for Confluence” to use page metadata fields as search parameter
- Use status macro for single select values
- Error when I create a new Metadata field
- Space "Product Directory" keeps appearing on Confluence instance
- User Profiles and Metadata Integration
- Deleted user is not anonymized in metadata set
- No results in Metadata Overview with filters
- Does Metadata work with appfire's Comala Document Management Data Center (formerly Comala Workflows)