Team Metadata for Teams
Configuration Users can now define structured fields that describe Teams, and Security Configuration users can enter the values for each Team. The values are available through the FenX APIs. Team Metadata is available to all clients.
Define Team fields. Add a Team Metadata card to Policy V2 and configure typed fields on the Requirement Details screen. Eight field types are supported, including data groups and linked dropdowns. Fields support a mandatory flag, a category, validations, trigger conditions, conditional values and references.
Enter values in Security Configuration. The Team configuration screen now has three tabs: Details, Permissions and Users. A single Save saves the changes made on all three tabs. The Metadata section on the Details tab shows the fields from the published schema. Mandatory fields must be completed before a Team can be saved.
Read and update values through the API. Team Metadata values can be read through the Query API and updated through the Command API.
Client adoption. Before assigning categories to Team Metadata fields, create a Reference Data list named Team Metadata Category.
Not included in this release. API filtering of Team Metadata attributes, journey and task assignment logic, and Team Metadata values in Journey Hub or entity profiles.
Permissions impact
New:
- Team Metadata Edit (
TeamMetadataEdit) allows a user to edit Team Metadata values on a Team. Editing in Security Configuration also requires Security Configuration Access and Security Configuration Edit. Without Team Metadata Edit, the Metadata section is read-only.
Check your Teams, and assign this permission to the Teams whose users should edit Team Metadata values. See the Permissions Catalogue.
User Guide Reference: Access Management Guide