KB-1089 How to rename a user in Appian

Elly Meng — Fri, 23 Sep 2022 21:25:23 GMT

Current Revision posted to Appian Knowledge Base by Elly Meng on 9/23/2022 9:25:23 PM

Purpose

This article includes instructions on how to change/edit/alter a user's username in Appian. If the account was created with the wrong name, the suggested approach is to create a new one with the desired name and deactivate the other one. This is feasible for accounts which are not yet associated with processes. If it is not feasible to create a new user, follow the instructions below.

Instructions

20.1 and later

Beginning in Appian 20.1, there are three new methods to rename users directly from the product and without the need for an outage. All methods can be performed by a System Administrator.

From the user profile page (Admin Console and Appian Designer)
Through the Rename Users smart service (bulk rename enabled)
Through the a!renameUsers() expression function that calls the smart service (bulk rename enabled)

See the following documentation for more details:

19.4 and earlier (self-managed only)

Note the following:

You MUST shut down all application server instances before running the rename. Failure to do so may cause user synchronization issues that can significantly degrade the end user experience on the site.
Renaming users using this method is resource intensive, because it acts as a simple search and replace in every engine in Appian. These steps must be executed during off-hours.
You will also need to update the username in any other systems where it is saved, including business datasources.

Contact Appian Technical Support for the correct version of the script based on the version of Appian used. If any of the user(s) being renamed are referenced in Decision objects, notify Appian Technical Support.
Disable LDAP Synchronization. It is important this remains disabled during the process, otherwise it is possible that the user will get re-introduced with the old username.
Unzip the script under <APPIAN_HOME>/_admin/_scripts on the server running the engines.
Grant execute permissions on the file if using Linux. Otherwise just start a command line as the Administrator.
Navigate to <APPIAN_HOME>/_admin/_scripts.
Execute the following commands first to verify that the rename will execute successfully:
1. Linux: ./renameUsers.sh --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2" --validate.
2. Windows: renameUsers.bat --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2" --validate.
If there are any warnings, review your input parameters or contact Appian Support. If the script verifies that the new usernames are available and that all the old usernames exist, proceed with the following command:
1. Linux: ./renameUsers.sh --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2" &.
2. Windows: renameUsers.bat --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2".
Alternatively, if renaming a larger number of users, use the --usernamesFile option:
- Linux: ./renameUsers.sh --usernamesFile "/home/john.smith/names.csv" &.
- Windows: renameUsers.bat --usernamesFile "/home/john.smith/names.csv".
- The usernamesFile should be named like <filename>.csv and have each line formatted as follows: <oldUsername>,<newUsername>.
Once the script is finished, an output file will get generated: <APPIAN_HOME>\_admin\_scripts\renameUsers_sql_queries_MM_DD_YY_hhmmss.sql.
Copy the generated SQL statements, log into the database containing the Appian data source with a user that has SELECT and UPDATE privileges over the database, and execute them. This will update the username in the primary DB. If the user has never logged into the environment, there will be no username to update in the primary DB.
Check that the user has been renamed.
You can re-enable LDAP Synchronization once the username has been updated.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2022

Tags: rename users, how-to, users, product use cases, completed use cases

KB-1089 How to rename a user in Appian

Elly Meng — Fri, 23 Sep 2022 21:24:29 GMT

Revision 7 posted to Appian Knowledge Base by Elly Meng on 9/23/2022 9:24:29 PM

Purpose

Instructions

20.1 and later

Beginning in Appian 20.1, there are three new methods to rename users directly from the product and without the need for an outage. All methods can be performed by a System Administrator.

From the user profile page (Admin Console and Appian Designer)
Through the Rename Users smart service (bulk rename enabled)
Through the a!renameUsers() expression function that calls the smart service (bulk rename enabled)

See the following documentation for more details:

19.4 and earlier (Self-managed only)

Note the following:

You MUST shut down all application server instances before running the rename. Failure to do so may cause user synchronization issues that can significantly degrade the end user experience on the site.
Renaming users using this method is resource intensive, because it acts as a simple search and replace in every engine in Appian. These steps must be executed during off-hours.
You will also need to update the username in any other systems where it is saved, including business datasources.

