@pega/sdk 0.0.13 → 0.0.14

package/templates/angular-sdk-reference/src/components/templates/default-form/default-form.component.ts

@@ -0,0 +1,101 @@
+/**
+ * DefaultForm — renders form fields in a configurable grid layout (1/2/3 columns).
+ *
+ * Reads NumCols from config to determine grid layout. Children are the form field
+ * components rendered via PConnectBridge.
+ *
+ * Pattern reference: angular-sdk-components DefaultFormComponent + sdk-react DefaultForm
+ */
+
+/* eslint-disable @typescript-eslint/no-explicit-any */
+import { Component, Input, ChangeDetectorRef, NgZone } from '@angular/core';
+import type { OnInit, OnDestroy } from '@angular/core';
+import { CommonModule } from '@angular/common';
+import type { Unsubscribe } from '@pega/sdk-angular';
+import { PConnectBridgeComponent } from '@pega/sdk-angular';
+
+@Component({
+  selector: 'pega-default-form',
+  standalone: true,
+  imports: [CommonModule, PConnectBridgeComponent],
+  template: `
+    <div
+      *ngIf="instructions"
+      style="margin-bottom: 0.75rem; color: #6b7280; font-size: 0.875rem;"
+      [innerHTML]="instructions"
+    ></div>
+    <div [style.display]="'grid'" [style.gridTemplateColumns]="gridColumns" [style.gap]="'1rem'">
+      <div *ngFor="let getter of childGetters">
+        <pconnect-bridge [getPConnect]="getter"></pconnect-bridge>
+      </div>
+    </div>
+  `,
+})
+export class DefaultFormComponent implements OnInit, OnDestroy {
+  @Input() props: any;
+
+  gridColumns = 'repeat(1, minmax(0, 1fr))';
+  instructions = '';
+  childGetters: Array<() => typeof PConnect> = [];
+
+  private pConn: any;
+  private observable: any;
+  private storeUnsub: Unsubscribe | undefined;
+
+  constructor(
+    private ngZone: NgZone,
+    private cdr: ChangeDetectorRef,
+  ) {}
+
+  ngOnInit(): void {
+    this.pConn = this.props.getPConnect();
+    // @ts-ignore
+    const { PConnectObservable } = PCore.getInitialiser().getSdkCore() as any;
+    this.observable = new PConnectObservable(this.pConn);
+    this.updateSelf();
+
+    this.storeUnsub = this.observable.subscribe(() => {
+      this.updateSelf();
+    });
+  }
+
+  ngOnDestroy(): void {
+    this.storeUnsub?.();
+    this.observable?.destroy();
+  }
+
+  private updateSelf(): void {
+    const configProps = this.pConn.getConfigProps();
+    const numCols = configProps.NumCols ?? '1';
+    this.instructions = configProps.instructions ?? '';
+
+    switch (numCols) {
+      case '2':
+        this.gridColumns = 'repeat(2, 1fr)';
+        break;
+      case '3':
+        this.gridColumns = 'repeat(3, 1fr)';
+        break;
+      default:
+        this.gridColumns = 'repeat(1, minmax(0, 1fr))';
+        break;
+    }
+
+    // Children: first child's children are the actual form fields
+    const kids = this.pConn.getChildren?.() ?? [];
+    let fields: any[] = [];
+    if (kids.length > 0 && kids[0].getPConnect) {
+      fields = kids[0].getPConnect().getChildren?.() ?? [];
+    } else {
+      fields = kids;
+    }
+
+    this.childGetters = fields.map((child: any) => {
+      return child.getPConnect ?? (() => child);
+    });
+
+    this.ngZone.run(() => {
+      this.cdr.detectChanges();
+    });
+  }
+}

package/templates/angular-sdk-reference/src/components/templates/narrow-wide/narrow-wide.component.ts

