This action updates an existing user in the ExtraView database.
SYNTAX
http://www.myserver.com/evj/ExtraView/ev_api.action?
security_user_id=username
&password=password OR [&access_token=token-value]
&statevar=insert_user
&p_template_file=file.html
&company_name=user_company
&email=email_address
&security_user_id =userID
&last_name=user_last_name
[&first_name=user_first_name]
[&security_password=password]
[&job_title=user_job_title]
[&address_line1=user_address_line_1]
[&address_line2=user_address_line_2]
[&city=city]
[&state=state]
[&postal_code=postal_code]
[&country=country]
[&work_telephone=work_telephone]
[&home_telephone=home_telephone]
[&cell_phone=cell_phone]
[&address_line1=user_address_line_1]
[&fax=fax]
[&pager=pager]
NOTES
You must always provide the security_user_id and it must exist. All other parameters are optional, and if provided, the value of the parameter provided will be used to update the database.
If the ExtraView behavior setting named ENFORCE_DETAILED_USER_INFO has a value of YES, then the COMPANY_NAME, ADDRESS_LINE1, CITY, STATE, POSTAL_CODE and WORK_TELEPHONE can be updated, but if any of them do not exist, it must be provided.
You must have update permission to the security key named SE_SECURITY_USER before you can execute the command.
The optional access_token parameter allows you to use a valid OAuth2 token obtained with the get_token command. If you provide the access_token parameter, then the user_id and password parameters should not be provided. This prevents the password being sent in clear text over your network connection.