Contact Appian Technical Support for the correct version of the script based on the version of Appian used. If any of the user(s) being renamed are referenced in Decision objects, notify Appian Technical Support.
Disable LDAP Synchronization. It is important this remains disabled during the process, otherwise it is possible that the user will get re-introduced with the old username.
Unzip the script under <APPIAN_HOME>/_admin/_scripts on the server running the engines.
Grant execute permissions on the file if using Linux. Otherwise just start a command line as the Administrator.
Navigate to <APPIAN_HOME>/_admin/_scripts.
Execute the following commands first to verify that the rename will execute successfully:
1. Linux: ./renameUsers.sh --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2" --validate.
2. Windows: renameUsers.bat --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2" --validate.
If there are any warnings, review your input parameters or contact Appian Support. If the script verifies that the new usernames are available and that all the old usernames exist, proceed with the following command:
1. Linux: ./renameUsers.sh --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2" &.
2. Windows: renameUsers.bat --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2".
Alternatively, if renaming a larger number of users, use the --usernamesFile option:
- Linux: ./renameUsers.sh --usernamesFile "/home/john.smith/names.csv" &.
- Windows: renameUsers.bat --usernamesFile "/home/john.smith/names.csv".
- The usernamesFile should be named like <filename>.csv and have each line formatted as follows: <oldUsername>,<newUsername>.
Once the script is finished, an output file will get generated: <APPIAN_HOME>\_admin\_scripts\renameUsers_sql_queries_MM_DD_YY_hhmmss.sql.
Copy the generated SQL statements, log into the database containing the Appian data source with a user that has SELECT and UPDATE privileges over the database, and execute them. This will update the username in the primary DB. If the user has never logged into the environment, there will be no username to update in the primary DB.
Check that the user has been renamed.
You can re-enable LDAP Synchronization once the username has been updated.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2022

Tags: rename users, how-to, users, product use cases, completed use cases

KB-1089 How to rename a user in Appian

Parmida Borhani — Mon, 30 Mar 2020 22:06:40 GMT

Revision 6 posted to Appian Knowledge Base by Parmida Borhani on 3/30/2020 10:06:40 PM

Purpose

Instructions

20.1 and later

Beginning in Appian 20.1, there are three new methods to rename users directly from the product and without the need for an outage. All methods can be performed by a System Administrator.

From the user profile page (Admin Console and Appian Designer)
Through the Rename Users smart service (bulk rename enabled)
Through the a!renameUsers() expression function that calls the smart service (bulk rename enabled)

See the following documentation for more details:

19.4 and earlier

Self-managed

Note the following:

You MUST shut down all application server instances before running the rename. Failure to do so may cause user synchronization issues that can significantly degrade the end user experience on the site.
Renaming users using this method is resource intensive, because it acts as a simple search and replace in every engine in Appian. These steps must be executed during off-hours.
You will also need to update the username in any other systems where it is saved, including business datasources.

Contact Appian Technical Support for the correct version of the script based on the version of Appian used. If any of the user(s) being renamed are referenced in Decision objects, notify Appian Technical Support.
Disable LDAP Synchronization. It is important this remains disabled during the process, otherwise it is possible that the user will get re-introduced with the old username.
Unzip the script under <APPIAN_HOME>/_admin/_scripts on the server running the engines.
Grant execute permissions on the file if using Linux. Otherwise just start a command line as the Administrator.
Navigate to <APPIAN_HOME>/_admin/_scripts.
Execute the following commands first to verify that the rename will execute successfully:
1. Linux: ./renameUsers.sh --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2" --validate.
2. Windows: renameUsers.bat --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2" --validate.
If there are any warnings, review your input parameters or contact Appian Support. If the script verifies that the new usernames are available and that all the old usernames exist, proceed with the following command:
1. Linux: ./renameUsers.sh --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2" &.
2. Windows: renameUsers.bat --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2".
Alternatively, if renaming a larger number of users, use the --usernamesFile option:
- Linux: ./renameUsers.sh --usernamesFile "/home/john.smith/names.csv" &.
- Windows: renameUsers.bat --usernamesFile "/home/john.smith/names.csv".
- The usernamesFile should be named like <filename>.csv and have each line formatted as follows: <oldUsername>,<newUsername>.
Once the script is finished, an output file will get generated: <APPIAN_HOME>\_admin\_scripts\renameUsers_sql_queries_MM_DD_YY_hhmmss.sql.
Copy the generated SQL statements, log into the database containing the Appian data source with a user that has SELECT and UPDATE privileges over the database, and execute them. This will update the username in the primary DB. If the user has never logged into the environment, there will be no username to update in the primary DB.
Check that the user has been renamed.
You can re-enable LDAP Synchronization once the username has been updated.

Cloud

Create a support case with Appian Technical Support and provide the following information:

