@sparkerp/plugin-sdk 0.1.0

package/bundle/docs/docs.json

@@ -0,0 +1,109 @@
+{
+  "title": "ERP Plugin Developer Docs",
+  "audience": ["plugin-developer", "application-user"],
+  "audienceNote": "Historically this field was the single string \"tenant\" (per-page frontmatter `audience: tenant|all` is the field that actually gates bundle/build inclusion — see BUNDLE_ALLOWLIST in tools/erp-cli/erp.mjs — this top-level field is informational only, read by no code path). It's now an array because this site genuinely serves two different readers as of the Applications section: plugin-developer (Quickstart/Concepts/Guides/Reference/Tutorial/Recipes/Troubleshooting — build plugins on the platform) and application-user (Applications — use a shipped business-application screen like HCM's Employee Profile). Every individual page still declares its own `audience: tenant` frontmatter regardless of which readership it's written for; \"tenant\" there means \"the customer org\", which is accurate for both readers.",
+  "diataxis": ["quickstart", "concepts", "guides", "reference", "tutorial", "recipes", "troubleshooting", "applications"],
+  "nav": [
+    {
+      "section": "Quickstart",
+      "items": [
+        { "title": "Build and publish a one-page plugin", "path": "quickstart/index.md" }
+      ]
+    },
+    {
+      "section": "Concepts",
+      "items": [
+        { "title": "Platform overview", "path": "concepts/overview.md" },
+        { "title": "What are the artifact types?", "path": "concepts/artifact-types.md" },
+        { "title": "How does a plugin get installed?", "path": "concepts/plugin-lifecycle.md" },
+        { "title": "How do the SDK modes work (monorepo vs connected)?", "path": "concepts/sdk-modes.md" },
+        { "title": "How does a page get its data?", "path": "concepts/page-data-flow.md" },
+        { "title": "Glossary", "path": "concepts/glossary.md" }
+      ]
+    },
+    {
+      "section": "Guides",
+      "items": [
+        { "title": "Set up the SDK and connect to an environment", "path": "guides/set-up-the-sdk.md" },
+        { "title": "Create a plugin from scratch", "path": "guides/create-a-plugin.md" },
+        { "title": "Add an entity", "path": "guides/add-an-entity.md" },
+        { "title": "Build a page", "path": "guides/build-a-page.md" },
+        { "title": "Wire a page's data", "path": "guides/wire-a-pages-data.md" },
+        { "title": "Add a data provider, data view, or data service", "path": "guides/add-a-data-provider.md" },
+        { "title": "Add a create / edit form", "path": "guides/add-a-create-edit-form.md" },
+        { "title": "Add a KPI or aggregation", "path": "guides/add-a-kpi.md" },
+        { "title": "Add an approval workflow", "path": "guides/add-an-approval-workflow.md" },
+        { "title": "Add business rules and expressions", "path": "guides/add-business-rules.md" },
+        { "title": "Add a scheduled reminder job", "path": "guides/add-a-reminder-job.md" },
+        { "title": "Add a cross-row aggregation job", "path": "guides/add-an-aggregation-job.md" },
+        { "title": "Add a cadence-generator job", "path": "guides/add-a-cadence-job.md" },
+        { "title": "Add a compliance-sweep job", "path": "guides/add-a-compliance-job.md" },
+        { "title": "Seed config and reference data on install", "path": "guides/seed-data-on-install.md" },
+        { "title": "Add menus", "path": "guides/add-menus.md" },
+        { "title": "Add translations (i18n)", "path": "guides/add-i18n.md" },
+        { "title": "Make a plugin work on desktop, tablet, and mobile", "path": "guides/responsive-plugin.md" },
+        { "title": "Add a custom block (a \"widget\" you build yourself)", "path": "guides/add-a-custom-block.md" },
+        { "title": "Build a plugin with custom React + Java code (L4)", "path": "guides/build-a-code-plugin.md" },
+        { "title": "Validate and test a plugin", "path": "guides/validate-and-test.md" },
+        { "title": "Publish and upgrade a plugin", "path": "guides/publish-and-upgrade.md" },
+        { "title": "Build a tenant extension service (L5)", "path": "guides/build-a-tenant-extension-service.md" },
+        { "title": "Build a Service-mode plugin in Python or Node.js", "path": "guides/build-a-polyglot-service-plugin.md" },
+        { "title": "Use the MCP server with an AI agent", "path": "guides/use-the-mcp-server.md" },
+        { "title": "Expose a plugin operation as an AI tool", "path": "guides/expose-a-plugin-operation-as-an-ai-tool.md" }
+      ]
+    },
+    {
+      "section": "Reference",
+      "items": [
+        { "title": "Schema reference", "path": "reference/index.md" }
+      ]
+    },
+    {
+      "section": "Tutorial",
+      "items": [
+        { "title": "Overview: build the Office Equipment module", "path": "tutorial/index.md" },
+        { "title": "1. Create the plugin", "path": "tutorial/01-create-the-plugin.md" },
+        { "title": "2. The equipment category entity + seeded data", "path": "tutorial/02-category-entity-and-seed.md" },
+        { "title": "3. The equipment register entity", "path": "tutorial/03-equipment-entity.md" },
+        { "title": "4. The equipment register page", "path": "tutorial/04-equipment-register-page.md" },
+        { "title": "5. The checkout entity, page, and lookups", "path": "tutorial/05-checkout-entity-and-page.md" },
+        { "title": "6. The checkout approval workflow", "path": "tutorial/06-checkout-approval-workflow.md" },
+        { "title": "7. The return-due reminder job", "path": "tutorial/07-return-due-reminder-job.md" },
+        { "title": "8. Menus, i18n, validate, publish", "path": "tutorial/08-menus-i18n-publish.md" }
+      ]
+    },
+    {
+      "section": "Recipes",
+      "items": [
+        { "title": "Recipe index", "path": "recipes/index.md" },
+        { "title": "A searchable related-record lookup field", "path": "recipes/related-record-lookup-field.md" },
+        { "title": "A resolved reference column in a grid", "path": "recipes/resolved-reference-grid-column.md" },
+        { "title": "A KPI dashboard page", "path": "recipes/kpi-dashboard-page.md" },
+        { "title": "A master-detail page with a child grid", "path": "recipes/master-detail-page.md" },
+        { "title": "An entity with an approval workflow", "path": "recipes/entity-with-approval-workflow.md" },
+        { "title": "An N-days-before reminder job", "path": "recipes/n-days-before-reminder.md" },
+        { "title": "A cross-row aggregation into a summary entity", "path": "recipes/cross-row-aggregation.md" },
+        { "title": "A scheduled record-generation cadence", "path": "recipes/scheduled-record-generation.md" },
+        { "title": "A condition-based compliance flag", "path": "recipes/condition-based-compliance-flag.md" },
+        { "title": "A cross-plugin offboarding fan-out", "path": "recipes/cross-plugin-offboarding-fanout.md" },
+        { "title": "A per-row document artifact generator", "path": "recipes/per-row-document-generator.md" },
+        { "title": "Install-lifecycle data seeding", "path": "recipes/install-lifecycle-data-seeding.md" }
+      ]
+    },
+    {
+      "section": "Troubleshooting",
+      "items": [
+        { "title": "Known gotchas", "path": "troubleshooting/known-gotchas.md" },
+        { "title": "Publishing and install errors", "path": "troubleshooting/publishing-errors.md" },
+        { "title": "\"My grid shows 0 rows\"", "path": "troubleshooting/grid-shows-zero-rows.md" },
+        { "title": "\"My scheduled job never runs\"", "path": "troubleshooting/job-never-runs.md" }
+      ]
+    },
+    {
+      "section": "Applications",
+      "items": [
+        { "title": "HCM: Employee Profile", "path": "applications/hcm/employee-profile.md" }
+      ]
+    }
+  ]
+}

