When an instance of eAdm contains a large number of message templates—sometimes over 200—it is essential to use a proper naming standard to maintain clarity and organization.

We recommend the following two-part convention to structure your message flow names.


Part 1: Identify the Recipient with a Prefix

Start the name with a prefix that identifies the primary recipient or the object the message concerns.

Prefix: AVD  |  Recipient / Object Type: Department Information

Prefix: ANS  |  Recipient / Object Type: Employee

Prefix: IKT  |  Recipient / Object Type: IT Department

Prefix: HR  |  Recipient / Object Type: HR and Payroll

Prefix: LED  |  Recipient / Object Type: Manager

Prefix: MAN  |  Recipient / Object Type: Manual User Accounts

Prefix: SYS  |  Recipient / Object Type: System Administrator for a specific application


Note: Alternatively, you can use the name of a specific business system as the prefix. For example: ACOS7: New user needs access.


Part 2: Identify the Event with a Code

Next, add a code that indicates what action triggered the message or where in the user lifecycle the event occurs.

Code: 1  |  Event / Lifecycle Stage: New account

Code: 2  |  Event / Lifecycle Stage: Restored account

Code: 3  |  Event / Lifecycle Stage: Modified account

Code: 4  |  Event / Lifecycle Stage: Account scheduled for deactivation

Code: 5  |  Event / Lifecycle Stage: Account has been deactivated

Code: 6  |  Event / Lifecycle Stage: Account temporarily deactivated (e.g., leave of absence)

Code: 7  |  Event / Lifecycle Stage: Access granted

Code: 8  |  Event / Lifecycle Stage: Access changed

Code: 9  |  Event / Lifecycle Stage: Access removed

Code: ERR  |  Event / Lifecycle Stage: Error situation that requires notification


Result: Simplified Searches and Clear Structure

Adopting this standard makes it easy to find specific message flows. For example, you can search for the prefix LED to instantly see all message flows intended for managers.

Below is an example of a filtered search result for "LED", demonstrating how the naming standard works in practice.

ID: 845  |  Name: LED 1 New employee email to manager  |  Subject: New employee [DisplayName] starts on [start]

ID: 1456  |  Name: LED 3 Employee changes position-email to manager  |  Subject: [DisplayName] has a new position

ID: 822  |  Name: LED 5 Employee is leaving-Email to manager  |  Subject: [DisplayName] is leaving on [APositionEndDate]

ID: 1442  |  Name: LED 5 Employee has left-Email to manager  |  Subject: The user accounts for [DisplayName] are now deactivated

ID: 1960  |  Name: LED 6 User account for employee on leave  |  Subject: The user account for [displayname] is now limited

ID: 851  |  Name: LED User back from leave - Manager  |  Subject: Restored user account for [displayname]