Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
+1
person also asked this
people also asked this
Replies
12 replies
Subscribers
10 subscribers
Views
38828 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
What characters are valid in user profile first and last name?
Jason Ruvinsky
Certified Senior Developer
over 8 years ago
There is inconsistent handling of "valid" characters in a user profile first and last name, depending on where the fields are edited. Using the "Create User with i18n" plugin smart service allows a name to include characters, such as comma and period. (e.g. "King, Jr.") This appears in the user profile from the People tab on designer, afterwards. However, if you edit any field on the user profile in designer and click "Update", a validation error states "King, Jr. contains an invalid character."
Also, the "Update User Profile" smart service throws an error when used to edit this user, stating: "[First name may only contain letters, numbers, whitespace, and the _ or - special characters][Last name may only contain letters, numbers, whitespace, and the _ or - special characters]".
Is this list of valid characters accurate? If so, why is it that Appian doesn't actually have any is...
OriginalPostID-258520
Discussion posts and replies are publicly visible
0
Jason Ruvinsky
Certified Senior Developer
over 8 years ago
Noticed this in the 17.1 release notes: User's First and Last Names Can Now Contain Periods
This change applies to all means of user creation and editing, including the Add User Smart Service, the Update User Profile Smart Service, User Management in the Admin Console, and the People tab in the legacy /designer environment
Eduardo, looks like you'll need to update your plugin once more.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 8 years ago
The API I am using should be compatible with these changes. That is the advantage of not using my own validation but the one in the public API :)
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
<