Adding the campaign element to the element palette in the Activity Builder

You must include the new campaign element in the element palette so that business users can drag the new element from the palette into the work area.

WebSphere Commerce ProfessionalWebSphere Commerce EnterpriseDialog activities are available only in the Professional and Enterprise editions of WebSphere Commerce.

Before you begin

Review the following topic to ensure that you understand how the element palette works:

Procedure

  1. Open WebSphere Commerce Developer and switch to the Enterprise Explorer view.
  2. Complete one of the following steps:
    • WebSphere Commerce Version 7.0.0.0Feature Pack 1In the Enterprise Explorer view, expand LOBTools > WebContent > WEB-INF > src > lzx > commerce > marketing > propertiesViews.
    • Introduced in Feature Pack 2In the Enterprise Explorer view, expand LOBTools > WebContent > config > commerce > marketing > propertiesViews.
  3. Open the properties view file for the version of the Activity Builder that contains the palette that you want to add the campaign element to.
    For example, if you are adding an action element to the palette for Dialog activities, then open the properties view for Dialog activities. To add the campaign element to the palette in more than one properties view, you must perform the remaining steps in this procedure in each applicable properties view.

    The properties view files are:

    OptionDescription
    WebSphere Commerce Version 7.0.0.0Feature Pack 1Properties view OpenLaszlo class files WebSphere Commerce Version 7.0.0.0Feature Pack 1
    WebActivityBuilder.lzx
    This properties view contains the palette for Web activities.
    WebActivityTemplateBuilder.lzx
    This properties view contains the palette for Web activity templates.
    DialogActivityBuilder.lzx
    This properties view contains the palette for Dialog activities.
    DialogActivityTemplateBuilder.lzx
    This properties view contains the palette for Dialog activity templates.
    Introduced in Feature Pack 2Properties view definition files Introduced in Feature Pack 2
    WebActivityBuilder.def
    This properties view contains the palette for Web activities.
    WebActivityTemplateBuilder.def
    This properties view contains the palette for Web activity templates.
    DialogActivityBuilder.def
    This properties view contains the palette for Dialog activities.
    DialogActivityTemplateBuilder.def
    This properties view contains the palette for Dialog activity templates.
  4. In the properties view file:
    OptionDescription
    WebSphere Commerce Version 7.0.0.0Feature Pack 1Locate the data set named palette WebSphere Commerce Version 7.0.0.0Feature Pack 1Here is an example of the data set for the Dialog activity palette:
    <dataset name="palette">
	<Group resourceBundle="mktMarketingResources" name="triggers">
		<Element objectType="wait"/>
		<Element objectType="registers"/>
		<Element objectType="purchases"/>
		<Element objectType="customerIsInSegment"/>
		<Element objectType="customerParticipatesInSocialCommerce"/>				
	</Group>
	<Group resourceBundle="mktMarketingResources" name="targets">
		<Element objectType="customerSegmentIdList"/>
		<Element objectType="shoppingCart"/>
		<Element objectType="purchaseHistory"/>
		<Element objectType="catalogBrowsingBehavior"/>
		<Element objectType="onlineBehavior"/>
		<Element objectType="socialCommerceParticipation"/>
		<Element objectType="time"/>
	</Group>
	<Group resourceBundle="mktMarketingResources" name="actions">
		<Element objectType="sendMessage"/>
		<Element objectType="issueCoupon"/>
		<Element objectType="addToRemoveFromCustomerSegment"/>
	</Group>
	<Group resourceBundle="mktMarketingResources" name="branching">
		<Element objectType="simpleBranch"/>
		<Element objectType="branch"/>
	</Group>
</dataset>
    Introduced in Feature Pack 2Locate the Xml element named palette Introduced in Feature Pack 2Here is an example of the Xml element for the Dialog activity palette:
    <Xml name="palette">
	<Group helpLink="concepts/csbtriggers.htm" helpText="help_palette_triggers" name="triggers" resourceBundle="mktMarketingResources">
		<Element objectType="wait"/>
		<Element objectType="registers"/>
		<Element objectType="purchases"/>
		<Element objectType="customerParticipatesInSocialCommerce"/>
		<Element objectType="customerAbandonsShoppingCart"/>
		<Element objectType="birthdayTrigger"/>
		<Element objectType="customerIsInSegment"/>		
		<Element objectType="eventAndParametersTrigger"/>
		<Element objectType="CustomerSearchesTrigger"/>					</Group>
	<Group helpLink="concepts/csbtargets.htm" helpText="help_palette_targets" name="targets" resourceBundle="mktMarketingResources">
		<Element objectType="customerSegmentIdList"/>
		<Element objectType="shoppingCart"/>
		<Element objectType="purchaseHistory"/>
		<Element objectType="catalogBrowsingBehavior"/>
		<Element objectType="onlineBehavior"/>
		<Element objectType="socialCommerceParticipation"/>
		<Element objectType="time"/>
	</Group>
	<Group helpLink="concepts/csbactions.htm" helpText="help_palette_actions" name="actions" resourceBundle="mktMarketingResources">
		<Element objectType="sendMessage"/>
		<Element objectType="issueCoupon"/>
		<Element objectType="addToRemoveFromCustomerSegment"/>
	</Group>
	<Group helpLink="concepts/csbbranchvsexp.htm" helpText="help_palette_branching" name="branching" resourceBundle="mktMarketingResources">
		<Element objectType="simpleBranch"/>
	</Group>
</Xml>
  5. Insert a new <Element/> tag as a child of the appropriate <Group/> tag.
    The new <Element/> tag must have an objectType value that matches the objectType value that is defined in the object definition for the campaign element. Elements are displayed in the palette in the order that they are listed in this file.
  6. Save and close the properties view file.