Update a user
Changes the fields of a BPMS 3.x user of the tenant of the request that the body carries, with the rules of creating a user, as the 3.x user form does; an absent field is left as it is. Requires 6.2.2.2 (edit users). A body that changes nothing writes nothing. The roles, the password, and the status have their own operations.
bearerAuthorizationBearer <token>The token of a session that createSession opened
userId*integerId of the user
int64The fields to change
application/json- body
email?|Up to 255 characters; an empty one removes it unless bpms.access.users.email-required is on, which also makes it unique in the tenant
identification?|Up to 15 letters and digits; unique in the tenant
lastName?|Up to 255 characters
name?|Up to 255 characters
userName?|The name the user logs in with, up to 255 characters; unique in any case
The user as stored after the update
application/json- response
email?string|nullenabled?booleanFalse when the user is disabled; a stored NULL reads as false
id?integerint64identification?stringlastName?stringlocked?booleanTrue once the failed logins exceed the configured maximum
name?stringpasswordChangeRequired?booleanTrue when the user must change the password at the next login
userName?stringThe name the user logs in with
curl -X PATCH 'https://bpms.bpms.work/api/v1/access/users/0' \ -H 'Content-Type: application/json' \ -d '{}'{ "email": "string", "enabled": true, "id": 0, "identification": "string", "lastName": "string", "locked": true, "name": "string", "passwordChangeRequired": true, "userName": "string"}