dss_coll_trans
This table contains information about pending collective scenario transitions. A collective transition is a transition that a collective scenario instance takes from one state in a scenario state machine to another. When the Scenarios module cannot complete such a transition in a single transaction (for example, when the transition initiates an e-mail campaign to a large number of users), it stores the pending transition in the database and completes it over multiple transactions.
Column | Data Type | Constraint |
|---|---|---|
| VARCHAR(25) | NOT NULL |
(Primary key) | The ID associated with the pending collective transition. | |
| WVARCHAR(255) | NULL |
The name of the scenario. | ||
| NUMERIC(19) | NULL |
The last time this scenario was modified. | ||
| VARCHAR(40) | NULL |
The ID of the server handling the transition. The value is a combination of a server name and | ||
| LONG VARBINARY | NULL |
The serialized JMS message bean that caused this scenario transition to occur. | ||
| VARCHAR(255) | NULL |
The type of the JMS event that caused this scenario transition to occur. | ||
| WVARCHAR(255) | NULL |
The name of the scenario segment. | ||
| VARCHAR(16) | NULL |
The state in the scenario state machine of the collective scenario instance at the start of the transition. | ||
| VARCHAR(25) | NULL |
The unique identifier for the collective scenario instance that is taking the transition. References | ||
| INT | NOT NULL |
Indicates where the transition is currently. The value can be actions1 (1), actions2 (2), nextState1 (3), or nextState2 (4). This value changes over multiple transactions as transition actions execute and move to the next scenario state. | ||
| INT | NULL |
For a given transition step, indicates where the transition is currently. For example, as multiple transition actions are executed, this value changes to indicate the index of the current action. | ||
| VARCHAR(25) | NULL |
The repository ID last used in a repository query. When a transition action is executed, for example, it is executed on a batch of individual scenario instances at a time. This value is used to keep track of the location in the process of cycling through the scenario instances. | ||
dss_ind_trans
This table contains information about pending individual scenario transitions. An individual transition is a transition taken from one scenario state machine state to another, by all the individual scenario instances in the originating state. The Scenarios module cannot typically complete such a transition in a single transaction because of the potentially large number of scenario instances involved, so it stores the pending transition in the database and completes it over multiple transactions.
Column | Data Type | Constraint |
|---|---|---|
| VARCHAR(25) | NOT NULL |
(primary key) | The ID associated with the pending individual transition. | |
| WVARCHAR(255) | NULL |
The name of the scenario. | ||
| NUMERIC(19) | NULL |
The last time this scenario was modified. | ||
| VARCHAR(40) | NULL |
The ID of the server handling the transition. The value is a combination of a server name and | ||
| LONG VARBINARY | NULL |
The serialized JMS message bean that caused this scenario transition to occur. | ||
| VARCHAR(255) | NULL |
The type of the JMS event that caused this scenario transition to occur. | ||
| WVARCHAR(255) | NULL |
The name of the scenario segment. | ||
| VARCHAR(16) | NULL |
The state in the scenario state machine of the individual scenario instances at the start of the transition. | ||
| VARCHAR(25) | NULL |
The repository ID last used in a repository query. When a transition action is executed, for example, it is executed on a batch of individual scenario instances at a time. This value is used to keep track of the location in the process of cycling through the scenario instances. | ||
dss_deletion
This table contains information about pending scenario deletions. An entry is created in this table when a scenario is marked as disabled, which means that all the scenario’s instances must be deleted. The Scenarios module typically cannot complete this deletion in a single transaction because of the potentially large number of scenario instances involved, so it stores the pending deletion in the database and completes the operation over multiple transactions.
Column | Data Type | Constraint |
|---|---|---|
| VARCHAR(25) | NOT NULL |
(primary key) | The ID associated with the pending deletion. | |
| WVARCHAR(255) | NULL |
The name of the scenario. | ||
| NUMERIC(19) | NULL |
The last time this scenario was modified. | ||
dss_del_seg_name
This table stores a list of the names of scenario segments that are pending deletion.
Column | Data Type | Constraint |
|---|---|---|
| VARCHAR(25) | NOT NULL |
(primary key) | The unique identifier for the scenario that contains the segment. | |
| INT | NOT NULL |
(primary key) | An index used to order the segments pending deletion. | |
| VARCHAR(255) | NULL |
The name of the segment pending deletion. | ||
