Free cookie consent management tool by TermsFeed

isusernametaken() Function

On This Page

Function

isusernametaken( username )

Verifies whether a user account with the specified username is already present.

See also: Create a New User, Add User Smart Service

Parameters

Keyword Type Description

username

Text

The username to check against the current list of active and deactivated users.

Returns

Boolean

Usage considerations

A false result indicates that the username is available to use when creating a new user, unless the username contains special characters that are not permitted.

For a list of usernames, returning false means that all of the usernames are available. If any of the usernames are taken, the result will be true.

Both active and deactivated user accounts are referenced.

The username parameter is case-sensitive, however you will not be able to create a username if case-insensitive matches exist.

isusernametaken() cannot be used to define a column of process report data or in a process event.

Using this function in a process model with autoscale enabled may result in degraded site or application performance. It should be used with caution and tested thoroughly before deploying it for real-world use. When the application is in production, use the Autoscaled Process Activity tab to monitor how the process performs at scale.

Examples

You can copy and paste these examples into the Expression Rule Designer to see how this works.

Given that you have users in your environment with the usernames john.doe and jane.doe:

1
isusernametaken("john.doe")

Returns true.

1
isusernametaken("John.Doe")

Returns false due to case sensitivity.

Feature compatibility

The table below lists this function's compatibility with various features in Appian.
Feature Compatibility Note
Portals Partially compatible

Can be used with Appian Portals if it is connected using an integration and web API.

Offline Interfaces Partially compatible

Can be used with offline interfaces if loaded at the top of the interface.

Sync-Time Custom Record Fields Incompatible
Real-Time Custom Record Fields Incompatible

Custom record fields that evaluate in real time must be configured using one or more Custom Field functions.

Process Reports Compatible
Process Events Compatible

Can be used to configure a process event node, such as a start event or timer event.

Process Autoscaling Partially compatible

Using this function in a process model with autoscale enabled may result in degraded site or application performance.

Event Consumer Filter Conditions Incompatible

Cannot be used in filter conditions.

Event Consumer Event Handlers Incompatible

Cannot be used in event handler expressions.

Feedback