Atlas — Standard classes derived from the Data- base class |
About thirty standard concrete classes derived from the Data- base class record information entered by developers or other staff. See Data- classes by class name for information on these.
Your system also includes several concrete Data- classes that it uses internally while it operates. The installation process creates instances of many of these classes. Later, as the system operates, it creates instances of others indirectly. In most cases no form is defined, so you cannot directly review the instances of these classes.
For a list of those concrete Data- classes that developers can maintain using forms, see Data classes by name.
A dot () marks those classes for which instances are persistent — saved to the PegaRULES database.
Class |
Description |
Data-Address-Email | Stores e-mail addresses used in correspondence. May be referenced in Correspondence Type rules. |
Data-Address-Fax | Stores fax number addresses used in correspondence. May be referenced in Correspondence Type rules. |
Data-Address-PhoneText | Stores phone text messages used in correspondence. May be referenced in Correspondence Type rules. |
Data-Address-Postal | Stores street addresses used in correspondence. May be referenced in Correspondence Type rules. |
Data-Admin-ArchiveSettings | Supports the Purge/Archive wizard. |
Data-Admin-IS-ClientSimulation | Supports unit testing of service rules with the Run toolbar button. |
Data-Admin-OperatorPassword | Supports the optional password management facility. Defined in the PegaPwdControl RuleSet. |
Data-Admin-Product | Stores information used by Product rule processing during upload. |
Data-Admin-Security | Supports the Access Role Editor. |
Data-Admin-Skill | Associates skill ratings with operators. Skill names are rules, not data objects. |
Data-Admin-SysMaint | Supports reporting features of the portal. |
Data-Admin-UnavailablePeriod | Supports recording of periods when a user is unavailable, corresponding to dates entered in the Scheduled Absences array on the Availability tab of the Operator ID form. |
Data-Agent | Saves the last time the agent was awakened. |
Data-Assignment-Summary | Supports reporting on
assignments, through a database table
pcv4_assignment_summary . If you create a
custom table to hold work objects (to supplement the
standard table pc_work ), you must adjust the
database view definition. See Working
with the PegaRULES database — Views and Indexes
and Pega Developer Network article
PRKB-16912 How to customize the display of a
worklist. |
Data-Assignment-WBSummary | Supports reporting on
assignments, through a database table
pcv4_assignmentwb_summary . If you create a
custom table to hold work objects (to supplement the
standard table pc_work ), you must adjust the
database view definition. See Working
with the PegaRULES database — Views and
Indexes. |
Data-Assistant | Not used. |
Data-AutoTest-AutoGen | Supports testing of decision tables; part of the Automated Testing feature. See About the Automated Testing feature. |
Data-AutoTest-Result-Case | Holds results of tests; part of the Automated Testing feature. See About the Automated Testing feature. |
Data-AutoTest-Result-Suite | Holds results of tests; part of the Automated Testing feature. See About the Automated Testing feature. |
Class |
Description |
Data-CESettings | Retains your preferences on the clipboard. See Developer portal basics — Preferences. |
Data-Circumstance-Duplicates | Supports problem reporting with rules that contain circumstance properties. Linked to a view in the PegaRULES database. See Working with the PegaRULES database — Views and Indexes. |
Data-ConnectHTTPStatus | Supports runtime operations of Connect HTTP rules. About Connect HTTP rules. |
Data-Corr-Email | Holds outgoing e-mail correspondence. May be referenced in Correspondence Type rules. |
Data-Corr-Fax | Holds outgoing fax correspondence. May be referenced in Correspondence Type rules. |
Data-Corr-Letter | Holds the body of letter or fax correspondence. May be referenced in Correspondence Type rules. |
Data-Corr-PhoneText | Holds the body of phone text correspondence. May be referenced in Correspondence Type rules. |
Data-COS-Class-DB | Supports communications between the Process Commander engine and the Correspondence Output Server. Used internally by Rule-Connect-SQL rules to write SQL statements. |
Data-COS-Admin-RDB-SQL Data-COS-RDB-SQL-* |
Supports communications between the Process Commander engine and the Correspondence Output Server. |
Data-COS-Servers-Default | Holds an instance for each installed Correspondence Output Server, identifying the COS database. |
Data-Cover-Associations | Not used. |
Data-Customer | Deprecated. Use Data-Party-Person or Data-Party-Org. |
Data-DBSummary-RDBList | Referenced in the RDB-List method for reports. |
Data-DBSummary-Union | Not used. |
Data-DecisionLogicSupport | Supports decision rule form processing. |
Data-DecisionRulePath | Supports decision rule form processing. |
Data-DisplayProperties | Abstract. Supports harness rule operations. |
Data-EmailAttachments | Supports creation of outgoing e-mail attachments (as part of correspondence) from work object attachments. |
Data-Email-Receive | Not used. |
Data-Event-Pattern | Supports scheduled processing of Agent Schedule instances (Data-Agent-Queue). |
Data-Gadget | The Applies To class of activities that define the gadgets in the tabs of the portal. Referenced in portal rules. No instances. |
Data-IS-ClientSimulation | Supports interactive testing of service rules with the Run toolbar button. |
Data-Management-Target | Supports the Product Migration wizard. See About the Product Migration wizard. |
Data-MO | Reserved. Supports models for flow rules based on flow rule category. |
Data-MO-Activity | Reserved. Supports models for flow rules based on flow rule category. |
Data-MO-Connector | Reserved. Supports models for flow rules based on flow rule category. |
Data-MO-Event | Reserved. Supports models for flow rules based on flow rule category. |
Data-MO-Freeform | Reserved. Supports models for flow rules based on flow rule category. |
Data-MO-Gateway | Reserved. Supports models for flow rules based on flow rule category. |
Data-MOD | Reserved. Supports models for flow rules based on flow rule category. |
Data-MQMessage | Contains WebSphere MQ messages created through operation of the Service MQ or Connect MQ interfaces. |
Data-Parse-State | Supports Rule-Parse-Structured processing. See About Parse Structured rules. |
Data-Party-Com | Used in work party configuration, generally for businesses that have a domain ending in ".com." Can be referenced in Work Parties rule instances. Contains the PartyDisplay HTML rule that can appear on the work object entry form.When users complete the party fields on a work object entry form that uses a Rule-Obj-WorkParties rule referencing this class, they create instances of this class. |
Data-Party-Gov | Used in work party configuration. Can be referenced in Work Parties rule instances. Contains the PartyDisplay HTML rule that can appear on the work object entry form. When users complete the party fields on a work object entry form that uses a Rule-Obj-WorkParties rule referencing this class, they create instances of this class. |
Data-Party-Operator | Used in party configuration. Can be referenced in Work Parties rule instances. Contains the PartyDisplay HTML rule that can appear on the work object entry form. When users complete the party fields on a work object entry form that uses a Rule-Obj-WorkParties rule referencing this class, they create instances of this class. |
Data-Party-Org | Used in party configuration for nonprofit organizations. Can be referenced in Work Parties rule instances. Contains the PartyDisplay HTML rule that can appear on the work object entry form. When users complete the party fields on a work object entry form that uses a Rule-Obj-WorkParties rule referencing this class, they create instances of this class. |
Data-Party-Person | Used in party configuration. Can be referenced in Work Parties rule instances. Contains the PartyDisplay HTML rule that can appear on the work object entry form. When users complete the party fields on a work object entry form that uses a Rule-Obj-WorkParties rule referencing this class, they create instances of this class. |
Data-PerfTest | Used by the Performance Test utility to support performance benchmarking. |
Data-Portal | Contains facts about your portal appearance and gadgets appearing on your portal. |
Data-Project-Group | A data table that supports the Project Explorer. See About the Project Explorer and project management interface. |
Data-Project-Name | A data table that supports the Project Explorer. See About the Project Explorer and project management interface. |
Data-Project-Task | A data table that supports the Project Explorer. See About the Project Explorer and project management interface. |
Data-Report-Aging | Contains data supporting aging reports. |
Data-Rule-Locking | Supports reporting on
checked-out rules, through the
pcbv4_rule_locking database view. |
Data-Rule-Overrides | Supports reporting through
the prbv4_rule_overrides database view. |
Data-Rule-Summary | Supports searching and
reporting on rules through the pr4_rule_vw
database view. See How to
report on multiple rule types. |
Data-RuleSearch | Supports the Lucene-based search facilities. In a multinode system, uses Connect SOAP and Service SOAP rules. |
Data-Saved-Context | Contains saved requestor contexts. |
Data-ServiceMessage | Used only passing service parameter data at runtime, and by Service Email rules for attachments. |
Data-ServiceSimulation | Supports testing of service rules with the Run button. |
Data-Spellchecker | Supports spellchecking processing. |
Data-SystemStart | Not used. |
Data-TRACERSettings | Holds a user's settings for the Tracer tool. |
Data-UI-Component-* | Internal classes supporting presentation of work object forms derived from harness, section, and flow action rules. |
Data-UniqueID | Stores next available unique work object or other ID number. |
Data-Upgrade | Reserved. Used internally only. |
Data-VERB-Registry | Supports the Virtual Enterprise Repository facility. See Virtual Enterprise Repository. |
Data-VERB-Repository | Supports the Virtual Enterprise Repository facility. See Virtual Enterprise Repository. |
Data-Work-History | Supports reporting through
the pcv4_work_history database view. |
Data-Work-Summary | Supports advanced reporting about work objects using Lucene search indexes. |
Data-WorkAttach-File | Contains files attached to work objects. See attachment. |
Data-WorkAttach-Note | Contains text notes attached to work objects. See attachment |
Data-WorkAttach-ScanDocument | Contains scanned documents (TIFF images) attached to a work object. See attachment, Scan Station. |
Data-WorkAttach-ScreenShot | Contains Screen Shot image attachments to a work object. See attachment. |
Data-WorkAttach-URL | Contains URL attachments to a work object. |
Working with the PegaRULES database — Tables for data objects