Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Adaptive Decision Manager data model

Updated on July 5, 2022

The Adaptive Decision Manager (ADM) database tables are part of the PegaDATA schema. The state of the ADM system is maintained in memory and regularly serialized to a database.

The frequency of serialization is determined by the backup interval setting. The state is also updated when you stop the ADM service.

ADM database tables

The following table describes each ADM table and the name of the class to which it belongs.

Database tableClassDescription
PR_DATA_ADM_CONFIGURATIONData-Decision-ADM-DB-ConfigurationTable containing ADM configurations. There is one configuration per each Adaptive Model rule. Each configuration is typically associated with multiple factories.
PR_DATA_ADM_FACTORYData-Decision-ADM-DB-FactoryTable containing ADM factories. Each factory is an individual model, for example, proposition X in channel Y.

ADM properties

The ADM data model uses the following properties:

  • Properties in the Configuration table
  • Properties in the Factory table

Properties in the Configuration table

The following properties are defined in the Data-Decision-ADM-DB-Configuration class.
PropertyDescription
pyConfigPartitionID

Primary key. Hash code (version 5 UUID) of pyConfigPartition.

This property originates from the Data-Decision-ADM-DB-ConfigPartition parent class.

pyConfigPartition

The partition that identifies this configuration in canonical JSON format. The partition is a combination of a key-value, where pyClassName and pyPurpose are the keys.

This property originates from the Data-Decision-ADM-DB-ConfigPartition parent class.

pyFormatThe data serialization format (BSON) that is used to serialize the configuration.
pyConfigurationThe serialized representation of the configuration. The serialization format used is specified in pyFormat.

Properties in the Factory table

The following properties are defined on the Data-Decision-ADM-DB-Factory class.
PropertyDescription
pyModelPartitionIDPrimary key. Hash code (version 5 UUID) of pyModelPartition.
pyConfigPartitionID

Primary key. Hash code (version 5 UUID) of pyConfigPartition.

This property originates from the Data-Decision-ADM-DB-ConfigPartition parent class.

pyModelPartitionThe partition for which the factory should produce a model in canonical JSON format. Models are created for every unique combination of proposition and channel internally represented by key-value pairs, where pyIssue, pyGroup, pyName, pyDirection, and pyChannel are the default keys. You can change the default keys and define your own. For more information, see Adding model identifiers.
pyConfigPartition

The partition identifying the configuration in canonical JSON format.

This property originates from the Data-Decision-ADM-DB-ConfigPartition parent class.

pyFormatThe data serialization format (BSON) used to serialize the factory.
pyFactoryThe serialized representation of the factory. The serialization format used is specified in the pyFormat column.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us