@@ -0,0 +1,37 @@
+/**
+ * NarrowWide — narrow-left/wide-right two-column layout (1:2 ratio).
+ *
+ * Pattern reference: angular-sdk-components NarrowWideFormComponent + sdk-react NarrowWide
+ */
+
+/* eslint-disable @typescript-eslint/no-explicit-any */
+import { Component, Input } from '@angular/core';
+import type { OnInit } from '@angular/core';
+import { CommonModule } from '@angular/common';
+import { PConnectBridgeComponent } from '@pega/sdk-angular';
+
+@Component({
+  selector: 'pega-narrow-wide',
+  standalone: true,
+  imports: [CommonModule, PConnectBridgeComponent],
+  template: `
+    <div style="display: grid; grid-template-columns: 1fr 2fr; gap: 1rem;">
+      <div *ngFor="let getter of childGetters">
+        <pconnect-bridge [getPConnect]="getter"></pconnect-bridge>
+      </div>
+    </div>
+  `,
+})
+export class NarrowWideComponent implements OnInit {
+  @Input() props: any;
+
+  childGetters: Array<() => typeof PConnect> = [];
+
+  ngOnInit(): void {
+    const pConn = this.props.getPConnect();
+    const children = pConn.getChildren?.() ?? [];
+    this.childGetters = children.map((child: any) => {
+      return child.getPConnect ?? (() => child);
+    });
+  }
+}

package/templates/angular-sdk-reference/src/components/templates/one-column/one-column.component.ts

@@ -0,0 +1,37 @@
+/**
+ * OneColumn — single-column layout template that renders children vertically.
+ *
+ * Pattern reference: angular-sdk-components OneColumnComponent + sdk-react OneColumn
+ */
+
+/* eslint-disable @typescript-eslint/no-explicit-any */
+import { Component, Input } from '@angular/core';
+import type { OnInit } from '@angular/core';
+import { CommonModule } from '@angular/common';
+import { PConnectBridgeComponent } from '@pega/sdk-angular';
+
+@Component({
+  selector: 'pega-one-column',
+  standalone: true,
+  imports: [CommonModule, PConnectBridgeComponent],
+  template: `
+    <div style="display: flex; flex-direction: column; gap: 0.25rem;">
+      <div *ngFor="let getter of childGetters">
+        <pconnect-bridge [getPConnect]="getter"></pconnect-bridge>
+      </div>
+    </div>
+  `,
+})
+export class OneColumnComponent implements OnInit {
+  @Input() props: any;
+
+  childGetters: Array<() => typeof PConnect> = [];
+
+  ngOnInit(): void {
+    const pConn = this.props.getPConnect();
+    const children = pConn.getChildren?.() ?? [];
+    this.childGetters = children.map((child: any) => {
+      return child.getPConnect ?? (() => child);
+    });
+  }
+}

package/templates/angular-sdk-reference/src/components/templates/two-column/two-column.component.ts

@@ -0,0 +1,37 @@
+/**
+ * TwoColumn — two-column grid layout template.
+ *
+ * Pattern reference: angular-sdk-components TwoColumnComponent + sdk-react TwoColumn
+ */
+
+/* eslint-disable @typescript-eslint/no-explicit-any */
+import { Component, Input } from '@angular/core';
+import type { OnInit } from '@angular/core';
+import { CommonModule } from '@angular/common';
+import { PConnectBridgeComponent } from '@pega/sdk-angular';
+
+@Component({
+  selector: 'pega-two-column',
+  standalone: true,
+  imports: [CommonModule, PConnectBridgeComponent],
+  template: `
+    <div style="display: grid; grid-template-columns: 1fr 1fr; gap: 1rem;">
+      <div *ngFor="let getter of childGetters">
+        <pconnect-bridge [getPConnect]="getter"></pconnect-bridge>
+      </div>
+    </div>
+  `,
+})
+export class TwoColumnComponent implements OnInit {
+  @Input() props: any;
+
+  childGetters: Array<() => typeof PConnect> = [];
+
+  ngOnInit(): void {
+    const pConn = this.props.getPConnect();
+    const children = pConn.getChildren?.() ?? [];
+    this.childGetters = children.map((child: any) => {
+      return child.getPConnect ?? (() => child);
+    });
+  }
+}

package/templates/angular-sdk-reference/src/components/templates/wide-narrow/wide-narrow.component.ts

