SaaS unique naming conventions

The Service Provider needs to enforce unique naming conventions for their own operation and make sure that tenants also adhere to these unique naming conventions.

The WFO multi-tenant system shares many system and organizational settings between tenants. Some of these settings require unique naming across the system. Therefore, it is important that the Service Provider and all tenants in a WFO multi-tenant environment adhere to naming conventions. If a tenant tries to create a non-unique name or does not adhere to the naming convention, the system displays an error message.

SaaS naming convention for user names

When setting up user account access, use the email address of the employee as the user name so that the name is unique.

For example, dennis.parker@CompanyX.com

SaaS naming convention for customer Integration Server adapters

Each customer Integration Server adapter that is added to the SaaS environment must adhere to the following naming convention:

[Adapter Type]_[Customer Adapter Identifier]_[Tenant/Oracle Customer ID]

For example:

ASE_Nevada_123456

System entities that must have unique names

The following system entities must have unique names. It is recommended to append a prefix designating the tenant or group name to each name to ensure uniqueness across the system.

System entity	Entity
System-wide entities	Alert rules
	Attributes
	Data sources
	Employee Types
	User-Defined Fields (UDFs)
	Users’ login names
	Queue filters
Recording Interactions	Archive campaign schedules
	Archive campaigns
	Recording rules
Interactions	CCD
Speech Analytics	Speech instance names
	Speech transcription rules
Workforce Management (WFM)	Activities
	Activity Types
	Job Titles
	Skills
	Special Days
	Work queues
	Campaigns
Scorecards	Extensible Dimension Members
	Extensible Dimension Types
	Performance Management objectives
Coaching	Performance Management Coaching Session Types
	Topics
eLearning	Lessons
	Lesson blocks
Real-Time Analytics Framework	Recorder Analytics identification rules
	Recorder Analytics rules

Dashboard names across tenants and organizations

Dashboard names do not have to be unique among tenants. In other words, multiple tenants can use the same names for dashboards. Within each tenant organization, however, the dashboard names must be unique. The non-unique dashboard name rule exists on the tenant level only.

If there is only one organization that does not have any tenants associated with it (also known as tenant 0), that organization can also use the same dashboard names as other tenant organizations.

However, if there are multiple organizations at the level of tenant 0, each additional organization must have unique dashboard names. In other words, multiple tenant 0 organizations cannot have the same dashboard names.

Example: Multiple tenant 0 organizations cannot have the same dashboard names

• Org 1, associated with tenant 1, can have a dashboard called: DB1

• Org 2, associated with tenant 2, can have a dashboard called: DB1

• Org 3, associated with no tenant (tenant 0) can have a dashboard called: DB1

• Org 4, also associated with no tenant (tenant 0) cannot have a dashboard called: DB1. This is because Org 3, which is associated with tenant 0 as well, has already taken that dashboard name. Org 4 must have different dashboard names than Org 3.

  

Organization	Tenant	Dashboard Name
Org 1	Tenant 1	DB1
Org 2	Tenant 2	DB1
Org 3	Tenant 0 (no tenant)	DB1
Org 4	Tenant 0 (no tenant)	DB2