EDIT_USER_PROFILE User Services Core Oracle Content Server

Core Oracle Content Server Services 4-143 ■ Access Number: These access numbers can be assigned to the user. – 1: Read only – 3: Read and write – 7: Read, write, delete – 15: Administrative permissions Example ■ IdcCommand command file format: IdcService=EDIT_USER dName=user20 dUserAuthType=Local ■ HDA format with optional parameters and attribute information: Properties LocalData IdcService=EDIT_USER dName=jsmith dFullName=Jennifer Smith dUserAuthType=Local dPassword=password dEmail=jsmithexample.com dUserType=MKT dUserLocale=English-US end ResultSet UserAttribInfo 2 dUserName AttributeInfo jsmith role,admin,15,role,contributor,15 end

4.14.15 EDIT_USER_PROFILE

Service that modifies the user profile for an existing user. and saves profile settings. This cannot be used to change a users security credentials. Access Level: Read, Global 17 Location: IdcHomeDirresourcescoretemplatesstd_services.htm ■ Any of the fields in the Users table except dName can be updated by this service. ■ You can use this service o edit personalization information that is not stored in the database. Some of a users information is stored in the database and some is stored in personalization data .hda files. ■ For information in the database, simply passing the corresponding field name and a value causes the field to be updated. ■ For personalization data, encoded topic strings must be used for example, topicString1=updateKeys:pne_portal:lm_Layout:Trays . ■ The Password value cannot be updated for proxied users. ■ The most likely reason this service would fail is if it cannot find the user dName in the system, or if the user name passed in dName does not match the current user. 4-144 Oracle Fusion Middleware Services Reference Guide for Oracle Universal Content Management Additional Required Service Parameters ■ dName: The user name. Optional Service Parameters ■ dFullName: The full name of the user. ■ dPassword: The password for the user. ■ dEmail: The email address of the user. ■ dUserLocale: The locale designation, such as English-US, English-UK, Deutsche, Français, or Español. ■ dUserType: The user type. ■ emailFormatList: Set to HTML for HTML-based emails or text for text-based email. ■ numTopics: The number of additional personalization topics in this request. ■ topicString1: An encoded string of a personalization topic to update. ■ numTopics: The total number of topic strings being passed. ■ Any field from the Users table except dName: dFullName, dEmail, dPasswordEncoding, dPassword, dUserType, dUserAuthType, dUserOrgPath, dUserSourceOrgPath, dUserSourceFlags, dUserArriveDate, dUserChangeDate, dUserLocale, dUserTimeZone. ■ topicString1 - topicStringN: Any number of strings encoded to define personalization topic edit operations. ■ RedirectUrl: Used to display another page. If omitted, the user is redirected to the Oracle Content Server home page. Optional parameters for Oracle Content Server version 7.0 and later: ■ Layout: The API to use for example, Top Menu or Trays. ■ Skin: The skin to use for example, Windows. ■ XuiSearchTemplate: The template to use for the users personalized Search Results page. Results ■ Result Sets: UserTopicEdits Returned only if personalization data was edited. Contains info about what topic edits were performed. Has the following fields: topicName, topicEditAction, topicKey, topicValue. Note that topicValue is an HDA-encoded string. ■ Local Data: – changedSubjects – dUser ■ Response Template: – REDIRECT_TEMPLATE redirect_template.htm – Default redirect service: GET_DOC_PAGE Page=HOME_PAGE Used By ■ Resource Includes: user_info_submit_form Core Oracle Content Server Services 4-145 Example ■ IdcCommand command file format: IdcService=EDIT_USER_PROFILE dName=sysadmin ■ HDA format with optional parameters: Properties LocalData IdcService=EDIT_USER_PROFILE dName=jsmith dFullName=Jennifer Smith dPassword=password dEmail=jsmithexample.com dUserType=MKT dUserLocale=English-US end

4.14.16 GET_ALIASES