A time frame during off-hours to perform the user rename. A minimum of 2 hours is needed for user renames. During this time, the site will be inaccessible as the application server(s) will be shutdown.
- Note: Depending on the size of the engines, Appian Technical Support may determine a longer time frame is needed. This will be determined and coordinated through the support case if necessary.
A csv file of usernames to be renamed in the format below. Each <old_username>,<new_username> pair should be on it's own line. Appian Technical Support requires usernames to be provided in this format for user renames:
```
<old_username_1>,<new_username_1> <old_username_2>,<new_username_2>
```

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2020

Tags: rename users, how-to, users, product use cases, completed use cases

KB-2099 How to rename a user in Appian

Rebecca Jonas — Mon, 30 Mar 2020 20:07:11 GMT

Revision 5 posted to Appian Knowledge Base by Rebecca Jonas on 3/30/2020 8:07:11 PM

Purpose

Instructions

20.1 and later

Beginning in Appian 20.1, there are three new methods to rename users directly from the product and without the need for an outage. All methods can be performed by a System Administrator.

From the user profile page (Admin Console and Appian Designer)
Through the Rename Users smart service (bulk rename enabled)
Through the a!renameUsers() expression function that calls the smart service (bulk rename enabled)

See the following documentation for more details:

19.4 and earlier

On-Premise

Note the following:

You MUST shut down all application server instances before running the rename. Failure to do so may cause user synchronization issues that can significantly degrade the end user experience on the site.
Renaming users using this method is resource intensive, because it acts as a simple search and replace in every engine in Appian. These steps must be executed during off-hours.
You will also need to update the username in any other systems where it is saved, including business datasources.

Contact Appian Technical Support for the correct version of the script based on the version of Appian used. If any of the user(s) being renamed are referenced in Decision objects, notify Appian Technical Support.
Disable LDAP Synchronization. It is important this remains disabled during the process, otherwise it is possible that the user will get re-introduced with the old username.
Unzip the script under <APPIAN_HOME>/_admin/_scripts on the server running the engines.
Grant execute permissions on the file if using Linux. Otherwise just start a command line as the Administrator.
Navigate to <APPIAN_HOME>/_admin/_scripts.
Execute the following commands first to verify that the rename will execute successfully:
1. Linux: ./renameUsers.sh --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2" --validate.
2. Windows: renameUsers.bat --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2" --validate.
If there are any warnings, review your input parameters or contact Appian Support. If the script verifies that the new usernames are available and that all the old usernames exist, proceed with the following command:
1. Linux: ./renameUsers.sh --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2" &.
2. Windows: renameUsers.bat --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2".
Alternatively, if renaming a larger number of users, use the --usernamesFile option:
- Linux: ./renameUsers.sh --usernamesFile "/home/john.smith/names.csv" &.
- Windows: renameUsers.bat --usernamesFile "/home/john.smith/names.csv".
- The usernamesFile should be named like <filename>.csv and have each line formatted as follows: <oldUsername>,<newUsername>.
Once the script is finished, an output file will get generated: <APPIAN_HOME>\_admin\_scripts\renameUsers_sql_queries_MM_DD_YY_hhmmss.sql.
Copy the generated SQL statements, log into the database containing the Appian data source with a user that has SELECT and UPDATE privileges over the database, and execute them. This will update the username in the primary DB. If the user has never logged into the environment, there will be no username to update in the primary DB.
Check that the user has been renamed.
You can re-enable LDAP Synchronization once the username has been updated.

Cloud

Create a support case with Appian Technical Support and provide the following information:

A time frame during off-hours to perform the user rename. A minimum of 2 hours is needed for user renames. During this time, the site will be inaccessible as the application server(s) will be shutdown.
- Note: Depending on the size of the engines, Appian Technical Support may determine a longer time frame is needed. This will be determined and coordinated through the support case if necessary.
A csv file of usernames to be renamed in the format below. Each <old_username>,<new_username> pair should be on it's own line. Appian Technical Support requires usernames to be provided in this format for user renames:
```
<old_username_1>,<new_username_1>
<old_username_2>,<new_username_2>
```

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2020

Tags: rename users, how-to, users, product use cases, completed use cases

DRAFT SP-3880 How to rename a user in Appian

Parmida Borhani — Mon, 30 Mar 2020 00:35:57 GMT

Revision 4 posted to Appian Knowledge Base by Parmida Borhani on 3/30/2020 12:35:57 AM

Purpose

Instructions

20.1 and later

