This is not the latest version of Identity Director documentation.
View available documentation.

Configure text service attributes

In the Management Portal at Entitlement Catalog, on the Attributes tab of the service page, configure text attributes to store a text value.

Configuration

Field	Explanation and Tips
Restricted information	Mask the attribute value in the Management Portal. This ensures you can be compliant with the privacy laws of your country or organization, as unauthorized administrators do not have access to private information like e-mail addresses, phone numbers, social security numbers, etc. This functionality applies to the Management Portal only; restricted information is still shown in the Web Portal. Authorized administrators see the icon for restricted attributes and their placeholders anywhere in the Management Portal. They can click this icon to view their value. These values are hidden again when the page is refreshed. This prevents situations in which unauthorized administrators can view restricted information by shoulder surfing authorized administrators. Where appropriate, a button is available to view ALL restricted attributes at once. Unauthorized administrators see the icon for restricted attributes and their placeholders. At Transactions, restricted attributes are shown as [attributename]. Although unauthorized administrators cannot see the attribute value, this still allows them to verify if the context or definition of the attribute is correct. You can set administrative permissions on this functionality. The value is also restricted if it is determined by a restricted service attribute, people attribute or people identifier.
Initial value	Optionally, specify a default value of the service attribute. Select Text to specify a manual value. You can also create a combination of a manual value and attributes and functions. If you specify another service attribute as initial value, and this attribute has an empty value at the start of the transaction, the initial value cannot be resolved. For example, if you have configured a service attribute Fullname with initial value #Service[Lastname],#Service[Firstname], the initial value cannot be resolved if the values of the attributes Lastname and Firstname are empty at the start of the transaction. You can only do this with a Set service attribute workflow action and set the service attribute Fullname after the attributes Lastname and Firstname receive their value. Select Person identifier / Person attribute to base the initial value on an existing people identifier or people attribute. If you select a person identifier as initial value, ALL values related to the identifier are resolved. For example, if a subscriber has multiple records for a people identifier E-mail address, all values are resolved. This may result in a service attribute value of e.g."[email protected];[email protected];[email protected]". Select Service Attribute to base the value on a service attribute of another service. The subscriber to the current service must already subscribe to the other service before the value of its service attribute can be resolved. If you select an organization service attribute, the initial value is the key of the organizational context item. The value is limited to 2000 characters.

Field

Explanation and Tips

Restricted information

Mask the attribute value in the Management Portal. This ensures you can be compliant with the privacy laws of your country or organization, as unauthorized administrators do not have access to private information like e-mail addresses, phone numbers, social security numbers, etc. This functionality applies to the Management Portal only; restricted information is still shown in the Web Portal.

Authorized administrators see the icon for restricted attributes and their placeholders anywhere in the Management Portal. They can click this icon to view their value. These values are hidden again when the page is refreshed. This prevents situations in which unauthorized administrators can view restricted information by shoulder surfing authorized administrators. Where appropriate, a button is available to view ALL restricted attributes at once.
Unauthorized administrators see the icon for restricted attributes and their placeholders. At Transactions, restricted attributes are shown as [attributename]. Although unauthorized administrators cannot see the attribute value, this still allows them to verify if the context or definition of the attribute is correct.
You can set administrative permissions on this functionality.
The value is also restricted if it is determined by a restricted service attribute, people attribute or people identifier.

Initial value

Optionally, specify a default value of the service attribute.

Select Text to specify a manual value. You can also create a combination of a manual value and attributes and functions.
- If you specify another service attribute as initial value, and this attribute has an empty value at the start of the transaction, the initial value cannot be resolved. For example, if you have configured a service attribute Fullname with initial value #Service[Lastname],#Service[Firstname], the initial value cannot be resolved if the values of the attributes Lastname and Firstname are empty at the start of the transaction. You can only do this with a Set service attribute workflow action and set the service attribute Fullname after the attributes Lastname and Firstname receive their value.
Select Person identifier / Person attribute to base the initial value on an existing people identifier or people attribute.
- If you select a person identifier as initial value, ALL values related to the identifier are resolved. For example, if a subscriber has multiple records for a people identifier E-mail address, all values are resolved. This may result in a service attribute value of e.g."[email protected];[email protected];[email protected]".
Select Service Attribute to base the value on a service attribute of another service.
- The subscriber to the current service must already subscribe to the other service before the value of its service attribute can be resolved.
- If you select an organization service attribute, the initial value is the key of the organizational context item.
The value is limited to 2000 characters.

You can force mandatory input by enabling Attribute may not be empty after workflow input from actor.

Example initial value based on service attribute of another service

Consider the following scenario:

You configure a service A with service attribute 1. Its initial value is "XYZ".
You configure a service B with service attribute 2. Its initial value is service attribute 1.

Results after a person subscribes to service B:

If he does not subscribe to service A, the initial value of service attribute 2 is empty.
If he subscribes to service A, the initial value of service attribute 2 is "XYZ".
If the value of service attribute 1 is based on a placeholder, the initial value of service attribute 2 may be different for each subscriber.

Placeholders

When you insert a text service attribute as a placeholder in actions, you can retrieve its value:

Placeholder	Explanation
#Service[{attributename}]	Resolve the value of the attribute.
#Service[{attributename}.Description]	Resolve the description of the attribute.

Configure text service attributes

Configuration

Example initial value based on service attribute of another service

Placeholders

See also