package/bundle/docs/guides/add-a-cadence-job.md

@@ -0,0 +1,134 @@
+---
+title: Add a cadence-generator job
+audience: tenant
+---
+
+# Add a cadence-generator job
+
+## What you're doing
+
+"Create new records on a schedule." A quarterly equipment audit, a monthly
+review, a follow-up task N days after some event. **No Java.** One
+`entity_cadence_config` row, run by the generic `engine-entity.cadence-generator`
+job, shipped as seed data.
+
+## Two modes
+
+| Mode | One tick creates | Set |
+| --- | --- | --- |
+| **standalone** | one new record every `interval_days` | `target_entity`, `interval_days`, `template_json`, `dedupe_target_field` |
+| **source-driven** | one record per *due* row of a source entity | also `source_entity`, `source_date_field`, `due_within_days`, `field_map_json` |
+
+## The complete example — standalone quarterly audit
+
+`spk-assembly/metadata/seed-data/office-equipment-cadence-configs.json`
+(standalone example,
+[real file](../examples/standalone-plugin/spk-assembly/metadata/seed-data/office-equipment-cadence-configs.json)):
+
+```json
+{
+  "entity": "entity_cadence_config",
+  "keyFields": ["cadence_code"],
+  "source": "office-equipment",
+  "rows": [
+    {
+      "cadence_code": "equipment-audit-schedule",
+      "target_entity": "oeq_audit",
+      "interval_days": 90,
+      "dedupe_target_field": "cadence_marker",
+      "template_json": {
+        "audit_number": "AUDIT-${date}-${ts}",
+        "audit_name": "Scheduled Equipment Audit ${date}",
+        "status": "DRAFT"
+      },
+      "seeded_by": "office-equipment",
+      "active": true
+    }
+  ]
+}
+```
+
+## Line by line
+
+- **`cadence_code`** — unique id; the natural key.
+- **`target_entity`** — the entity to create rows in.
+- **`interval_days`** — a new row is created only if the last one is older than
+  this many days (tracked in `last_generated_at`).
+- **`dedupe_target_field`** — a column on the target that the job stamps to
+  recognise its own creations and avoid double-generating in one window.
+- **`template_json`** — the field map for the new row. String values support
+  substitutions: `${date}` (today), `${ts}` (a timestamp), `${uuid}`, and (in
+  source-driven mode) `${sourceId}`.
+
+### Source-driven variant
+
+Add:
+
+```json
+"source_entity": "oeq_equipment",
+"source_date_field": "warranty_expiry_date",
+"due_within_days": 30,
+"field_map_json": { "equipment_id": "id", "equipment_tag": "asset_tag" },
+"dedupe_target_field": "equipment_id"
+```
+
+→ for every `oeq_equipment` whose `warranty_expiry_date` is within 30 days and
+which doesn't already have a target row (deduped on `equipment_id`), create one,
+copying `id`→`equipment_id` and `asset_tag`→`equipment_tag`.
+
+## The register rule
+
+`spk-assembly/metadata/rules/ensure_cadence_generator_job_registered.json`:
+
+```json
+{
+  "entityType": "entity_cadence_config",
+  "name": "ensure_cadence_generator_job_registered",
+  "triggerEvent": "AFTER_CREATE",
+  "conditions": null,
+  "actions": "[{\"type\": \"EXECUTE_SERVICE\", \"service\": \"ensureEntityCadenceGeneratorJobRegistered\"}]",
+  "priority": 10,
+  "active": true
+}
+```
+
+## Ground yourself first
+
+```bash
+erp schema pull entity-cadence-config
+erp examples patterns --kind jobs      # "scheduled-record-generation-cadence"
+```
+
+## How to verify it worked
+
+```bash
+erp api get "/api/v1/jobs/engine-entity.cadence-generator"
+# → { "status": "ENABLED", ... }
+
+erp api post "/api/v1/jobs/engine-entity.cadence-generator/execute" --body "{}"
+erp api get "/api/v1/entities/oeq_audit/records/query?size=5"
+```
+
+```json
+{ "rows": [
+  { "audit_number": "AUDIT-2026-09-10-1757492940", "audit_name": "Scheduled Equipment Audit 2026-09-10",
+    "status": "DRAFT", "cadence_marker": "equipment-audit-schedule" }
+], "total": 1 }
+```
+
+Run it again immediately — no new row (interval not elapsed). That's correct.
+
+## Common mistakes
+
+| Symptom | Cause | Fix |
+| --- | --- | --- |
+| a new row every single tick | `interval_days` missing or 0 | set it |
+| duplicate rows | `dedupe_target_field` not set, or not a stable column | in source-driven mode use the source-id column |
+| `${date}` appears literally in a non-string field | substitution only works in string template values | keep templated values as strings |
+| job not registered | no register rule shipped | ship it |
+
+## What to read next
+
+- [Add a compliance-sweep job](./add-a-compliance-job.md)
+- [Seed config and reference data on install](./seed-data-on-install.md)
+- Recipe: [scheduled record-generation cadence](../recipes/scheduled-record-generation.md)