Beginning in Appian 20.1, there are three new methods to rename users directly from the product and without the need for an outage. All methods can be performed by a System Administrator.

From the user profile page (Admin Console and Appian Designer)
Through a new Rename Users smart service (bulk rename enabled)
Through a new a!renameUsers() expression function that calls the smart service (bulk rename enabled)

See the following documentation for more details:

19.4 and earlier

On-Premise

Note the following:

You MUST shut down all application server instances before running the rename. Failure to do so may cause user synchronization issues that can significantly degrade the end user experience on the site.
Renaming users using this method is resource intensive, because it acts as a simple search and replace in every engine in Appian. These steps must be executed during off-hours.
You will also need to update the username in any other systems where it is saved, including business datasources.

Contact Appian Technical Support for the correct version of the script based on the version of Appian used. If any of the user(s) being renamed are referenced in Decision objects, notify Appian Technical Support.
Disable LDAP Synchronization. It is important this remains disabled during the process, otherwise it is possible that the user will get re-introduced with the old username.
Unzip the script under <APPIAN_HOME>/_admin/_scripts on the server running the engines.
Grant execute permissions on the file if using Linux. Otherwise just start a command line as the Administrator.
Navigate to <APPIAN_HOME>/_admin/_scripts.
Execute the following commands first to verify that the rename will execute successfully:
1. Linux: ./renameUsers.sh --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2" --validate.
2. Windows: renameUsers.bat --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2" --validate.
If there are any warnings, review your input parameters or contact Appian Support. If the script verifies that the new usernames are available and that all the old usernames exist, proceed with the following command:
1. Linux: ./renameUsers.sh --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2" &.
2. Windows: renameUsers.bat --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2".
Alternatively, if renaming a larger number of users, use the --usernamesFile option:
- Linux: ./renameUsers.sh --usernamesFile "/home/john.smith/names.csv" &.
- Windows: renameUsers.bat --usernamesFile "/home/john.smith/names.csv".
- The usernamesFile should be named like <filename>.csv and have each line formatted as follows: <oldUsername>,<newUsername>.
Once the script is finished, an output file will get generated: <APPIAN_HOME>\_admin\_scripts\renameUsers_sql_queries_MM_DD_YY_hhmmss.sql.
Copy the generated SQL statements, log into the database containing the Appian data source with a user that has SELECT and UPDATE privileges over the database, and execute them. This will update the username in the primary DB. If the user has never logged into the environment, there will be no username to update in the primary DB.
Check that the user has been renamed.
You can re-enable LDAP Synchronization once the username has been updated.

Cloud

Create a support case with Appian Technical Support and provide the following information:

A time frame during off-hours to perform the user rename. A minimum of 2 hours is needed for user renames. During this time, the site will be inaccessible as the application server(s) will be shutdown.
- Note: Depending on the size of the engines, Appian Technical Support may determine a longer time frame is needed. This will be determined and coordinated through the support case if necessary.
A csv file of usernames to be renamed in the format below. Each <old_username>,<new_username> pair should be on it's own line. Appian Technical Support requires usernames to be provided in this format for user renames:
```
<old_username_1>,<new_username_1>
<old_username_2>,<new_username_2>
```

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2020

Tags: rename users, how-to, users, product use cases, completed use cases

DRAFT SP-3880 How to rename a user in Appian

Parmida Borhani — Mon, 30 Mar 2020 00:32:20 GMT

Revision 3 posted to Appian Knowledge Base by Parmida Borhani on 3/30/2020 12:32:20 AM

Purpose

Instructions

20.1 and later

Beginning in Appian 20.1, there will be three new methods to rename users directly from the product and without the need for an outage. All methods can be performed by a System Administrator.

From the user profile page (Admin Console and Appian Designer)
Through a new Rename Users smart service (bulk rename enabled)
Through a new a!renameUsers() expression function that calls the smart service (bulk rename enabled)

See the following documentation for more details:

19.4 and earlier

On-Premise

Note the following:

You MUST shut down all application server instances before running the rename. Failure to do so may cause user synchronization issues that can significantly degrade the end user experience on the site.
Renaming users using this method is resource intensive, because it acts as a simple search and replace in every engine in Appian. These steps must be executed during off-hours.
You will also need to update the username in any other systems where it is saved, including business datasources.

