Glossary
Pega Community Wiki | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
An optional add-on that integrates Pega Platform data with information from other systems of record. Enabling the BIX ruleset allows extraction of data from the Pega Platform database. The BIX Extract rule defines the class, page, and properties from which to create extract files.
A Data Designer grid that lets you review and manage the selected data type's properties. The composition grid appears on the Definition tab of a data type.
The primary page that against which a flow runs. An interest page might be an embedded page of the case, or it might be the case itself.
A single-value text property that has values that are expected to match the key of an instance of a concrete class. In certain user interface and other rule configurations, linked properties can improve performance and eliminate the need to create a special-purpose activity. You can reference properties of a linked object, retrieved by a linked property, in a rule form or expression using the syntax .LinkedPropertyName.ObjectPropertyReference.
An application-specific access control element that is associated with a class and an access role. Using privilege rules in an application is optional, but they can offer improved control over access than access roles alone.
Defines the results that a decision strategy produces. The Strategy Result (SR) class is a subclass of the standard Data-pxStrategyResult class (either through pattern or direct inheritance).
The Data-pxStrategyResult class contains a set of predefined properties (for example, pyIssue, pyGroup). The SR class can be extended with application-specific properties.