Samples > Starter stores > Starter store enhancements > Social Commerce > WebSphere Commerce Dojo Enhancements API > User interface widgets
ibm.social.Profile
The Profile widget is used by shoppers to create an online community profile that contains their personal information. This information is displayed when the social networking content created by the shopper is displayed in the storefront.
Each online community profile varies depending on whether Pluck or Lotus Connections is used as the profile service provider. The individual profile fields included in the Profile widget are configured by the service provider implementation.
A default online community profile is created when:
- The shopper registered with the store before the Social Commerce Profile widget was integrated into the storefront.
- The shopper does not create an online community profile during registration with the store.
The session ID for the shopper is used to create the default online community profile and screen name. This default profile is used by the Blog, PhotoGallery, and Reviews widgets to create user-generated content.
Sample Output
Example
<div dojoType = "ibm.social.Profile" profileAction = "Create" submitElementId="WC_UserRegistrationAddForm_links_1" productionModeSubmit = "true" profileId = "User Logon Id" derivedFields = "profileWidgetEmail=derivedEmailField,profileWidgetDOB=yearDropDown:monthDropDown:dayDropDown" </div> <div dojoType = "ibm.social.Profile" profileAction = "Update" submitElementId="WC_UserRegistrationUpdateForm_links_1" productionModeSubmit = "true" profileId = "User Logon Id" derivedFields = "profileWidgetEmail=derivedEmailField,profileWidgetDOB=yearDropDown:monthDropDown:dayDropDown" </div> <div dojoType = "ibm.social.Profile" profileId = "User Logon Id" profileAction = "ProductionRegisterOrFetch"> </div>
Parameters
- dojoType
- (String) The Dojo widget type. Set to ibm.social.Profile.
- profileAction
- (String) The action to perform on the online community profile. For example, to create or update the profile. The supported modes are Create, Update, Fetch, and ProductionRegisterOrFetch.
- productionModeSubmit
- (String) Used only for the Create and Update modes. When set to true, this parameter hides the Submit button. Use this parameter during store page integration to provide a single Submit button that can be used for both the WebSphere Commerce profile fields and the Social Commerce profile fields.
- submitElementId
- (String) The ID of the default Submit button element within a store page. Use this ID to attach the Profile widget to the default Submit button in the store. This parameter is required when the productionModeSubmit parameter is set to true.
- derivedFields
- (String) Used to prevent the repetition of user input when redundant fields exist within the same store page. Use this parameter when multiple forms are integrated into the same store page and a specific field appears in more than one form. For example, when both the default registration form and the Social Commerce Profile widget form are integrated into the same Madisons store page and both forms use the Birthday field. This parameter dynamically generates a check box beside the node that is defined as the field that derives the value from the duplicate field. The HTML ID attribute from the duplicate field is required to map the value derived from the duplicate field. Shoppers can choose to either inherit the value from the duplicate field or enter a new value for the field. The following example shows the derivedFields parameter used when duplicate fields exist for E-mail address and Birthday:
derivedFields = "profileWidgetEmail=derivedEmailField,profileWidgetDOB=yearDropDown:monthDropDown:dayDropDown"Where:
- profileWidgetEmail
- The HTML ID attribute of the field that derives the value from derivedEmailField.
- profileWidgetDOB
- The HTML ID attribute of the field that derives the value from three HTML IDs (yearDropDown, monthDropDown, and dayDropDown) that are associated to create a single value. For example, three individual drop-down lists that represent the year, month, and day entries. Use semicolons to separate each HTML ID when this scenario occurs with only date type fields.
Related tasks
Related reference
My Account: Personal Information