11.1 About Extended User Attributes Services

A typical Extended User Attributes service entry is similar to the following:

ADD_EXTENDED_USER_ATTRIBUTES
UserService 0 null null null !csUnableToAddExtendedAttr(dName)
3:checkSubAdmin:UserAdmin:0:null
3:loadUserAndCheckEditAllowedWithExtendedAttributes::4:null
3:setLocalValues:alwaysSave,1,doAdminFields,1:0:null
3:removeCachedUser::0:null
3:setConditionVars:IsModifyExisting,1,IsAddingAttributes,1:0:null
3:modifyExtendedUserAttributes:IuserExtendedAttribute:8:null
3:checkRefreshUsers::0:null

• The first line indicates the service name: ADD_EXTENDED_USER_ATTRIBUTES

• The second line lists the service's attributes:

  • Service class: UserService

  • Access level: 0

  • Template: null (none used)

  • Service type: null (not a subservice)

  • Subjects Notified: null

  • Error message: Unable to add new extended attributes for user

• The remainder of the entry lists the service's actions, each line designating one action:

  • action type: for example, 3, indicating a Java method.

  • action name: for example, modifyExtendedUserAttributes

  • action parameters: for example, IuserExtendedAttribute. If no parameters are specified, double-colons (::) are included.

  • action control mask: for example, 8, indicating the end of a database transation. The double-colon indicator (::) can also be included.

  • action error message: for example, null if no message is available.

Each element of the service's action is separated by a colon (:).

See "Customizing Services" for details about a service's attributes and actions.