More actions
User Functions
These functions are to be used to manipulate user’s properties. Thread’s user is distinguished from the resource project questionnaire’s user, for example, the thread’s user is the interviewer while the resource project questionnaire is the interviewee when using Cati.
Pages in category "User Functions"
The following 83 pages are in this category, out of 83 total.
G
- GetAddress
- GetCity
- GetCountry
- GetCulture
- GetCurrentUserEmail
- GetCurrentUserFirstName
- GetCurrentUserFullName
- GetCurrentUserId
- GetCurrentUserLastName
- GetCurrentUserMiddleName
- GetCurrentUserResourceId
- GetCurrentUserUniqueId
- GetEmail
- GetFirstName
- GetLanguage
- GetLastName
- GetMiddleName
- GetPassword
- GetPhoneNumber
- GetPoints
- GetRegion
- GetRoleIdByName
- GetSampleRuleId
- GetTimezone
- GetUserIdFromResourceId
- GetUsername
- GetUserRoleId
- GetZipcode
S
U
- User addUserHourlyCost
- User expirePoints
- User formatName
- User generateRandomNumericPassword
- User generateRandomPassword
- User getCallingLoggedInUser
- User getCommunicationHistory
- User getCurrentUser
- User getLoggedInUser
- User getPointsEarnedInPeriod
- User getPointsUsedInPeriod
- User getQasUser
- User getResourceIdFromUserId
- User getResourceIdFromUserIds
- User getRoleIdByName
- User getTransactionHistory
- User getUserByGuid
- User getUserByResourceId
- User getUserByUsername
- User getUserHourlyCosts
- User getUsersByEmail
- User getUsersByGroupResourceId
- User getUsersByResourceIds
- User insertPoints
- User isMemberOfSampleRule
- User isValidUsername
- User new
- User removeAllUserHourlyCosts
- User removeUserHourlyCost
- User save
- User updateUserHourlyCost
- User usernameExists
- User withdrawPoints
- UsernameExists