@cxtms/cx-schema 1.9.255 → 1.9.257

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cxtms/cx-schema",
-  "version": "1.9.255",
+  "version": "1.9.257",
   "description": "Schema validation package for CXTMS YAML modules",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

package/schemas/schema.graphql

@@ -11084,6 +11084,7 @@ type orderMoveLeg {
   orderMoveLegStatus: orderMoveLegStatus
   startDate: DateTime
   endDate: DateTime
+  getAddress(idPropertyName: String!): contactAddress
   trackingEvents: [trackingEvent!]
   customValues: MapOfObject
   isDeleted: Boolean!

package/schemas/workflows/tasks/all.json

@@ -25,6 +25,9 @@
     {
       "$ref": "caching.json"
     },
+    {
+      "$ref": "calendar.json"
+    },
     {
       "$ref": "charge.json"
     },

package/schemas/workflows/tasks/calendar.json

@@ -0,0 +1,25 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "title": "Calendar Tasks",
+  "description": "Issue and import iCalendar feed links",
+  "type": "object",
+  "properties": {
+    "task": { "type": "string", "enum": ["Calendar/IssueLink@1", "Calendar/ImportFeed@1"] },
+    "name": { "type": "string" },
+    "description": { "type": "string" },
+    "conditions": { "type": "array" },
+    "continueOnError": { "type": "boolean" },
+    "inputs": {
+      "type": "object",
+      "properties": {
+        "organizationId": {}, "calendarId": {}, "label": {},
+        "organizationConnectionId": {}, "url": {}, "etag": {}
+      },
+      "required": ["organizationId"],
+      "additionalProperties": true
+    },
+    "outputs": { "type": "array" }
+  },
+  "required": ["task", "name", "inputs"],
+  "additionalProperties": true
+}

package/skills/cxtms-developer/ref-entity-dispatch-routing.md

@@ -162,6 +162,7 @@ Vertical-specific routing details belong in `customValues`.
 | `startDate` | `DateTime?` | UTC start |
 | `endDate` | `DateTime?` | UTC end |
 | `customValues` | `Dictionary` | Location, event, appointment, and metric data |
+| `getAddress(idPropertyName)` | `ContactAddress?` | Resolves a contact-address ID from the named `customValues` property; tenant-scoped through the parent move |
 | `trackingEvents` | `[TrackingEvent]` | Leg-level milestones |
 
 Entity-trigger payloads load the status navigation before mapping when necessary. This
@@ -184,6 +185,7 @@ are appended and omitted existing records are not deleted.
 
 - Queries: `dispatchRouteStatus`, `dispatchRouteStatuses`, `dispatchRouteStopStatus`, `dispatchRouteStopStatuses`, `dispatchRouteTemplate`, `dispatchRouteTemplates`, `dispatchRoute`, `dispatchRoutes`.
 - Order move queries: `orderMove`, `orderMoves`, `orderMoveStatus`, `orderMoveStatuses`, `orderMoveLegStatus`, and `orderMoveLegStatuses`.
+- Order-move legs expose `getAddress(idPropertyName: String!)` to resolve an integer contact-address ID from the named `customValues` property. Missing or invalid values return `null`, and cross-organization addresses are never returned.
 - Nested order resolvers: `getOrderMoves(filter, orderBy)` returns pending or statusless moves (defaulted to sequence order), while `getOrderMove(filter, orderBy)` returns the first matching pending or statusless move. Moves whose status stage is no longer `Pending` are excluded.
 - Order move mutations create, sparse-update, and soft-delete moves; create/update accepts nested `orderMoveLegs`, reconciled by ID and array order. Omitted or `isDeleted: true` legs are soft-deleted, new already-deleted legs are ignored, and only active legs consume sequence positions.
 - `createOrderMoveLeg`, `updateOrderMoveLeg`, and `deleteOrderMoveLeg` manage one leg without resending the parent move. Create requires `orderMoveId`, appends after the last active leg when `sequence` is omitted, and accepts name, status, dates, and custom values. Update takes a sparse values map; delete is soft. Each operation is organization-scoped through the parent move.

package/skills/cxtms-module-builder/ref-components-forms.md

@@ -729,7 +729,9 @@ Headless barcode/keyboard scanner listener. Captures rapid keystrokes and fires
 | `maxBarcodes` | `number` | — | Mobile: maximum accepted scans in continuous mode |
 | `onScan` | `action[]` | — | **Required.** Action on scan detection |
 
-**Renders:** Nothing (empty fragment). Web listens on `document` keypress. Mobile supports
+**Renders:** Nothing (empty fragment). Web listens on `document` keydown, ignores form controls
+and non-printable keys, and derives letters, unshifted digits, minus, and period from physical
+key codes to avoid keyboard-layout transformations. Other printable keys use `event.key`. Mobile supports
 native HID scanners with a hidden-input fallback and shares camera-scanner deduplication rules.
 
 **Scan data:** `result: { data: string, format: 'input' }`

package/skills/cxtms-workflow-builder/SKILL.md

@@ -53,6 +53,8 @@ npx cxtms create workflow <name> --template <template>
 
 **All templates** — update `name`, `description`, `tags`, `inputs`, `variables`, replace placeholder steps.
 
+**Workflow overrides** — active workflows in the same organization with the same case-insensitive `workflow.name` form an override group. Only the highest `workflow.priority` is effective (default 50; lowest workflow ID wins ties). Use a higher priority to replace a base-app workflow without modifying it. The rule covers triggers, schedules, execution by name, MCP surfaces, public API routes, and document workflows; deactivating or deleting the winner restores the next-highest definition.
+
 **`entity-trigger`** — set `entityName`, `eventType` (Modified/Created/Deleted), `position` (Before/After), `conditions` on `changes`. Access entity via `{{ entity.* }}`. Before: use `Validation/Validate@1`. After: cascade changes.
 
 **`document`** — keep `file`/`fileName`/`fileDisposition` outputs. Update `Document/Render@1`: `engine` (handlebars/jsrender), `recipe` (chrome-pdf/html-to-xlsx), `content` (HTML template), `data` mapping.

package/skills/cxtms-workflow-builder/ref-entity.md

@@ -18,9 +18,21 @@
 - Notification tasks (Create)
 - Note tasks (Create, Update, Delete, Import, Export, RenameThread)
 - AccountingTransaction/ApplyCredit task
+- Calendar feed tasks (IssueLink, ImportFeed)
 
 All entity tasks follow the `Namespace/Operation@Version` pattern. Outputs are stored as `ActivityName.StepName.outputKey`.
 
+## Calendar feeds
+
+| Task | Description |
+|------|-------------|
+| `Calendar/IssueLink@1` | Issue a user or organization-connection iCalendar feed link |
+| `Calendar/ImportFeed@1` | Reconcile an iCalendar feed into a local mirror calendar |
+
+`Calendar/IssueLink@1` requires `organizationId` and `calendarId`; optional `label` and `organizationConnectionId` create a labeled user link or an idempotent system link. Outputs: `calendarLinkId`, `url`, `isSystem`. The URL contains the token and must be stored securely.
+
+`Calendar/ImportFeed@1` requires `organizationId` and accepts `url`, prior mirror `calendarId`, and prior `etag`. Outputs: `status`, `reason`, `calendarId`, `etag`, `businessHours`, and `availabilityBlocks`. Status is `ok`, `unchanged`, `revoked`, `error`, or `skipped`. Persist the returned calendar ID and ETag after successful calls; do not delete a previous mirror on `error`.
+
 ## PostalCodes
 
 | Task | Description |