Configure table people attributes

In the Management Portal at Data Model > People Attributes, configure People Attributes. Configure table attributes to store multiple rows of data in a table structure.

You can use table people attributes for example in actions to direct the workflow or to personalize notifications. This is also very useful in integrations with third-party solutions like Mobile Device Management (MDM) systems.
You can link table service attributes to table people attributes.

Configuration

Field Explanation and Tips
Name
  • The Name of the attribute must be unique for all attribute types.
  • If the attribute is filled using a data connection:
    • the icon is displayed next to the attribute name, in the list on the People Attributes page.
    • the Data connection name is displayed on the attribute details page.
  • You can add a maximum of 32 columns.
    • Select the check boxes in the Required column to specify mandatory columns.
    • Select the check boxes in the Restricted Information column to mask the column values in the Management Portal.
      • Authorized administrators see the icon Eye-outline-vector-256-256 for restricted attributes and their placeholders. 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 Evil eye 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.
      This ensures you can be compliant with the privacy laws of your country or organization, by limiting 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.

Description

Specify a description for the people attribute that will make its purpose clearer to you. Usually a business logic reason.

Visible in Web Portal

Select this option to make your attribute visible in the person details view for Delegated Administration panels. This ensures that delegated users have an easier time identifying people that share similar characteristics, like identical first and last names.

If the attribute is marked as containing restricted information, the content will be hidden in the Management Portal and the Web Portal

Service Delivery Triggers

View which people attributes trigger a service delivery when you make changes to their value. The details page of each people attribute show a list of the services in which the person attribute is set as a delivery trigger.

Table Columns

  • Specify a column name.

  • You can add a maximum of 32 columns. If you only need 1 column, consider using the list people attribute.
    • Select the check boxes in the Required column to specify mandatory columns.
    • Select the check boxes in the Restricted Information column to mask the column values in the Management Portal.
      • Authorized administrators see the icon Eye-outline-vector-256-256 for restricted attributes and their placeholders. 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 Evil eye 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.
      This ensures you can be compliant with the privacy laws of your country or organization, by limiting access to private information like e-mail addresses, phone numbers, social security numbers, etc.
      This functionality applies to the Management Portal and the Web Portal.

When you configure the attribute values that apply to a person (on the Attributes tab of the Person page):

  • Mandatory columns are shown in red.
  • Click the arrows to configure the order of the rows.
  • Values are validated. If you use separators:
    • Pipe-characters ("|") are changed to a capital i ("I").
    • Semi-colons (";") are changed to a colon (":").
  • You can add a maximum of 512 rows.

Consider the following scenario:

  • People use multiple devices to interact in your environment.
  • You want to store the following information about these devices in a people attribute: device identifier, friendly name of the device, type of device, OS, phone number, and status.

With a table people attribute, you can store this information in the following format:

ID FriendlyName Type OS PhoneNumber Status
123-123-1234 S4 Phone Android 8008937810 Active
123-123-1235 iPad PDA iOS   Wiped

To retrieve data from the table, you can use the commands below. The commands are based on Subscriber, but they are also available for Requester and Actor:

Get the values of the entire table
Command #Subscriber[PA Table.FullTable] Notes: Column values are separated with “;”, rows with a “|”.
Example #Subscriber[MyMobileDevices.FullTable]
Returns 123-123-1234;S4;Phone;Android;8008937810;Active|123-123-1235;iPad;PDA;iOS;;Wiped

 

Get all values of the selected table row
Command #Subscriber[{attributename}.CurrentRow.FullRow]
Example #Subscriber[Devices.CurrentRow.FullRow]
Returns 123-123-1235;iPad;PDA;iOS;;Wiped

 

Get the value of a specific column in the selected table row
Command #Subscriber[{attributename}.CurrentRow.{columnname}]
Resolve the values of the table selection that was made with the Perform Table Operation action during a service transaction.
Example #Subscriber[Devices.CurrentRow.OS]
Returns iOS

 

Get the values of a table column
Command #Subscriber[PA Table.EntireColumn.C1]
Resolve the value of a specific column of the table selection that was made with the Perform Table Operation action during a service transaction.
Example #Subscriber[MyMobileDevices.EntireColumn.UUID]
Returns 123-123-1234 123-123-1235

 

Get the number of rows of a table
Command #Subscriber[PA Table.Number of rows]
Example #Subscriber[MyMobileDevices.Number of rows]
Returns 2

 

Get the description of the table
Command #Subscriber[PA Table.Description]
Example #Subscriber[MyMobileDevices.Description]
Returns "This table gives an overview of the mobile devices of the subscriber."
See also