Creating the properties view for the campaign element
If your new campaign element requires input from business users, declare the widgets to capture that input. By doing this, you create the user interface, called the properties view, for the new campaign element. In the Activity Builder, a campaign element's properties view displays below the work area when you click the campaign element.
Before you begin
About this task
Procedure
- Review the available widgets for Management Center properties views and plan the user interface for your campaign element.
- Open HCL Commerce Developer and switch to the Enterprise Explorer view.
- Create a directory to store your new properties view file.
Use a directory structure similar to the following example:
- LOBTools/WebContent/WEB-INF/src/xml/your_company_name/marketing/propertiesViews/activityBuilder
- Create the new properties view file. Name the file using this syntax: campaign_element_namePropertiesView.xml; for example, CustomLevelOfSupportPropertiesView.xml.
-
Define the new properties view as a flow element property.
For example:
<FlowElementProperties definitionName="extCustomLevelOfSupportProperties"> <PropertyGroup name="group" collapsable="false"> <PropertyCombobox promptText="Support level" propertyName="supportLevel"/> </PropertyGroup> </FlowElementProperties>
More complex properties views require multiple widgets. Another option is tabs. Consider using the properties view of an existing, similar campaign element as a starting point for your new campaign element. The existing properties view files are stored here:
LOBTools/WebContent/WEB-INF/src/xml/commerce/marketing/propertiesViews/activityBuilder
- Define the new properties view file wherever it is used.