user Data Type

Namespace
http://eurotech.com/edc/2.0
Schema
edc.xsd
Properties
name data type type namespace min/max occurs constraints description
id long element edc 1/1 required  
accountId long element edc 1/1 required  
username string element edc 0/1    
createdOn dateTime element edc 0/1    
createdBy long element edc 1/1 required  
modifiedOn dateTime element edc 0/1    
modifiedBy long element edc 1/1 required  
status userStatus element edc 0/1    
password string element edc 0/1    
displayName string element edc 0/1    
email string element edc 0/1    
phoneNumber string element edc 0/1    
loginOn dateTime element edc 0/1    
loginAttempts int element edc 1/1 required  
lockedOn dateTime element edc 0/1    
optlock int element edc 1/1 required The optlock field is used to detect that this entity has not been modified by someone else. When updating an entity, first do a find to get the latest version of the entity and note the value of the optlock. Then in the update operation, set the optlock value to match the value that you found. If someone else has updated the entity between your find and update operations, the update will fail and the db/server will return an error.

See this stackoverflow question for more information on optimistic locking.

loginAttemptsResetOn dateTime element edc 0/1    
unlockOn dateTime element edc 0/1    
trust_date dateTime element edc 0/1    

Example

<user xmlns="http://eurotech.com/edc/2.0">
  <id>...</id>
  <accountId>...</accountId>
  <username>...</username>
  <createdOn>...</createdOn>
  <createdBy>...</createdBy>
  <modifiedOn>...</modifiedOn>
  <modifiedBy>...</modifiedBy>
  <status>...</status>
  <password>...</password>
  <displayName>...</displayName>
  <email>...</email>
  <phoneNumber>...</phoneNumber>
  <loginOn>...</loginOn>
  <loginAttempts>...</loginAttempts>
  <lockedOn>...</lockedOn>
  <optlock>...</optlock>
  <loginAttemptsResetOn>...</loginAttemptsResetOn>
  <unlockOn>...</unlockOn>
  <trust_date>...</trust_date>
</user>