package/bundle/docs/guides/add-a-compliance-job.md

@@ -0,0 +1,139 @@
+---
+title: Add a compliance-sweep job
+audience: tenant
+---
+
+# Add a compliance-sweep job
+
+## What you're doing
+
+"Find rows that break a policy and flag them — or raise an escalation." More
+expressive than a [reminder job](./add-a-reminder-job.md): the condition is a
+**boolean expression** over the row's fields (plus `now` and an optional
+`related_count`), not just one date column. **No Java.** One
+`entity_compliance_config` row, run by `engine-entity.compliance-sweep`, shipped
+as seed data.
+
+Use this instead of a reminder job whenever the condition is more than "one date
+vs now".
+
+## Two outcomes
+
+| Outcome | Set |
+| --- | --- |
+| **FLAG** — set a field on the offending row | `set_field`, `set_value` |
+| **ESCALATION** — raise a row in a separate entity, deduped by source id | `escalation_entity`, `escalation_dedupe_field`, `field_map_json`, `escalation_template_json` |
+
+## The complete example — flag un-acknowledged checkouts
+
+`spk-assembly/metadata/seed-data/office-equipment-compliance-configs.json`
+(standalone example,
+[real file](../examples/standalone-plugin/spk-assembly/metadata/seed-data/office-equipment-compliance-configs.json)):
+
+```json
+{
+  "entity": "entity_compliance_config",
+  "keyFields": ["compliance_code"],
+  "source": "office-equipment",
+  "rows": [
+    {
+      "compliance_code": "checkout-acknowledgement-compliance",
+      "source_entity": "oeq_checkout",
+      "when_status_in": "CHECKED_OUT,DUE_SOON,OVERDUE",
+      "condition_expr": "custody_acknowledged != true && daysBetween(checkout_date, now()) > 7",
+      "set_field": "compliance_flag",
+      "set_value": "NON_COMPLIANT",
+      "seeded_by": "office-equipment",
+      "active": true
+    }
+  ]
+}
+```
+
+## Line by line
+
+- **`compliance_code`** — unique id; natural key.
+- **`source_entity`** — table to evaluate.
+- **`when_status_in`** — optional status pre-filter.
+- **`condition_expr`** — a boolean expression in the platform
+  `ExpressionEvaluator` language. In scope: the row's own fields, `now`, and (if
+  configured) `related_count`. Whitelisted functions only — `daysBetween`,
+  `now`, `coalesce`, arithmetic, `&&`, `||`, `!`, comparisons. **No** ternary,
+  **no** `in`, **no** `^`. A row where the expression is **true** is
+  non-compliant.
+- **`set_field` / `set_value`** — FLAG outcome. Idempotent: a row already equal
+  to `set_value` is skipped.
+
+### Related-count variant (cross-record)
+
+```json
+"related_count_entity": "oeq_license_assignment",
+"related_count_key_field": "license_id",
+"related_count_status_in": "ACTIVE",
+"condition_expr": "related_count > entitlement_quantity"
+```
+
+→ counts `ACTIVE` assignments whose `license_id` equals the source row's id,
+binds it as `related_count`, and flags over-allocated licences.
+
+### Escalation variant
+
+Replace `set_field`/`set_value` with:
+
+```json
+"escalation_entity": "oeq_compliance_case",
+"escalation_dedupe_field": "checkout_id",
+"field_map_json": { "checkout_id": "id", "employee_id": "employee_id" },
+"escalation_template_json": { "status": "OPEN", "severity": "HIGH" }
+```
+
+→ one `oeq_compliance_case` per offending checkout, deduped on `checkout_id`.
+
+## The register rule
+
+`spk-assembly/metadata/rules/ensure_compliance_sweep_job_registered.json`:
+
+```json
+{
+  "entityType": "entity_compliance_config",
+  "name": "ensure_compliance_sweep_job_registered",
+  "triggerEvent": "AFTER_CREATE",
+  "conditions": null,
+  "actions": "[{\"type\": \"EXECUTE_SERVICE\", \"service\": \"ensureEntityComplianceSweepJobRegistered\"}]",
+  "priority": 10,
+  "active": true
+}
+```
+
+## Ground yourself first
+
+```bash
+erp schema pull entity-compliance-config
+erp examples patterns --kind jobs     # "condition-based-compliance-flagging"
+```
+
+## How to verify it worked
+
+```bash
+erp api get "/api/v1/jobs/engine-entity.compliance-sweep"
+# → { "status": "ENABLED", ... }
+
+erp api post "/api/v1/jobs/engine-entity.compliance-sweep/execute" --body "{}"
+erp api get "/api/v1/entities/oeq_checkout/records/query?size=10"
+```
+
+Rows that break the policy now carry `"compliance_flag": "NON_COMPLIANT"`.
+
+## Common mistakes
+
+| Symptom | Cause | Fix |
+| --- | --- | --- |
+| expression parse error | used ternary / `in` / `^` | rewrite with whitelisted operators |
+| nothing flagged | `condition_expr` logic inverted (true = compliant) | true must mean *non*-compliant |
+| `related_count` is always 0 | `related_count_key_field` isn't the FK back to the source id | fix the FK column name |
+| escalations duplicate | `escalation_dedupe_field` not the source-id column | must be a numeric column holding the source id |
+
+## What to read next
+
+- [Add business rules and expressions](./add-business-rules.md) — same expression language
+- Recipe: [condition-based compliance flag](../recipes/condition-based-compliance-flag.md)

