Develop > Presentation layer > Customize marketing > Marketing customization: Management Center > Customizing triggers, targets, and actions
Add a new trigger, target or action
Add a new campaign element to the Activity Builder if the default campaign elements do not meet the business needs. You can then use the new campaign element in marketing activities.
- Create the campaign element template definition
By creating the campaign element template definition, you define the blueprint for the campaign element. When you have defined the XML you require, add the template definition to the DMELETEMPLATE table as a new entry.
- Register controller command names to match in a behavior rule
If you are creating a new trigger, target, or action that specifies a controller command in its behavior rule, register the controller command in a custom version of the marketing component configuration file (wc-admin-component.xml). When you register the controller command, also specify the Web application paths to exclude when the controller command is run from that Web application. This ensures that the behavior rule will match only for applicable Web applications that use the controller commands.
- Create the campaign element task command
Create a new task command interface and its associated implementation class for the new campaign element. The task command performs the work for the campaign element, and it can also validate parameters if required.
- Inform the marketing services of an external event for a trigger or target
If the custom trigger or target must detect an event that occurs on system that is external to WebSphere Commerce, then inform the marketing services of that event.To do so, call the Process MarketingTrigger service using a URL or using Java code. If the trigger or target detects a WebSphere Commerce event (or no event), you do not need to do this task.
- Define icons to represent the campaign element
You can create and load three versions of a custom icon to represent the new campaign element in the Management Center user interface. These images help business users identify the element when creating activities in the Activity Builder.
- Create the object definition for the campaign element
Create a new OpenLaszlo object definition for the new campaign element to collect input from the Management Center user interface. When business users fill in data about the new campaign element in a marketing activity, the object definition persists the data in two tables: DMELEMENT and DMELEMENTNVP.
- Create the properties view for the campaign element
If the 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.
- Create the summary for the campaign element
To display summary text below the campaign element in the Activity Builder work area, create a new extension class for this summary. In the Activity Builder, business users can read the summary text to quickly understand how an element is being used in a Web or Dialog activity.
- Add 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.
- Create and registering a serialization JSP file for the campaign element
Create and register a serialization JSP file to take the authoring elements from the DMELEMENT and DMELEMENTNVP tables for the new campaign element and display them in the Management Center user interface. Business users can then set the properties for the campaign element in marketing activities.
Related concepts
Marketing activity data storage and process flow
Campaign element template definitions
Campaign element task commands
Related reference
List of shipped campaign element templates and task commands