cxtms 1.9.249 → 1.9.251

package/package.json

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

package/schemas/components/field-collection.json

@@ -210,6 +210,35 @@
             "isClosed": false
           }
         },
+        "onItemAdd": {
+          "$ref": "../schemas.json#/definitions/actionsList",
+          "description": "Actions fired after an item is added. Variables include parentItem, item, index, and fieldName."
+        },
+        "onItemRemove": {
+          "$ref": "../schemas.json#/definitions/actionsList",
+          "description": "Actions fired after an item is removed. Variables include parentItem, the removed item, index, and fieldName."
+        },
+        "dotsMenu": {
+          "type": "object",
+          "required": ["items"],
+          "properties": {
+            "items": {
+              "type": "array",
+              "items": {
+                "type": "object",
+                "required": ["label"],
+                "properties": {
+                  "label": { "type": ["string", "object"] },
+                  "disabled": {},
+                  "permission": { "type": "string" },
+                  "onClick": { "$ref": "../schemas.json#/definitions/actionsList" },
+                  "remove": { "type": "boolean", "default": false }
+                }
+              }
+            }
+          },
+          "description": "Custom per-item menu. Items with remove=true invoke built-in collection removal; other items dispatch onClick."
+        },
         "groupMode": {
           "type": "boolean",
           "default": false,

package/schemas/schema.graphql

@@ -11038,6 +11038,9 @@ extend type Mutation {
   createOrderMove(input: CreateOrderMoveInput!): CreateOrderMovePayload!
   updateOrderMove(input: UpdateOrderMoveInput!): UpdateOrderMovePayload!
   deleteOrderMove(input: DeleteOrderMoveInput!): DeleteOrderMovePayload!
+  createOrderMoveLeg(input: CreateOrderMoveLegInput!): CreateOrderMoveLegPayload!
+  updateOrderMoveLeg(input: UpdateOrderMoveLegInput!): UpdateOrderMoveLegPayload!
+  deleteOrderMoveLeg(input: DeleteOrderMoveLegInput!): DeleteOrderMoveLegPayload!
 }
 
 type OrderMovesCollectionSegment {
@@ -11093,7 +11096,14 @@ input CreateOrderMoveCommandValuesInput { orderId: Int!, sequence: Int, name: St
 input CreateOrderMoveLegValuesInput { name: String, orderMoveLegStatusId: Int, startDate: DateTime, endDate: DateTime, customValues: MapOfObject }
 input UpdateOrderMoveInput { organizationId: Int!, orderMoveId: Int!, values: MapOfObject! }
 input DeleteOrderMoveInput { organizationId: Int!, orderMoveId: Int! }
+input CreateOrderMoveLegInput { organizationId: Int!, values: CreateOrderMoveLegCommandValuesInput! }
+input CreateOrderMoveLegCommandValuesInput { orderMoveId: Int!, sequence: Int, name: String, orderMoveLegStatusId: Int, startDate: DateTime, endDate: DateTime, customValues: MapOfObject }
+input UpdateOrderMoveLegInput { organizationId: Int!, orderMoveLegId: Int!, values: MapOfObject! }
+input DeleteOrderMoveLegInput { organizationId: Int!, orderMoveLegId: Int! }
 type CreateOrderMovePayload { orderMove: orderMove, query: Query! }
 type UpdateOrderMovePayload { orderMove: orderMove, query: Query! }
 type DeleteOrderMovePayload { deleteResult: DeleteResult, query: Query! }
+type CreateOrderMoveLegPayload { orderMoveLeg: orderMoveLeg, query: Query! }
+type UpdateOrderMoveLegPayload { orderMoveLeg: orderMoveLeg, query: Query! }
+type DeleteOrderMoveLegPayload { deleteResult: DeleteResult, query: Query! }
 

package/schemas/workflows/flow/transition.json

@@ -17,7 +17,7 @@
       "oneOf": [
         {
           "type": "string",
-          "description": "Single source state name, or '*' for wildcard (any non-final state)."
+          "description": "Single source state name, or '*' for wildcard (any non-final state except the transition's own target state)."
         },
         {
           "type": "array",

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

@@ -186,6 +186,7 @@ are appended and omitted existing records are not deleted.
 - Order move queries: `orderMove`, `orderMoves`, `orderMoveStatus`, `orderMoveStatuses`, `orderMoveLegStatus`, and `orderMoveLegStatuses`.
 - 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.
 - A dynamic order update can supply `orderMoves` to reconcile the full collection with the same rules. New moves inherit `organizationId` and `orderId` from the aggregate; omitted or explicitly deleted moves are soft-deleted; active moves and nested legs are resequenced from 1.
 - Mutations use `input: { organizationId, values }` and return payload fields named `dispatchRouteStatus`, `dispatchRouteStopStatus`, `dispatchRouteTemplate`, `dispatchRoute`, or `generateDispatchRoutesResult`.
 - Stop status mutations: `createDispatchRouteStopStatus`, `updateDispatchRouteStopStatus`, `deleteDispatchRouteStopStatus`.

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

@@ -593,6 +593,9 @@ When `options.allowRemove` is enabled and the item count is above `minItems`, re
 | `addButton.icon` | `string` | `plus` | Add button icon |
 | `addButton.position` | `top \| bottom \| both` | `bottom` | Add button placement |
 | `defaultItem` | `any` | — | Template for new items |
+| `onItemAdd` | `action[]` | — | Fires after add with `parentItem`, new `item`, `index`, and `fieldName` |
+| `onItemRemove` | `action[]` | — | Fires after removal with `parentItem`, removed `item`, `index`, and `fieldName` |
+| `dotsMenu.items` | `{label,disabled?,permission?,onClick?,remove?}[]` | Delete only | Custom per-item menu; `remove: true` invokes built-in soft/hard removal |
 | `layout` | `list \| grid \| accordion` | `list` | Layout mode |
 | `cols` | `number` | `1` | Grid columns (non-responsive). For adaptive item layouts, set `cols: 1` and use a `layout` inside `itemTemplate` with `itemDefaults.size: { xs, md }`. |
 | `groupCols` | `number \| {xs,sm,md,lg,xl}` | `1` | Group columns when `groupMode` is true |
@@ -623,6 +626,11 @@ the header unless its position is explicit. Nested collections collapse by defau
 records expand automatically. `itemIcon`, `itemSubtitle`, and badge/count templates receive the
 parent variables plus `item`, `index`, and the item's own fields.
 
+Add/remove hooks support live persistence rather than waiting for a parent form submit. Custom
+menu actions receive the same row variables. A field's `onBlur` action receives its current value
+as `changedValues`, and placeholders inside item templates can reference `item`, `index`, and
+`parentItem`.
+
 ```yaml
 component: field-collection
 name: lineItems

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

@@ -175,7 +175,7 @@ For Order-triggered auto-transitions, `order.orderStatusName` is available in th
 ### From States
 - Single state: `from: Draft`
 - Multiple states: `from: [Draft, Submitted]`
-- Wildcard (any non-final state): `from: "*"`
+- Wildcard (any non-final state other than the transition's own target): `from: "*"`. This prevents a wildcard transition from repeatedly transitioning an entity into its current state; matching is case-insensitive.
 
 ### Execution Order
 1. Validate transition from current state