ATG Personalization Programming Guide

Personalization Module Scenario Tables

The Personalization module uses the following tables to store user-related information about scenarios. The tables shown here, with the prefix dps, apply to external users. A parallel set of tables exists with the prefix dpi (for example, dpi_user_scenario) for internal users.

dps_scenario_value

This table contains a map of values that can be used in scenarios to persist scenario-related per-user information. For example, one segment in a scenario may store a value under a key in this map, and another segment (or scenario) may look up or change that value. These values are similar to scenario variables but are persisted across scenario segments. Both the keys and the values in this map are Strings.

Column

Data Type

Constraint

id

VARCHAR(40)

NOT NULL

(primary key)

The unique identifier associated with the user.

tag

VARCHAR(42)

NOT NULL

(primary key)

The key for a value in the scenario map.

scenario_value

VARCHAR(100)

NULL

The value for this key.

dps_user_scenario

This table associates a user with individual scenario instances.

Column

Data Type

Constraint

id

VARCHAR(40)

NOT NULL

The unique identifier associated with the user. References dps_user(id).

ind_scenario_id

VARCHAR(25)

NOT NULL

(primary key)

The ID associated with the scenario instance. References dss_ind_scenario(id).

dps_user_slot

This table stores information that associates a persistent slot with a user in the profile repository. (Specifically, the data corresponds to the value of the slotInstances property in the user profile.)

Column

Data Type

Constraint

id

VARCHAR(40)

NOT NULL

(primary key)

The unique identifier associated with the user. References dps_user(id).