package/bundle/docs/guides/add-a-create-edit-form.md

@@ -0,0 +1,167 @@
+---
+title: Add a create / edit form
+audience: tenant
+---
+
+# Add a create / edit form
+
+## What you're doing
+
+Adding a dialog to a list page that creates (or edits) a row. On this platform a
+"form" for a list page is not a separate artifact — it's a `core.dialog` block on
+the page, containing input blocks bound to page state, plus a Save button whose
+action chain `POST`s (or `PUT`s) to the entity.
+
+## The pattern
+
+1. **A "New" button** clears the form's page-state keys and opens the dialog.
+2. **Each field** is an input block (`core.text-input`, `core.select`,
+   `core.date-picker`, `core.number-input`, `core.checkbox`, `core.lookup`)
+   whose `value` binds a page-state key and whose `committed` event writes
+   `${event.new}` back to that key.
+3. **Save** calls `POST /api/v1/entities/<name>/records` with a `params` object
+   built from the page-state keys, closes the dialog, toggles the grid refresh,
+   and shows a toast.
+
+## The complete example
+
+From the tutorial's `equipment-register.json`. The "New" button:
+
+```json
+{
+  "blockType": "core.button",
+  "properties": { "labelKey": { "source": "static", "value": "office-equipment.equipment-register.newBtn" },
+                  "variant": { "source": "static", "value": "contained" } },
+  "events": { "clicked": { "source": "action-chain", "actions": [
+    { "id": "a0", "order": 0, "type": "setValue", "config": { "field": "page.formAssetTag", "value": null } },
+    { "id": "a1", "order": 1, "type": "setValue", "config": { "field": "page.formName", "value": null } },
+    { "id": "a2", "order": 2, "type": "setValue", "config": { "field": "page.formCategoryId", "value": null } },
+    { "id": "a3", "order": 3, "type": "setValue", "config": { "field": "page.formStatus", "value": "AVAILABLE" } },
+    { "id": "a4", "order": 4, "type": "setValue", "config": { "field": "page.formDialogOpen", "value": true } }
+  ] } }
+}
+```
+
+One text field inside the dialog:
+
+```json
+{
+  "blockType": "core.text-input",
+  "properties": { "value": { "source": "binding", "binding": { "scope": "page", "key": "formAssetTag" } } },
+  "events": { "committed": { "source": "action-chain", "actions": [
+    { "id": "a0", "order": 0, "type": "setValue",
+      "config": { "field": "page.formAssetTag", "value": "${event.new}" } }
+  ] } }
+}
+```
+
+The Save button:
+
+```json
+{
+  "blockType": "core.button",
+  "properties": { "labelKey": { "source": "static", "value": "office-equipment.equipment-register.form.saveBtn" },
+                  "variant": { "source": "static", "value": "contained" } },
+  "events": { "clicked": { "source": "action-chain", "actions": [
+    { "id": "a0", "order": 0, "type": "callApi",
+      "config": { "connectionRef": "self", "path": "/api/v1/entities/oeq_equipment/records", "httpMethod": "POST",
+        "params": {
+          "asset_tag": "${page.formAssetTag}",
+          "name": "${page.formName}",
+          "category_id": "${page.formCategoryId}",
+          "status": "${page.formStatus}"
+        } },
+      "output": "createResult" },
+    { "id": "a1", "order": 1, "type": "setValue", "config": { "field": "page.formDialogOpen", "value": false } },
+    { "id": "a2", "order": 2, "type": "setValue", "config": { "field": "page.gridRefreshTick", "value": "${!page.gridRefreshTick}" } },
+    { "id": "a3", "order": 3, "type": "showToast", "config": { "message": "Saved." } }
+  ] } }
+}
+```
+
+## Line by line — the rules that bite
+
+- **`committed` fires with `event.new`.** The value the user just entered is
+  `${event.new}`. **Not** `event.value`, **not** `event.record`. This is true for
+  text inputs, selects, date pickers, checkboxes, and `core.lookup`.
+- **The handler must write back to state.** `committed` → `setValue page.<key> =
+  ${event.new}`. Without this the input shows what you type but page state never
+  updates, and Save sends nulls.
+- **Save reads from `${page.<key>}`** in the `params` object — the same keys the
+  inputs write and the "New" button clears.
+- **Clear the keys in the "New" button**, not on dialog close — so re-opening
+  always starts blank (or with defaults like `status: "AVAILABLE"`).
+- **Booleans and numbers** flow through as their JSON types when you `setValue`
+  a real `true`/`10`; only `defaultValue` in an *entity* file must be a string.
+
+## Editing an existing row
+
+Same dialog. The grid's `rowClicked` event fetches the record and populates the
+same page-state keys, then opens the dialog:
+
+```json
+"events": { "rowClicked": { "source": "action-chain", "actions": [
+  { "id": "a0", "order": 0, "type": "callApi",
+    "config": { "connectionRef": "self", "path": "/api/v1/entities/oeq_equipment/records/${event.id}", "httpMethod": "GET", "params": {} },
+    "output": "detail" },
+  { "id": "a1", "order": 1, "type": "setValue", "config": { "field": "page.formAssetTag", "value": "${detail.asset_tag}" } },
+  { "id": "a2", "order": 2, "type": "setValue", "config": { "field": "page.editingId", "value": "${event.id}" } },
+  { "id": "a3", "order": 3, "type": "setValue", "config": { "field": "page.formDialogOpen", "value": true } }
+] } }
+```
+
+Save then branches on `page.editingId` — `PUT .../records/${page.editingId}` if
+set, `POST` if not. (`${event.id}` is the clicked row's id.)
+
+## A lookup field (foreign key)
+
+```json
+{
+  "blockType": "core.lookup",
+  "properties": {
+    "value": { "source": "binding", "binding": { "scope": "page", "key": "formCategoryId" } },
+    "recordType": { "source": "static", "value": "OeqCategory" },
+    "optionsSourceKey": { "source": "static", "value": "oeq-category-search" }
+  },
+  "events": { "committed": { "source": "action-chain", "actions": [
+    { "id": "a0", "order": 0, "type": "setValue",
+      "config": { "field": "page.formCategoryId", "value": "${event.new}" } }
+  ] } }
+}
+```
+
+`optionsSourceKey` is the `name` of a `search` Data Service. `recordType` is a
+documentation-only label. `${event.new}` is the picked record's id. See
+[the lookup recipe](../recipes/related-record-lookup-field.md).
+
+## How to verify it worked
+
+Publish, then drive it from the API the same way the Save chain does:
+
+```bash
+erp api post "/api/v1/entities/oeq_equipment/records" \
+  --body '{"asset_tag":"LAP-001","name":"Dell Latitude 7440","category_id":1,"status":"AVAILABLE"}'
+```
+
+```json
+{ "id": 1, "created_by": "you@example.com", "asset_tag": "LAP-001",
+  "name": "Dell Latitude 7440", "status": "AVAILABLE", "warranty_alert": false }
+```
+
+If that works, the dialog works.
+
+## Common mistakes
+
+| Symptom | Cause | Fix |
+| --- | --- | --- |
+| Save sends `null` for a field the user filled in | `committed` handler missing or reads `event.value` | write `setValue page.<key> = ${event.new}` |
+| dialog re-opens with last row's data | keys cleared on close instead of on "New" | clear in the "New" button chain |
+| grid doesn't show the new row | no `refreshTrigger` toggle in the Save chain | add `setValue page.gridRefreshTick = ${!page.gridRefreshTick}` |
+| lookup saves a name, not an id | bound the label instead of `${event.new}` | `${event.new}` is the id |
+| `POST` 400s on an enum field | value not one of `typeParams.enumValues` | check the entity's enum list |
+
+## What to read next
+
+- [Add a data provider, data view, or data service](./add-a-data-provider.md)
+- [Add an approval workflow](./add-an-approval-workflow.md) — a Submit button
+- Recipe: [master-detail page with a child grid](../recipes/master-detail-page.md)