القائمة
Schema and authoring guide for Pega class definition rules (Rule-Obj-Class), including work subclasses, data classes, and inheritance patterns
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when the bundled Pega Infinity Authoring Codex plugin needs setup, authentication help, or troubleshooting. Confirm the plugin MCP server first, then verify the bundled runtime and skills payload.
Use when the GitHub Copilot CLI plugin needs connection setup help, environment configuration, or troubleshooting. Guides first-time setup, OAuth configuration, and recovery from connection failures.
Use this skill when the user asks to design or review a data model, choose between Case Type vs. Data Object, model a business process in App Studio or Dev Studio, add or change Case Types or Data Objects, or structure fields, relationships, primary fields, business keys, or attachments within a Pega application.
Load before creating or updating any Pega rules. Covers the ChangeRequest 4-stage lifecycle (intake, authoring, review, complete), branch isolation, case properties, and resuming cases.
Load when building a DX API assignment action payload for runtime case updates. Covers when to use content, when to use pageInstructions, how to combine them, and how to structure supported page, page-list, and page-group instructions for perform-action.
General instructions for creating and updating Pega rules using the schema-backed authoring tools
| name | rules-rule-obj-class |
| description | Schema and authoring guide for Pega class definition rules (Rule-Obj-Class), including work subclasses, data classes, and inheritance patterns |
Prerequisite: Load methodology-rule-authoring first
| Skill | Description |
|---|---|
Stub Class | Minimal class definition -- smallest valid create payload |
Work Subclass | Work class with class group assignment (HASCLASSGROUP) |
Data Class Definition | Data class (NOCLASSGROUP) |
Abstract Class | Abstract class without a trailing dash |
Embed Class | Concrete embedded class deriving from Embed- |
Class Group Root (ISCLASSGROUP) | Class group root (ISCLASSGROUP) -- subclasses point back to this class |
pyClassName is the class keypyClassName is the sole identity key (from pyKeyDefList) and the value
the agent must supply. pyInitialVersion is auto-derived (always
01-01-01) and can be omitted.
Pega validates pyClassName at case type save time. Create the class rule
before any rules that reference the class as an instance (pxObjClass) or
as the applies-to class pyClassName.
pyClassGroupIndicator values| Value | Meaning | pyClassGroup behavior |
|---|---|---|
HASCLASSGROUP | Subclass belonging to a class group | Agent must set pyClassGroup to the group root |
ISCLASSGROUP | This class IS the class group root | Auto-set to pyClassName. Common parents: Work-, Work-Cover-, PegaAccel |
NOCLASSGROUP | No class group (data, embed, etc.) | Auto-set to pyClassName |
When comparing a class created via the API with one created through the Pega UI, the UI-created class will have empty placeholder entries in embedded arrays that the API-created class will not:
pyLockDefList, pyLinks, pyPagesAndClasses, pyValidRuleSets,
pxClassSQL, pyKeyDefList (when no actual keys are defined).
These are cosmetic differences, not functional.