Reassign Services simplifies and automates the transfer of existing Subscriber services from a Source User to a Target User.

This utility is for example useful when an employee left the company and a new employee now starts the same role. Therefore, instead removing the old subscriber and configuring a new subscriber with the same settings and standards, the services and settings can be moved from the old subscriber to the new subscriber.

Custom settings can be applied to these services during the reassignment. A Reassign Services Profile setting is available to choose the configuration templates that will be used to update services during reassignment. These allow you to customize most settings on any of the above devices, including Line Alerting Name, Line Label, DisplayASCII values, and so on.

Example templates are provided that contain macro variables for fields that are likely to differ between subscribers. The field values then resolve with input from existing target user details. In this way the templates are not limited by for example a Site and Phone Model.

When reassigning services from existing source users to existing target users, the latter are moved to the same site as the source user, if these differ.

An option is also available to create a new target user as part of the Reassign Services process, instead of selecting an existing user without services. This user will be created at the same site as the source user.

Reassign User Services

The Reassign Services feature directs you to the Customer hierarchy (if you are not already there) because it supports target users that are on a different site as the source user.

Most of the services are updated to be associated to the target user and have settings updated according to the Configuration Templates (CFTs) in the reassign profiles.

The feature includes the optional ability to update shared line appearances of the source user's lines on other users' phones to reflect the destination user's details. For example:

In this case, when Bob's service is reassigned to a new user, Mary's Line 2 appearance will need to be updated to reflect the new user (e.g display name, label, etc.). This is supported for line appearances on Phones, Device Profiles, and Remote Destination Profiles. See the reassign services profiles section for more details on the controls.

Model Details: view/ReassignServicesVIEW

Field Name	Comment
Reassign Service Profile	This field will pre-populate with the first profile. You can select a different profile if required. If no profile option is available, then a reassign service profile needs to be added in the system.
Source User	Choose the subscriber to be reassigned. This provides a list of usernames of Subscribers in the system. It will list local or CUCM-LDAP Synced Subscribers only (not VOSS-LDAP Synced). Once a subscriber is selected, the Source User Services tab is updated to show services currently assigned and that will be reassigned to the target user. This is a good way to validate that all the services are shown or that there are not services that you do not want reassigned.
Source User Hierarchy	Once a subscriber is selected the Source User Hierarchy will be populated - this is a read-only informational field.
Add A New Target User	Select this option if you need to add a new local user to the system as the target user. Once selected, the form updates to reflect this choice.
Target User	To reassign to an existing user: select the username from the dropdown. This will show local or CUCM-LDAP synced users at the customer level or lower. Once a user is selected, the Target User Services tab is updated to reflect any services currently assigned to the user. If the user has any entries on this tab then the transaction will be blocked. So this provides an option to check before submitting. To create a new target user: enter the username for the new user to be created. The user will be added to the same hierarchy as the source user.
Target User Hierarchy	Shown only if add new target user is not selected - read-only informational field. Shows the hierarchy of the selected target user. Can be different to the source user and the feature will move the target user to the same hierarchy as the selected source user.
First Name	First Name of the Target user. Will be read only if the target user is a LDAP synced user.
Last Name	Last Name of the Target user. Will be read only if the target user is a LDAP synced user.
Email Address	Email Address of the Target user. Will be read only if the target user is a LDAP synced user.
Password	Visible if the target user is not a LDAP synced user. Enter the password for the target user.
Pin	Enter the PIN for the target user (used for device profile and voicemail).

An asterisk * in the title indicates the field is mandatory.
If a field has a default value, it is shown in the Description column.
If the field type is an array, the Field Name has a .[n] suffix, where n is the array index placeholder.
Object and array field names are listed to provide context. If a field belongs to an object or an array, the full field name is shown in dot separated notation.

Title		Description	Details
Current Hierarchy PKID		The Pkid of the hierarchy node from where the view is launched.	Field Name: currentHnPkid Type: String
Source User		Name of Source User with existing services.	Field Name: sourceUsername Type: String Choices: [" "]
Source User Hierarchy		The name of the hierarchy node where Source User resides and the Target User will be moved to.	Field Name: sourceUserHn Type: String
Source Hierarchy Pkid		The PKID of the hierarchy node where the Source User resides and the Target User will be moved to.	Field Name: sourceUserHnPkid Type: String
Source Site		The Site name where the Source User resides and the Target User will be moved to	Field Name: sourceUserSite Type: String
Add New Target User		Checkbox to allow adding of Target User.	Field Name: addTargetUser Type: Boolean
Target User		Name of Target User that will receive services.	Field Name: username Type: String
Target User Hierarchy		The name of the hierarchy node where Target User resides at submit time.	Field Name: targetUserHn Type: String
Target User Current Hierarchy Pkid		The PKID of the hierarchy node where Target User resides at submit time.	Field Name: targetUserHnPkid Type: String
Target User Current Site Name		The Site where Target User currently resides.	Field Name: targetUserSite Type: String
First Name		The First Name of the Target User used in naming macros.	Field Name: firstName Type: String
Last Name		The Last Name of the Target User used in naming macros.	Field Name: lastName Type: String
Email Address		The Email Address of the Target User to be created.	Field Name: email Type: String
Password		The Password of the Target User to be created.	Field Name: password Type: String Is Password: True
Pin		The Pin of the Target User to be created.	Field Name: pin Type: String Is Password: True
Reassign Services Profile		Choose a Reassign Services Profile to apply to this service change.	Field Name: reassignServicesProfile Type: String Target: data/ReassignServicesProfile Target attr: profileName Format: uri
Source User Services			Field Name: existingSource Type: Object
	Phones		Field Name: existingSource.phones Type: String
	Extension Mobility Profiles		Field Name: existingSource.ext_mobilities Type: String
	Voicemail Extension		Field Name: existingSource.voicemail Type: String
	Webex		Field Name: existingSource.webex Type: String
	Single Number Reach		Field Name: existingSource.snr Type: String
Target User Services			Field Name: existingTarget Type: Object
	Phones		Field Name: existingTarget.phones Type: String
	Extension Mobility Profiles		Field Name: existingTarget.ext_mobilities Type: String
	Voicemail Extension		Field Name: existingTarget.voicemail Type: String
	Webex		Field Name: existingTarget.webex Type: String
	Single Number Reach		Field Name: existingTarget.snr Type: String
LDAP User Status		The LDAP User Status of the Target User to be created.	Field Name: ldapUserStatus Type: Integer
LDAP Directory Name		The LDAP Directory Name of the Target User to be created.	Field Name: ldapDirectoryName Type: String

Model: view/ReassignServicesVIEW

Reassign User Services

Reassign User Services

Model Details: view/ReassignServicesVIEW