|
|
|
|
Creating users
To create new users:
- Use the PutProvisioningData operation.
To create new users and return an identifier set for each user:
- Use the PutProvisioningDataAndGetIdentifierSets operation.
Note: Use PutProvisioningDataAndGetIdentiferSets if the returned identifier sets are used within the client. The operation is significantly slower than PutProvisioningData.
Usage—for both operations:
- Specify one or more MedML <USER> elements for non-existent users.
- If the USERNAME you specify does not already exist, the user is automatically created.
- If you specify a USERNAME that already exists, the existing user is updated with the values you specify for the other fields.
- USERNAME values are case-sensitive.
- If you use PutProvisioningData to create a new user, set the user password, and activate the user in different command strings in the same call, the method runs successfully (the user is created, the password is set, and the user is active).
However, if you use the study with CIS or the ODM Export interface, when InForm Adapter attempts to process the transaction, it fails and generates the error "Failed to download InForm Transaction from trial 'trialxyz'". The InForm Server Adapter cannot continue to process any remaining transactions.
If you plan to use CIS or the ODM Export interface with the study, use either of the following workarounds when you use the PutProvisioningData method:
- Use separate calls to PutProvisioningData to create a user, set the user password, and activate the user.
- To use a single call to PutProvisioningData, create the user, set the password, and activate the user in the same command string within the call.
- Always set the UPDATE=TRUE flag when creating a new user.
Users and Rights groups
- New users that you add with the User Management Interface must have an associated rights group to use the InForm application. For more information, see Creating a rights group.
Values: USER element—Create user
Field
Required?
Comments
USERNAME
Yes
USERTYPE
Yes
The Support User type is reserved only for Oracle Support personnel.
FIRSTNAME
No
LASTNAME
No
DISPLAYNAME
No
DESCRIPTION
No
TITLE
No
ADDRESS
No
ADDRESS2
No
CITY
No
STATE
No
STATE and PROVINCE are mutually exclusive.
PROVINCE
No
STATE and PROVINCE are mutually exclusive.
ZIPCODE
No
ZIPCODE and POSTCODE are mutually exclusive.
POSTCODE
No
ZIPCODE and POSTCODE are mutually exclusive.
COUNTRY
No
PHONE
No
ALTPHONE
No
FAX
No
EMAIL
No
BEEPER
No
HOMESCREENURL
No
ACTIVESTATE
No
Active/Inactive, defaults to Inactive.
DELETESTATE
No
Terminated/Reinstate.
PASSWORD
No
USERMUSTRESETPASSWORD
No
USERDATEFORMAT
No
PRODUCTLOCALE
Yes
Required when creating new USER elements.
Values: ja-JP or en-US.
STUDYLOCALE
Yes
Required when creating new USER elements.
Value must be a study locale that is defined in some study version in the trial.
