Specify Custom User Attributes
This applies to: Visual Data Discovery
You can define and manage custom user attributes in the Symphony interface. This article covers updating user attributes in Visual Data Discovery.
Note: For more information about Custom User Attributes in Managed Dashboards & Reports, see Add a Custom Attribute.
If you are hosting users who connect solely to embedded Visual Data Discovery content as trusted access users in a specific tenant, use the Custom User Attributes enumerated here to define what your users can access and what they see. This requires use of the trusted access method of Pull for user information and connection.
If you use the trusted access method of Push for user information and connection, custom attributes must be set using the API. API documentation is provided in your environment at this link:
<symphony-URL>/discovery/swagger-ui.html.
Supplied Context Variables
The following context variables are provided with Symphony.
${User.composerUserName}: include to insert the name of the user who is currently logged in.${User.accountId}: include to insert the user account ID of the user who is currently logged in.${User.credentials}: include to pass the session ID or trusted access token (in embedded environments) of the user.
You do not need to create custom user attributes for the user name or account ID. Use these supplied context variables instead.
Add A Custom Attribute for a User in Visual Data Discovery
Add a custom attribute for a user
Access the Custom Attributes tab for the user. See Modify Users.
Select Add Custom Attribute. A blank line is added to the Custom Attributes tab.
-
Supply values for the attribute, as described in the following table:
Tab Field Description Key
Specify the name of the custom attribute. The name cannot include braces.
Value
Specify one or more values for the custom attribute. See below for more options.
Usage
Shows how the attribute appears in the text entry fields of the application.
Secure
Select this checkbox if you want to encrypt the custom attribute values.
Delete
Select the delete button to remove the attribute.
When you have specified all values, select Save to save the user.
Remove a Custom Attribute from a User
Remove a custom attribute from a user
Access the Custom Attributes tab for the user. See Modify Users. The defined custom attributes are listed.
Select the delete button corresponding to the attribute you want to remove.
When are done removing your specific attributes, select Save to save the user.
Specify Multivalue (Array) Custom Attributes
For multivalue user attributes (arrays), the elements must be comma-separated and contain no redundant white spaces between elements. These multivalue custom attributes should only be used as arrays in INCLUDE and EXCLUDE filter operations. With all other filter operations, the custom attribute values are used as-is.
For example, an INCLUDE or EXCLUDE row security filter that uses a multivalue custom attribute containing the array (["apples", "oranges", "bananas"]) will interpret the values as three separate values, splitting the values on commas.
However, an EQUAL or NOT EQUAL row security filter using the same multivalue custom attribute would interpret the array values as a single value ("apples,oranges,bananas").
Null values in multivalue custom attributes are processed as a special text marker - [Null].
Specify Numeric Values in Custom Attributes
Numeric value in custom attributes are supported as integers or floating-point values represented as text.
Specify Time Values in Custom Attributes
For date-time values, the following formats are supported:
ISO-8601 format with optional milliseconds (but no timezone):
yyyy-MM-ddTHH:mm:ss[.SSS]Symphony's default API time format:
yyyy-MM-dd HH:mm:ss.SSS, milliseconds required.
Unix time stamp format (seconds/milliseconds) is not supported for date-time values.
The BETWEEN filter operator expects an array with two elements.
When you use a time-value custom attribute as a filter variable for a filter using BETWEEN, two explicit elements must be specified (for example start_date and end_date). The dates can be specified as static date-time values, dynamic time patterns, or single-value user attributes.
Specifications such as [${User.date_array}], with the date_array attribute containing two elements are not supported.
Comments
0 comments
Please sign in to leave a comment.