メニュー
Schema and authoring guide for Pega edit validate rules (Rule-Edit-Validate), including Java validation code, error messaging, and property-level validation 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-edit-validate |
| description | Schema and authoring guide for Pega edit validate rules (Rule-Edit-Validate), including Java validation code, error messaging, and property-level validation patterns |
Prerequisite: Load methodology-rule-authoring first
| Skill | Description |
|---|---|
Boolean true validation | Boolean true validation -- checks value is true, adds error message if false |
Not-blank validation | Not-blank validation with error message |
Numeric range validation | Numeric range validation with class scoping |
The pyJavaCode field receives these implicit variables:
theValue (String) -- the property value being validatedtheProperty (ClipboardProperty) -- the property being validated; use theProperty.addMessage("key") to attach error messagestools (PublicAPI) -- standard Pega API for database access, page operations, etc.pega (PegaAPI) -- extended Pega APIThe code must return boolean -- true if valid, false if invalid.
pyValidateName is the identifier used to reference this rule from property definitions. It typically matches pyRuleName. When attaching a validate rule to a property, the property's edit validate field references the pyValidateName.
Validate rules have an empty pyClassName, making them globally available regardless of applies-to class.
Call theProperty.addMessage("messageKey") before returning false. The message key can be:
"pyPleaseSelectARuleSet") that resolves via Pega's localization framework