Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Default fact properties in Pega 7.2 to 7.3

Suggest edit Updated on October 16, 2017

You define properties that have a wide range of unique values as fact properties. Numeric fact properties can be used as key performance indicators and visualized as such in Visual Business Director.

Default fact properties are one type of Interaction History property that are part of the Interaction History data model. For more information, see Interaction History data model in Pega 7.2 to 7.3.

The following fact properties are defined on the Data-Decision-IH-Fact class.

PropertyTypeDescription
pxDecisionTimeDateTimeA time stamp when the decision was issued.
pxFactIDDecimalAn automatically generated unique fact record ID. Initially generated IDs start at a random value, and then the value is incremented by 1 for every new ID.
pxInteractionIDDecimalA unique 64-bit identifier for all records that belong to the same interaction.
pxOutcomeTimeDateTimeA time stamp when the record was stored in the Interaction History tables.
pxPriorityDoubleAction priority. This strategy property is set during strategy execution (based on the logic defined in a strategy rule). Priority can be based on, for example, margin, propensity to accept, or multiple parameters.
pxRankIntegerAction rank. This strategy property is set by various shapes during strategy execution (based on the logic defined in a strategy rule).
pyExternalIDTextWork item ID that was set through interaction rules previous to Pega 7.1. This property is not automatically set, but it is defined by a user.
pyGroupIDIdentifierThe ID of the group to which the subject ID belongs.
pyLatitudeDouble

Geographical latitude. It This strategy property enables association of a geographical location with a record. It needs to be set during strategy execution.

Use this property to capture geographic coordinates for the location of the customer when the integration takes place instead of using Location dimension.

pyLongitudeDouble

Geographical longitude. This strategy property enables association of a geographical location with a record. It needs to be set during strategy execution.

Use this property to capture geographic coordinates for the location of the customer when the integration takes place instead of using Location dimension.

pyPartitionKeyInteger

Partition key is a computed value that was stored in the process of writing the interaction record. It is used to distribute interaction history records across different partitions.

If you rely on this property to read interaction records more efficiently, make sure that the number of partitions was defined in the installation and configuration process.
pyPropensityDoubleCalculated propensity for the action. It is the likelihood that a customer will accept a particular proposition. The value for propensity is within the range of 0 to 1.
pySubjectIDIdentifierThe subject ID that was used when setting the results of the strategy. It represents the identity (the customer) with whom the integration was handled.
Foreign keys corresponding to primary keys (pzIDs) in each dimension table:
pzActionIDDecimalUnique Action dimension record ID.
pzApplicationIDDecimalUnique Application dimension record ID.
pzChannelIDDecimalUnique Channel dimension record ID.
pzContextIDDecimalUnique Context dimension record ID.
pzCustomerIDDecimalUnique Customer dimension record ID.
pzLocationIDDecimalUnique Location dimension record ID.
pzOperatorIDDecimalUnique Operator dimension record ID.
pzOutcomeIDDecimalUnique Outcome dimension record ID.
Did you find this content helpful? YesNo

100% found this useful

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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