Contact Appian Technical Support for the correct version of the script based on the version of Appian used. If any of the user(s) being renamed are referenced in Decision objects, notify Appian Technical Support.
Disable LDAP Synchronization. It is important this remains disabled during the process, otherwise it is possible that the user will get re-introduced with the old username.
Unzip the script under <APPIAN_HOME>/_admin/_scripts on the server running the engines.
Grant execute permissions on the file if using Linux. Otherwise just start a command line as the Administrator.
Navigate to <APPIAN_HOME>/_admin/_scripts.
Execute the following commands first to verify that the rename will execute successfully:
1. Linux: ./renameUsers.sh --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2" --validate.
2. Windows: renameUsers.bat --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2" --validate.
If there are any warnings, review your input parameters or contact Appian Support. If the script verifies that the new usernames are available and that all the old usernames exist, proceed with the following command:
1. Linux: ./renameUsers.sh --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2" &.
2. Windows: renameUsers.bat --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2".
Alternatively, if renaming a larger number of users, use the --usernamesFile option:
- Linux: ./renameUsers.sh --usernamesFile "/home/john.smith/names.csv" &.
- Windows: renameUsers.bat --usernamesFile "/home/john.smith/names.csv".
- The usernamesFile should be named like <filename>.csv and have each line formatted as follows: <oldUsername>,<newUsername>.
Once the script is finished, an output file will get generated: <APPIAN_HOME>\_admin\_scripts\renameUsers_sql_queries_MM_DD_YY_hhmmss.sql.
Copy the generated SQL statements, log into the database containing the Appian data source with a user that has SELECT and UPDATE privileges over the database, and execute them. This will update the username in the primary DB. If the user has never logged into the environment, there will be no username to update in the primary DB.
Check that the user has been renamed.
You can re-enable LDAP Synchronization once the username has been updated.

Cloud

Create a support case with Appian Technical Support and provide the following information:

A time frame during off-hours to perform the user rename. A minimum of 2 hours is needed for user renames. During this time, the site will be inaccessible as the application server(s) will be shutdown.
- Note: Depending on the size of the engines, Appian Technical Support may determine a longer time frame is needed. This will be determined and coordinated through the support case if necessary.
A csv file of usernames to be renamed in the format below. Each <old_username>,<new_username> pair should be on it's own line. Appian Technical Support requires usernames to be provided in this format for user renames:
```
<old_username_1>,<new_username_1>
<old_username_2>,<new_username_2>
```

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2020

Tags: rename users, how-to, users, product use cases, completed use cases

DRAFT SP-3880 How to rename a user in Appian

Parmida Borhani — Fri, 27 Mar 2020 05:09:44 GMT

Revision 2 posted to Appian Knowledge Base by Parmida Borhani on 3/27/2020 5:09:44 AM

Purpose

Instructions

20.1 and later

Beginning in Appian 20.1, users can be renamed directly from the product and without the need for an outage. Please see the documentation for more details.

19.4 and earlier

On-Premise

Note the following:

You MUST shut down all application server instances before running the rename. Failure to do so may cause user synchronization issues that can significantly degrade the end user experience on the site.
Renaming users using this method is resource intensive, because it acts as a simple search and replace in every engine in Appian. These steps must be executed during off-hours.
You will also need to update the username in any other systems where it is saved, including business datasources.

Contact Appian Technical Support for the correct version of the script based on the version of Appian used. If any of the user(s) being renamed are referenced in Decision objects, notify Appian Technical Support.
Disable LDAP Synchronization. It is important this remains disabled during the process, otherwise it is possible that the user will get re-introduced with the old username.
Unzip the script under <APPIAN_HOME>/_admin/_scripts on the server running the engines.
Grant execute permissions on the file if using Linux. Otherwise just start a command line as the Administrator.
Navigate to <APPIAN_HOME>/_admin/_scripts.
Execute the following commands first to verify that the rename will execute successfully:
1. Linux: ./renameUsers.sh --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2" --validate.
2. Windows: renameUsers.bat --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2" --validate.
If there are any warnings, review your input parameters or contact Appian Support. If the script verifies that the new usernames are available and that all the old usernames exist, proceed with the following command:
1. Linux: ./renameUsers.sh --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2" &.
2. Windows: renameUsers.bat --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2".
Alternatively, if renaming a larger number of users, use the --usernamesFile option:
- Linux: ./renameUsers.sh --usernamesFile "/home/john.smith/names.csv" &.
- Windows: renameUsers.bat --usernamesFile "/home/john.smith/names.csv".
- The usernamesFile should be named like <filename>.csv and have each line formatted as follows: <oldUsername>,<newUsername>.
Once the script is finished, an output file will get generated: <APPIAN_HOME>\_admin\_scripts\renameUsers_sql_queries_MM_DD_YY_hhmmss.sql.
Copy the generated SQL statements, log into the database containing the Appian data source with a user that has SELECT and UPDATE privileges over the database, and execute them. This will update the username in the primary DB. If the user has never logged into the environment, there will be no username to update in the primary DB.
Check that the user has been renamed.
You can re-enable LDAP Synchronization once the username has been updated.