@@ -0,0 +1,37 @@
+/**
+ * WideNarrow — wide-left/narrow-right two-column layout (2:1 ratio).
+ *
+ * Pattern reference: angular-sdk-components WideNarrowFormComponent + sdk-react WideNarrow
+ */
+
+/* eslint-disable @typescript-eslint/no-explicit-any */
+import { Component, Input } from '@angular/core';
+import type { OnInit } from '@angular/core';
+import { CommonModule } from '@angular/common';
+import { PConnectBridgeComponent } from '@pega/sdk-angular';
+
+@Component({
+  selector: 'pega-wide-narrow',
+  standalone: true,
+  imports: [CommonModule, PConnectBridgeComponent],
+  template: `
+    <div style="display: grid; grid-template-columns: 2fr 1fr; gap: 1rem;">
+      <div *ngFor="let getter of childGetters">
+        <pconnect-bridge [getPConnect]="getter"></pconnect-bridge>
+      </div>
+    </div>
+  `,
+})
+export class WideNarrowComponent implements OnInit {
+  @Input() props: any;
+
+  childGetters: Array<() => typeof PConnect> = [];
+
+  ngOnInit(): void {
+    const pConn = this.props.getPConnect();
+    const children = pConn.getChildren?.() ?? [];
+    this.childGetters = children.map((child: any) => {
+      return child.getPConnect ?? (() => child);
+    });
+  }
+}

package/templates/angular-sdk-reference/src/helpers/event-utils.ts

@@ -0,0 +1,18 @@
+// From DX Components src/utils/event-utils.js
+
+export function handleEvent(actions: any, eventType: string, propName: string, value: string | boolean | number) {
+  switch (eventType) {
+    case 'change':
+      actions.updateFieldValue(propName, value);
+      break;
+    case 'blur':
+      actions.triggerFieldChange(propName, value);
+      break;
+    case 'changeNblur':
+      actions.updateFieldValue(propName, value);
+      actions.triggerFieldChange(propName, value);
+      break;
+    default:
+      break;
+  }
+}

package/templates/angular-sdk-reference/src/helpers/utils.ts

@@ -0,0 +1,38 @@
+export function getOptionList(configProps: any, dataObject: any): any[] {
+  const listType = configProps.listType;
+  let arReturn: any[] = [];
+
+  if (listType) {
+    switch (listType.toLowerCase()) {
+      case 'associated':
+        // data source should be an array
+        if (typeof configProps.datasource === 'object') {
+          arReturn = configProps.datasource;
+        }
+        break;
+
+      case 'datapage':
+        // get data page
+        // eslint-disable-next-line no-case-declarations
+        const dataPage = configProps.datasource;
+        if (typeof dataPage === 'string' && dataObject[dataPage]) {
+          alert('need to handle data page');
+        } else {
+          let listSourceItems = configProps.listOutput;
+          if (typeof dataPage === 'object' && !Array.isArray(listSourceItems)) {
+            listSourceItems = dataPage.source ? dataPage.source : [];
+          }
+          (listSourceItems || []).forEach((item: any) => {
+            item.value = item.text ? item.text : item.value;
+          });
+          arReturn = listSourceItems || [];
+        }
+        break;
+
+      default:
+        break;
+    }
+  }
+
+  return arReturn;
+}

package/templates/angular-sdk-reference/src/helpers/versionHelpers.ts

@@ -0,0 +1,14 @@
+/**
+ * versionHelpers.ts
+ *
+ * Container helper functions that can identify which version of
+ * PCore/PConnect is being run
+ */
+
+export const sdkVersion = '8.7';
+
+export function compareSdkPCoreVersions() {
+  // const theConstellationVersion = PCore.getPCoreVersion();
+
+  console.warn(`Using Constellation version ${PCore.getPCoreVersion()}. Ensure this is the same version as your Infinity server.`);
+}

package/templates/angular-sdk-reference/tsconfig.json

