Profile Field Type: Dependent Field
Why should I use profile field type Dependent field?
It converts any profile field (for example an alphanumeric code) to any output (for example readable text).
This field type is not editable for users.
Special configuration
Navigate to the Depending on section.
First, select an existing field which your new field will depend on.
Then, in the left field, enter the value of the dependee (the existing field).
In the right field, enter the value of the dependent (the new field you are creating).
Click on the + button to the right.
Optional: Add more dependencies and follow the steps above. Remember that all dependencies you add refer to the one profile field you selected above.
Please note: Dependent fields update automatically when the dependees change. Unfortunately it can happen that this does not work in single cases.
To fix dependent field values for all users you can run the LUP: Bulk profile update (dependent fields) job.
To do this go to the “Scheduled Jobs” section in Confluence administration. There you need to run LUP: Bulk profile update (dependent fields).
Edge Case: Depending On Groups (confluence.groups)
Confluence group names as Field Values (like the default group confluence-users) that should be associated with a new Target Value need to be set between wildcard characters *
Example: confluence-users → *confluence-users*
Use wildcards and logical operators to create more complex filters
Why should I use wildcards and logical operators?
Because the source format can take on multiple values, you have to add wildcards and logical operators in the menu structure, if you plan to use this for the personalization of the menu. You can get more info on wildcards and logical operators here.
Link to this page: https://seibert.biz/fieldtypedependentfield
