Defining custom attributes

Name

Description

ENUMERATION

Displays an additional panel where the limited list of values should be provided. Accepts only these pre-defined values.

NUMERIC

The value is a numerical value.

TEXT

Accepts any value and converts it into strings.

EMAIL

Accepts email values and maintains their verification status.
Once a value is entered in an attribute of Email, its status is set to PENDING. This is indicated by a warning icon next to its name. A verification email (personalized via templates) is sent. Once the email has been successfully verified, its status is set to VERIFIED. This is indicated by a green check icon next to its name,

HASH

The value is hashed upon storage and is thus rendered unreadable. For every user a different (unique) salt hash is applied.
SHA-256 and SHA-512 algorithms are available.

SEARCHABLE_HASH

The value is hashed upon storage and is thus rendered unreadable. Uses the same salt hash for every user. This makes it possible to search for hashed values.
SHA-256 and SHA-512 algorithms are available.

SMS

Attribute used specifically for SMS communication (eg. to send a One-Time Password)

JSON

The value of the attribute is in a JSON format

Name

Description

Single Value

There can only be one value for this Attribute type for any user
For example “Date of birth” needs only one value.

Required

A value for this attribute is mandatory (indicated by asterisks).
A warning message will be displayed if an attempt is made to save without a value for this attribute.

Read Only

The attribute has Read Only permission. It cannot be updated from the Self Service Portal. It can be updated from the Admin Portal.

Hidden

The attribute and its value will not be visible in Self-service Portal.

Override

The value of the attribute in the TrustBuilder repository (if a value exists) takes priority over a value returned by an IDP for that attribute.

System

The system attributes are defined and configured when the application is first launched. A system attribute cannot be deleted.

Unique

Derived

Derived attributes are linked to a workflow by a workflow ID property which is specified in the principal attribute definition screen. The value of the attribute is obtained by executing the specified workflow.

The selected workflow will be executed for all schemes when no schemes are selected in the configuration.

The result of the workflow is expected in the following JavaScript structure:

<<subtype_name>: {
	<attr_name>: ["value1", ... ,"value3"],
	...
	<attr_name>: ["value1", ... ,"value3"]
}
...
<subtype_name>: {
	<attr_name>: ["value1", ... ,"value3"],
	...
	<attr_name>: ["value1", ... ,"value3"]
}

Where the values assigned to each attr_name has to be an array (even if it only contains one value)

As an example, the following workflow script produces a value for the attribute Full Name by concatenating the First Name and Last Name attribute values of the principal.

function getFullNameValues(workItem){
	var fn = workItem.input.value.attributes.common.firstName[0];
	var ln = workItem.input.value.attributes.common.lastName[0];
	var fullname = fn + " " + ln;
	var fullname_str = JSON.stringify(fullname).replace(/\"/g, "");
    workItem.output = tb.simpleResponse({
		common: {
			fullname: [fullname_str]
		}
	});
}

Please note that the names of custom attributes must be lowercase and without underscores, hence the name of the custom attribute in this example is fullname.

The workflow function is given an object as parameter, called workItem in this example, that contains the principal object (accessed via workItem.input.value) and where the output of the workflow must also be stored, in workItem.output. As shown in the example above, the output object can be created using tb.simpleResponse and passing as parameter a JavaScript object with the correct structure.

Finally, since the returned values have to be in JSON format, the fullname attribute is converted into a JSON string by the JSON.stringify method and the backward slashes \ created by the conversion are removed.

Approval policy

Displays an additional panel where statements should be added. Configure the statements to define who is allowed to approve the change requests.
See Manage policies