Creating lists of marketing objects

This example describes how to display a list of marketing object references.

Scenario

You have a project that has four subordinate marketing objects associated with it:

Two Brochures

One Mailer

One Resource bundle

After you create the project, you periodically check to see which participating marketing objects have already been created.

This example describes the steps necessary to create this scenario in IBM® Operações de Marketing.

Assumptions

The following items exist in Operações de Marketing:

A project template named Event planning

Marketing object templates for Brochures, Mailers, and Resource bundles.

Tasks

To implement this scenario, perform the following tasks.

1.	Using the Forms Editor, create a specification file to hold the following forms:

Create a form to hold a custom text attribute, Originating Project.

After you create a participating marketing object, you enter the value of the project code for the originating project in this field.

Create a custom tab, Participating Marketing Objects.

For the custom tab, you add a single object reference attribute to a form. To configure this attribute, you must first create a custom view.

"Creating the custom tab and attribute" describes the details for creating these forms.

2.	Create a custom view as described in "Creating the custom view".

3.	Load the forms into Operações de Marketing, and add the forms to the appropriate templates:

4.	Create the objects:

a project from the Event planning project template, EventStuff001.

a brochure, Brochure001, and set its originating project to the project code for EventStuff001.

a mailer, Mailer001, and set its originating project to the project code for EventStuff001.

When you open the Participating Marketing Objects tab for EventStuff001, you see the details for the associated marketing objects:

Creating the custom tab and attribute

We need a tab that can hold the list. We add this tab to a project template in Operações de Marketing. We also need to define the custom form to hold the project code. The custom view depends on both these forms using the same database table, so we create them both in this section.

1.	In the Forms Editor, create a specifications file to hold two forms, both using the same database table.

2.	Create the specifications database table as follows:

Field	Value
Table Name	dyn_mo_table
Display Name	dyn_mo_table
Key Column Name	po_id
Attribute Name	po_id

3.	Create the two forms:

Field	Form 1	Form 2
Internal Name	OriginatingProj	linkedMOs
Display Name	Originating Project	Associated MOs
Description	Will hold a single attribute that points to the originating project.	Form to display the linked Marketing Objects in a list.
Attribute Name Database Table	dyn_mo_table	dyn_mo_table

4.	For the list TVC component, specify the following:

Field	Value
Reference Database Table	proj_mos_by_proj_code
Reference Table Key Column	mo_id
Filter By Parent ID	checked
Parent ID Column Name	ProjID

5.	Create a TVC attribute of type Single List Object Reference. In the Object Reference Properties section, specify the following:

Field	Value
Object Reference Id Column	mo_id
Object Reference Type Column	comp_type_name

6.	Create a form attribute of type TVC Component and set the TVC Component to the TVC attribute set in step 3.

7.	Create a form attribute to hold the project code as a text attribute. For this attribute, specify the following:

Field	Value
Attribute type	Text - Single-Line
Internal Name	PID
Form	Originating Project
Display Name	Project Code
Database Column	PID

8.	Export the forms and save and close the specifications file.

9.	Run the SQL script to create the dyn_mo_table and its columns.

Creating the custom view

Typically, you need to create a custom view before you can add an object reference to a list view. In this example, we reference a marketing object on a project, where the marketing object contains a text field that holds a project code.

This example uses three tables to create the view: uap_projects, uap_mktgobject, and the custom table dyn_mo_table. The view is named proj_mos_by_proj_code.

Prerequisite custom table

Before creating the view, ensure that you have created the custom table, dyn_mo_table, and that it contains the following columns:

po_id: key column, specified in the DB Tables tab for the form

PID: text column created in the Forms Attribute tab to hold the project code as text.

Custom view details

The view contains the following columns:

proj_code and project_id from uap_projects

name, comp_type_name, and mktg_object_id from uap_mktgobject

The actual SQL code to create the view follows:

create view proj_mos_by_proj_code (
asscProj, MOName, ProjID, mo_id, comp_type_name) As
select PROJ.name as asscProj, MO.name as MOName,
PROJ.project_id as ProjID, MO.mktg_object_id as mo_id,
MO.comp_type_name as comp_type_name
from uap_projects PROJ, dyn_mo_table MOT, uap_mktgobject MO
where PROJ.proj_code = MOT.PID and MOT.po_id = MO.mktg_object_id

The following table shows the column names and some sample rows from this database view:

asscProj	MOName	ProjID	mo_id	comp_type_name
BRAIN-001	RB-005	101	147	creatives
BRAIN-001	RB-006	101	148	creatives
Event Horizon	CampaignMAIL01	149	145	creatives
Event Horizon	CampaignBRO01	149	142	creatives
Event Horizon	CampaignRB01	149	143	creatives
Event Horizon	CampaignRB02	149	144	creatives