@cxtms/cx-schema 1.9.249 → 1.9.250

package/package.json

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

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/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`.