@cxtms/cx-schema 1.9.256 → 1.9.257

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cxtms/cx-schema",
-  "version": "1.9.256",
+  "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/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' }`