Cloud

Create a support case with Appian Technical Support and provide the following information:

A time frame during off-hours to perform the user rename. A minimum of 2 hours is needed for user renames. During this time, the site will be inaccessible as the application server(s) will be shutdown.
- Note: Depending on the size of the engines, Appian Technical Support may determine a longer time frame is needed. This will be determined and coordinated through the support case if necessary.
A csv file of usernames to be renamed in the format below. Each <old_username>,<new_username> pair should be on it's own line. Appian Technical Support requires usernames to be provided in this format for user renames:
```
<old_username_1>,<new_username_1>
<old_username_2>,<new_username_2>
```

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2020

Tags: rename users, how-to, users, product use cases, completed use cases

DRAFT SP-3880 How to rename a user in Appian

Parmida Borhani — Fri, 27 Mar 2020 05:04:37 GMT

Revision 1 posted to Appian Knowledge Base by Parmida Borhani on 3/27/2020 5:04:37 AM

Purpose

Instructions

20.1 and later

Beginning in Appian 20.1, users can be renamed directly from the product and without the need for an outage. Please see the documentation for more details.

19.4 and earlier

On-Premise

Note the following:

You MUST shut down all application server instances before running the rename. Failure to do so may cause user synchronization issues that can significantly degrade the end user experience on the site.
Renaming users using this method is resource intensive, because it acts as a simple search and replace in every engine in Appian. These steps must be executed during off-hours.
You will also need to update the username in any other systems where it is saved, including business datasources.

Contact Appian Technical Support for the correct version of the script based on the version of Appian used. If any of the user(s) being renamed are referenced in Decision objects, notify Appian Technical Support.
Disable LDAP Synchronization. It is important this remains disabled during the process, otherwise it is possible that the user will get re-introduced with the old username.
Unzip the script under <APPIAN_HOME>/_admin/_scripts on the server running the engines.
Grant execute permissions on the file if using Linux. Otherwise just start a command line as the Administrator.
Navigate to <APPIAN_HOME>/_admin/_scripts.
Execute the following commands first to verify that the rename will execute successfully:
1. Linux: ./renameUsers.sh --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2" --validate.
2. Windows: renameUsers.bat --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2" --validate.
If there are any warnings, review your input parameters or contact Appian Support. If the script verifies that the new usernames are available and that all the old usernames exist, proceed with the following command:
1. Linux: ./renameUsers.sh --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2" &.
2. Windows: renameUsers.bat --oldUsernames "oldUsername1;oldUsername2" --newUsernames "newUsername1;newUsername2".
Alternatively, if renaming a larger number of users, use the --usernamesFile option:
- Linux: ./renameUsers.sh --usernamesFile "/home/john.smith/names.csv" &.
- Windows: renameUsers.bat --usernamesFile "/home/john.smith/names.csv".
- The usernamesFile should be named like <filename>.csv and have each line formatted as follows: <oldUsername>,<newUsername>.
Once the script is finished, an output file will get generated: <APPIAN_HOME>\_admin\_scripts\renameUsers_sql_queries_MM_DD_YY_hhmmss.sql.
Copy the generated SQL statements, log into the database containing the Appian data source with a user that has SELECT and UPDATE privileges over the database, and execute them. This will update the username in the primary DB. If the user has never logged into the environment, there will be no username to update in the primary DB.
Check that the user has been renamed.
You can re-enable LDAP Synchronization once the username has been updated.

Cloud

Create a support case with Appian Technical Support and provide the following information:

A time frame during off-hours to perform the user rename. A minimum of 2 hours is needed for user renames. During this time, the site will be inaccessible as the application server(s) will be shutdown.
- Note: Depending on the size of the engines, Appian Technical Support may determine a longer time frame is needed. This will be determined and coordinated through the support case if necessary.
A csv file of usernames to be renamed in the format below. Each <old_username>,<new_username> pair should be on it's own line. Appian Technical Support requires usernames to be provided in this format for user renames:
```
<old_username_1>,<new_username_1>
<old_username_2>,<new_username_2>
```

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2020

Tags: rename users, how-to, users, product use cases, completed use cases