@@ -1,11 +1,12 @@
 {
   "compileOnSave": false,
   "compilerOptions": {
+    "rootDir": "../..",
     "outDir": "./dist/out-tsc",
     "forceConsistentCasingInFileNames": true,
     "strict": true,
     "noImplicitOverride": true,
-    "noPropertyAccessFromIndexSignature": true,
+    "noPropertyAccessFromIndexSignature": false,
     "noImplicitReturns": true,
     "noFallthroughCasesInSwitch": true,
     "sourceMap": true,
@@ -21,7 +22,9 @@
       "@pega/sdk-angular": ["../../packages/sdk-angular/src/index.ts"],
       "@pega/sdk-types": ["../../packages/sdk-types/src/index.ts"]
     },
-    "ignoreDeprecations": "5.0"
+    "ignoreDeprecations": "5.0",
+    "typeRoots": ["../../node_modules/@types", "../../node_modules/@pega"],
+    "types": ["pcore-pconnect-typedefs"]
   },
   "angularCompilerOptions": {
     "enableI18nLegacyMessageIdFormat": false,

package/templates/react-sdk-reference/.ai-common/agents/embedded-flow-expert.md

@@ -90,7 +90,7 @@ Reduce that response to a generatable list by applying the following in order. P
 2. **Keep components that appear in at least one lifecycle view.** A view is out-of-the-box, and therefore not part of the case lifecycle, when its name begins with `py` or `pz`, or when it is `CaseHistory`. Keep a component if it appears in **at least one** view that is not out-of-the-box. A component may legitimately appear in both kinds of view — one lifecycle view is enough to keep it. Drop a component only when every view it appears in is out-of-the-box.
 
 3. **Strip what is never generated, wherever it appears.** This rule is independent of point 2 and applies even to components that passed it:
-   - Structural wrappers the SDK's registry already provides and that render nothing of their own: View, Region, FlowContainer, Assignment, CaseView, RootContainer. Templates traverse through these to reach their children rather than rendering them, so there is no visual contract to implement.
+   - Structural wrappers the SDK's registry already provides and that render nothing of their own: View, Region, FlowContainer, Assignment, CaseView, RootContainer, and reference nodes. Templates traverse through these to reach their children rather than rendering them, so there is no visual contract to implement. A reference node resolves a view by name — including the one an embedded record uses for its inline form — and the runtime already handles it.
    - Any component whose name starts with `px` (internal Pega infrastructure)
    - Chrome the SDK adapter provides and that is never generated: NavBar, DeferLoad, VerticalTabs, DashboardFilter
    - Chrome whose fate point 4 decides rather than the data page: ActionButtons, Stages, MultiStep
@@ -103,9 +103,15 @@ Reduce that response to a generatable list by applying the following in order. P
 
    `Stages` is the counter-example: it is case chrome, never appears in an embedded assignment, and must not be generated for an embedded flow. It stays stripped.
 
-5. **Present the resolved list, and the exclusions with their reasons.** Name what will be generated, then separately name what was dropped because it appears only in out-of-the-box views, and what was stripped because it is never generated. An exclusion the user disagrees with is far easier to catch when it is visible, and a silently missing component surfaces much later as a rendering gap. **Report the starting fields here too** — either the property names the case type accepts at creation, or that none were confirmed and pre-fill will therefore be off. This is the last point before analysis and generation begin, so it is the last cheap moment for the user to correct either one. Then ask whether to proceed.
+5. **Present the resolved list, and the exclusions with their reasons.** Name what will be generated, then separately name what was dropped because it appears only in out-of-the-box views, what was stripped because it is never generated, and what was added because a selected component declares it as a registry dependency. An exclusion the user disagrees with is far easier to catch when it is visible, and a silently missing component surfaces much later as a rendering gap. **Report the starting fields here too** — either the property names the case type accepts at creation, or that none were confirmed and pre-fill will therefore be off. This is the last point before analysis and generation begin, so it is the last cheap moment for the user to correct either one. Then ask whether to proceed.
 
-6. **Beyond the additions in point 4, generate only what this resolved list contains.** Do NOT add components based on assumptions about what a case type might need.
+6. **Beyond the additions in point 4, generate only what this resolved list contains, plus the registry dependencies the selected components declare.** Do NOT add components based on assumptions about what a case type might need.
+
+   Some components are orchestrators: they render no control of their own, and instead resolve other components from the registry at runtime. Reference fields and embedded data fields are the clearest examples — one of them may resolve a table, a repeating-group template, a picker, or a value display depending on how it was configured. Those dependencies are building blocks rather than fields, so they never appear in view metadata and this data page never returns them. A registry lookup that finds nothing degrades to a fallback or a blank render rather than raising an error, so an orchestrator generated on its own looks like a styling fault rather than a missing component.
+
+   A dependency named in a generated component's own skill file is therefore **not** an assumption — it is part of that component's contract. Read each selected component's skill file, collect the registry keys it declares it will resolve, and add any that are neither already registered in the project nor already in the list. The dependency is **transitive**: a dependency's own skill may declare further ones, so repeat until the set stops growing. Record which component required each addition, and report them under point 5 separately from the chrome added by point 4.
+
+   The distinction to hold: a dependency a skill file declares is required, and omitting it produces a component that cannot render. A component you believe a case type might need is not. Never widen the list on your own judgement.
 
 ### Step 0.4 — Proceed to workflows
 
@@ -148,7 +154,7 @@ If the user named a launch point but no render target, the skill infers it from
 7. **Adapt to the customer's framework** — the skills and prompts are framework-agnostic. Determine the customer's framework from their project configuration and apply conventions accordingly.
 8. **Verification is mandatory, and it is not only static** — the generation prompt's checks confirm the generated files are well-formed. They do not confirm the flow runs. Whenever the integration has been wired, finish with `{{SKILL_DIR}}/embedded-flow/run-and-verify-integration.md` and report how far it got. Never declare success on static checks alone.
 9. **Case type class must be used** — the confirmed case type class must be written into `sdk-config.json` (in the `appMashupCaseType` field) and used in the bootstrap/wiring module when calling the mashup API to create a case.
-10. **Only generate server-resolved components** — generate exactly what Step 0.3 produced: the components the case type's data page returned and that survived its filters, plus the additions point 4 names (`FieldValueList`, `ActionButtons`, and `MultiStep` for a multi-step case). Do NOT add anything else based on assumptions about what a case type might need.
+10. **Only generate server-resolved components, their declared dependencies, and the named chrome** — generate exactly what Step 0.3 produced: the components the case type's data page returned and that survived its filters, the additions point 4 names (`FieldValueList`, `ActionButtons`, and `MultiStep` for a multi-step case), and the registry dependencies that the selected components' own skill files declare, resolved transitively per point 6. Do NOT add anything else based on assumptions about what a case type might need.
 11. **Never silently replace existing behaviour, and never assume where the flow renders** — before anything is written, resolve the launch point and the render target. If the named control already does something, ask whether to override; if they decline, stop the whole flow, do not embed on a different control, and do not leave partial edits behind. If the render target was never stated and cannot be inherited from the control's existing behaviour, ask. See Step 0 of the wire-integration skill.
 12. **Never handle credentials** — when verification reaches the Pega login form in the browser, a human signs in at a visible window. Do not request, capture, log, echo, or store those credentials, at any stage and under any failure condition.
 
@@ -164,6 +170,7 @@ If the user named a launch point but no render target, the skill infers it from
 | Every component is removed by the lifecycle filter               | The case type may have no lifecycle views. Show the views that were returned, explain that all of them are out-of-the-box, and ask the user to confirm before proceeding                                                                                                                                                                       |
 | Customer's project uses an unfamiliar framework                  | Read the framework's documentation (if accessible) + rely heavily on the representative components from the Design Profile                                                                                                                                                                                                                     |
 | A requested component has no skill file                          | The name is not a Pega component name. Resolve it to a canonical one using the staged process in Step 1 of the generation prompt (normalized name, then alias table, then behaviour class, then ask the user), implement that component's skill, and tell the user which substitution you made                                                 |
+| A generated component renders blank or shows the fallback        | Most likely a registry dependency it resolves at runtime was never generated. Orchestrator components fail this way silently. Re-read that component's skill file, collect the registry keys it declares, and confirm each one is registered — see point 6 of Step 0.3. Do not treat it as a styling fault                                     |
 | Design Profile extraction finds no clear patterns                | Ask the user to point to specific example components in their codebase                                                                                                                                                                                                                                                                         |
 | Generated component fails type check after 2 retries             | Report the specific error, show the problematic code, and ask the user for guidance                                                                                                                                                                                                                                                            |
 | Customer uses multiple design systems in one project             | Ask which one should be used for the Pega components, or default to the one used for form elements                                                                                                                                                                                                                                             |

package/templates/react-sdk-reference/.ai-common/prompts/component-manifest.json

@@ -29,6 +29,11 @@
       { "name": "Decimal", "path": "src/components/field/Decimal" },
       { "name": "Dropdown", "path": "src/components/field/Dropdown" },
       { "name": "Email", "path": "src/components/field/Email" },
+      { "name": "EmbeddedData", "path": "src/components/field/EmbeddedData" },
+      {
+        "name": "EmbeddedDataMulti",
+        "path": "src/components/field/EmbeddedDataMulti"
+      },
       { "name": "Group", "path": "src/components/field/Group" },
       { "name": "Integer", "path": "src/components/field/Integer" },
       { "name": "Location", "path": "src/components/field/Location" },
@@ -274,6 +279,8 @@
     "web address": ["URL"],
     "formatted rich text entry": ["RichText", "RichTextEditor"],
     "list of simple values": ["ScalarList"],
+    "a record stored on the case itself": ["EmbeddedData"],
+    "a list of records stored on the case itself": ["EmbeddedDataMulti"],
     "reference to another record": ["ObjectReference"],
     "reference to a person": ["UserReference", "Operator"],
     "geographic location": ["Location"],

package/templates/react-sdk-reference/.ai-common/prompts/generate-all-components.md

@@ -193,7 +193,9 @@ Intersect the confirmed selection with the type scope from Step 0, group the res
 - Step 3 checks for existing files only within the generation set.
 - Steps 4–8 each generate only the components of their type that are in the generation set, and are skipped entirely when it holds none of their type.
 
-Generate nothing outside the generation set. Do not add components based on assumptions about what a portal might need.
+Generate nothing outside the generation set, with one exception: the registry dependencies that the selected components' own skill files declare. Some components are orchestrators — they render no control of their own and instead resolve other components from the registry at runtime, as reference and embedded data fields do. Those dependencies are building blocks rather than fields, so they never appear in view metadata and no data source above returns them, and a registry lookup that finds nothing degrades to a blank render rather than raising an error. Read each selected component's skill file, collect the registry keys it declares it will resolve, and add any that are neither already registered nor already in the set; repeat until the set stops growing, since a dependency's own skill may declare further ones. Report these additions in the Step 9 summary, naming which component required each.
+
+A dependency a skill file declares is required. A component you believe a portal might need is not — do not add components based on assumptions about what a portal might need.
 
 ---
 

package/templates/react-sdk-reference/.ai-common/skills/field-components.md

@@ -45,6 +45,50 @@ Extend the field input contract for component-specific additional inputs (e.g.,
 
 ---
 
+## Condition Encoding
+
+Several configuration settings describe a _condition_ rather than a fixed value. This section states their contract once; individual field skills may reference it instead of restating it.
+
+### The six shapes
+
+A condition-style setting can arrive in one of six forms: absent, the boolean true, the boolean false, an empty string, an expression-marked string, or a When-Rule-marked string. **All six are already resolved to a plain boolean by the runtime before the component receives the input.**
+
+This applies to `readOnly`, `required`, `disabled`, `visibility`, the nested visibility that governs a field-input warning message, and the same settings on any nested field descriptor. Because a descriptor is itself an ordinary field, the contract applies **recursively** to every level of nesting.
+
+### Consequences
+
+- Type every one of these inputs as a plain boolean. Never inspect its raw string form.
+- Never treat a non-empty string as automatically true. Doing so makes every expression-based or rule-based setting permanently active — the single most common way to get this wrong.
+- Treat absent, an empty string, and an explicitly-emitted default value as equivalent to the setting's documented default.
+- Ensure a resolved `disabled` or `readOnly` genuinely prevents interaction, rather than being accepted as an unused input.
+
+### Key presence never indicates intent
+
+Configuration does not clear a setting's key consistently when its control stops being relevant. All of the following occur:
+
+- A control that becomes hidden may leave its last value behind as a stale key.
+- A control that becomes hidden may instead have its key cleared.
+- A key cleared by one change may reappear later carrying a **re-seeded default**, not the value that was last configured for it.
+- Some presentations emit a setting's default explicitly while others omit it entirely, for the identical setting at the identical value.
+
+Therefore: decide which settings are active from the component's mode and presentation, never from which keys are present, and never assume a key's value reflects the last choice made for it.
+
+### Convenience visibility choices
+
+Visibility offers extra options phrased as "if not blank" and "if not zero". These are authoring conveniences that compile to ordinary expressions evaluated against the field's own bound value — they introduce no new value shape. They are offered only where the field has a single scalar bound value to test; a field bound to a list, or one presented as an embedded form, offers only the always / expression / rule choices.
+
+Never implement show/hide logic from `visibility`. A field whose visibility resolves to false is not rendered by the surrounding runtime at all.
+
+### Exception: conditions scoped to a single row
+
+A condition that governs an individual row of a list does **not** arrive resolved.
+
+Such a setting must be read from the component's **raw** configuration — the resolved inputs do not carry it — and evaluated per row against that row's own data, using the platform's expression engine. The configuration surface offers these settings only three choices: never, always, and a custom condition. The When-Rule option is deliberately absent, because a When Rule resolves once and cannot vary from row to row.
+
+Two failure modes to avoid. Typing such a setting as a boolean silently discards the per-row behaviour and applies one verdict to the whole list. Truthiness-checking the raw marked string makes the action permanently available for every row. Handle the three real cases explicitly: absent or true means allowed, an expression means evaluate per row, and anything else means denied.
+
+---
+
 ## Implementation Pattern
 
 ### Abstract Field Component Pattern
@@ -146,35 +190,37 @@ After creating a component, register it in the project's component map: import t
 
 ## Existing Field Components
 
-| Component       | Pega Name       | Description                       |
-| --------------- | --------------- | --------------------------------- |
-| AutoComplete    | AutoComplete    | Typeahead search field            |
-| CancelAlert     | CancelAlert     | Cancel confirmation dialog        |
-| Checkbox        | Checkbox        | Single checkbox with label        |
-| Currency        | Currency        | Currency input with formatting    |
-| Date            | Date            | Date picker                       |
-| DateTime        | DateTime        | Date + time picker                |
-| Decimal         | Decimal         | Decimal number input              |
-| Dropdown        | Dropdown        | Select/dropdown with options      |
-| Email           | Email           | Email input with icon             |
-| Group           | Group           | Field group container             |
-| Integer         | Integer         | Integer-only input                |
-| Location        | Location        | Google Maps location picker       |
-| Multiselect     | Multiselect     | Multi-select dropdown             |
-| ObjectReference | ObjectReference | Reference to another object       |
-| Percentage      | Percentage      | Percentage input                  |
-| Phone           | Phone           | Phone input with country selector |
-| RadioButtons    | RadioButtons    | Radio button group                |
-| RichText        | RichText        | Rich text editor                  |
-| ScalarList      | ScalarList      | List of scalar values             |
-| SelectableCard  | SelectableCard  | Card-style selection              |
-| SemanticLink    | SemanticLink    | Clickable link to another case    |
-| TextArea        | TextArea        | Multi-line text input             |
-| TextContent     | TextContent     | Static text display               |
-| TextInput       | TextInput       | Single-line text input            |
-| Time            | Time            | Time picker                       |
-| URL             | URL             | URL input with validation         |
-| UserReference   | UserReference   | User picker                       |
+| Component         | Pega Name         | Description                                    |
+| ----------------- | ----------------- | ---------------------------------------------- |
+| AutoComplete      | AutoComplete      | Typeahead search field                         |
+| CancelAlert       | CancelAlert       | Cancel confirmation dialog                     |
+| Checkbox          | Checkbox          | Single checkbox with label                     |
+| Currency          | Currency          | Currency input with formatting                 |
+| Date              | Date              | Date picker                                    |
+| DateTime          | DateTime          | Date + time picker                             |
+| Decimal           | Decimal           | Decimal number input                           |
+| Dropdown          | Dropdown          | Select/dropdown with options                   |
+| Email             | Email             | Email input with icon                          |
+| EmbeddedData      | EmbeddedData      | Single embedded record shown as a picker       |
+| EmbeddedDataMulti | EmbeddedDataMulti | List of embedded records (table, groups, tabs) |
+| Group             | Group             | Field group container                          |
+| Integer           | Integer           | Integer-only input                             |
+| Location          | Location          | Google Maps location picker                    |
+| Multiselect       | Multiselect       | Multi-select dropdown                          |
+| ObjectReference   | ObjectReference   | Reference to another object                    |
+| Percentage        | Percentage        | Percentage input                               |
+| Phone             | Phone             | Phone input with country selector              |
+| RadioButtons      | RadioButtons      | Radio button group                             |
+| RichText          | RichText          | Rich text editor                               |
+| ScalarList        | ScalarList        | List of scalar values                          |
+| SelectableCard    | SelectableCard    | Card-style selection                           |
+| SemanticLink      | SemanticLink      | Clickable link to another case                 |
+| TextArea          | TextArea          | Multi-line text input                          |
+| TextContent       | TextContent       | Static text display                            |
+| TextInput         | TextInput         | Single-line text input                         |
+| Time              | Time              | Time picker                                    |
+| URL               | URL               | URL input with validation                      |
+| UserReference     | UserReference     | User picker                                    |
 
 ---