Changing the Display Name pattern for user creation in Atria

How to Customize Display Name Patterns


By default, Atria's Display Name Pattern is set to First Name Last Name format.  This is used to default the Display Name when creating new users.
This guide shows how to customize Display Name Patterns in Atria to meet the needs of individual customers.

The Display Name field in Active Directory and Azure Active Directory is shown in the Outlook Global Address book as 

Default Configuration

Under the Customer > Advanced Properties, the default Pattern is set to FirstName LastName when provisioning new users

Example (User Provisioned)

Example - Adding a standard Suffix to the Display Name

Certain requirements requires a standard suffix on the User's Display Name. This needs customizing the Display Name Pattern that is set.
This is configured as an advanced properties for each customer.

Steps on Customizing the Display Name Pattern

1. In Atria Menu, Navigate to Configurations > Validation

If the User Full Name (Display Name) is planned to have a special character, then we need to make sure that the regular expression validation for it is configured.
2. On the Validations page, change the filter to Regular Expression

From this, look for the "User Full Name" expression and update it with the special character needed (if still missing)

3. After the User Full Name regular expression is set, we can now set the Display Name Pattern. Change the Validation Filter to Drop Down List

From this, look for the "UserDisplayPatterns" and add a new drop down option and based on the pattern you want it to be customized
(example below is that the Display Name Pattern will be appended with | Custom)

4. After configuring the validations, navigate to the Customer that will have this specific Display Name Pattern. On the customer, edit it and navigate to Advanced Properties
Note that this configuration needs to be applied to individual customers
Select the User Display Name Pattern. Then Provision the Customer.

5. Now after provisioning, when creating a new user, the custom pattern should be appended.

For any questions or assistance needed, feel free to contact Automate101 Support -

    • Related Articles

    • Display Patterns for Billing Line Descriptions

      Purpose: When generating billing data, two descriptions are generated for each billable item - Line description (detailed) and summary descriptions.   The Summary Description serves two purpose: Used as a template for your invoice lines and reporting ...
    • HOW TO : Configure Atria to have a freeform Company Name attribute for users.

      Users in Active Directory and Azure AD have an attribute called Company.  By default, Atria will automatically populate this value with the Customer Name field from Atria.  With default configuration, this means that on importing users with the AD ...
    • Adding a Remote Dedicated Customer

      Overview In Atria V15, we now have the ability to manage Private Active Directory's. Customers who have their own AD Infrastructure, gain the same self service and management capabilities of Atria that have worked so well for multi-tenant Active ...
    • Atria API User Guide (CortexAPI)

      Overview The application programming interface (API) is a powerful interface that allows you to interact directly with Atria without using the ATRIA Web User Interface (UI).  The API grants a user, with some development knowledge, the ability to ...
    • Billing Rules Engine User Guide

      Objective This article describes how to use the Atria billing rules engine to identify specific Atria entities as non-billable.   Applies to Introduced in Atria version 12.0.0 Billing Rule Feature Overview Many entities - customers, services, users, ...