forcedotcom/sf-skills / skills/platform-policy-rule-generate
platform-policy-rule-generate
VerifiedTHE skill for creating a Data Cloud / Data Governance access policy — authors and deploys a PolicyRuleDefinitionSet + PolicyRuleDefinition pair (CRUD) covering OLS, FLS, RLS, masking/transform, and tag/classification-based access for the DATACLOUD or ALL consumer. TRIGGER when the user wants to create/write/author a Data Cloud or Data Governance policy, access policy, or policy rule, or to grant access to a Data Cloud object THROUGH A POLICY — a Data Cloud policy-create request routes here, not to the tag/classification surface. Resolves every reference via Data 360 MCP. SCOPE: Data Cloud policies only (not Security Center, DSAR, or User Access Policies). DO NOT TRIGGER to create tags/classifications, or to grant object/dataspace access via a PERMISSION SET / RBAC grant (use platform-dataspace-access-configure). For a vague object-access ask, surface both skills and ASK the permission-set way vs the policy way; if unsure the object is Data Cloud, ask which first.
references/resource-expression.md
View on GitHub# Resource Expressions
Use `resourceExpression` when the resource-side operand is computed from a projection instead of a direct path. The condition must use `<resourcePath>EXPRESSION</resourcePath>`.
A transform argument list is different: it is a top-level `resourceExpression` on the rule, not inside a condition. Use `ARGLIST` exactly as documented in `policy-shapes.md` and the retrieved masking example.
The validated RLS join shape is:
```xml
<conditions>
<clause>WHEN</clause>
<operator>EXISTS</operator>
<policyRuleDefinitionCondition>
<clause>WHEN</clause>
<operator>EQUALS</operator>
<policyRuleValueSet>
<valueText>${User.Email}</valueText>
</policyRuleValueSet>
<resourcePath>RECORDFIELD</resourcePath>
<valueDomain>RESOURCE_DMO:RESOURCE_FIELD</valueDomain>
</policyRuleDefinitionCondition>
<resourceExpression>
<projection>
<join>
<alias>JOIN_ALIAS</alias>
<predicate>
<attribute>JOIN_DMO:JOIN_FIELD</attribute>
<comparator>EQUALS</comparator>
<on>
<field>RESOURCE_FIELD</field>
<resourceAlias>resource</resourceAlias>
<schema>RESOURCE_DMO</schema>
</on>
</predicate>
<schema>JOIN_DMO</schema>
</join>
</projection>
<type>PROJECTION</type>
<version>1</version>
</resourceExpression>
<resourcePath>EXPRESSION</resourcePath>
<whereClauseConjunction>1</whereClauseConjunction>
</conditions>
```
For a join, define an `<alias>`, a `<schema>`, and a `<predicate>`. `<attribute>` belongs to the joined schema; `<on>` identifies the evaluated resource schema and field. Verify that join keys have compatible types. `whereClauseConjunction` numbers the nested `policyRuleDefinitionCondition` elements from `1`; it does not refer to top-level rule conditions.
Do not invent projection structure or substitute a different operator. Start from a retrieved, deployed example for the same relationship shape and change only resolved schema, field, and alias values while preserving which side is joined and which side is the evaluated resource.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |