cxtms 1.9.40 → 1.9.42

package/package.json

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

package/skills/cxtms-developer/SKILL.md

@@ -49,6 +49,10 @@ Use `--feature <feature_name>` with `cx-cli create` to automatically place files
 !cat skills/cxtms-developer/ref-entity-shared.md
 !cat skills/cxtms-developer/ref-entity-geography.md
 
+### Equipment & Fleet
+
+!cat skills/cxtms-developer/ref-entity-equipment.md
+
 ### Warehouse & Inventory
 
 !cat skills/cxtms-developer/ref-entity-warehouse.md
@@ -65,6 +69,7 @@ Use `--feature <feature_name>` with `cx-cli create` to automatically place files
 | **Pricing** | Rate, Lane, Discount, AccountingItem, AccountingAccount, PaymentTerm | ref-entity-rate.md |
 | **Shared** | Tag, Attachment, Division, EquipmentType, PackageType, Note/NoteThread | ref-entity-shared.md |
 | **Geography** | Country, State, City, Port, Vessel, CustomCode, ModeOfTransportation | ref-entity-geography.md |
+| **Equipment** | Equipment, EquipmentStatus | ref-entity-equipment.md |
 | **Warehouse** | InventoryItem, WarehouseLocation, CargoMovement (Order variant) | ref-entity-warehouse.md |
 | **Notification** | Notification, UserNotification | ref-entity-notification.md |
 
@@ -87,7 +92,9 @@ Most entities have `customValues` — a `Dictionary<string, object?>` stored as
 
 **Lookup entities**: Job, JobStatus, Tag, Attachment, EventDefinition, Rate, Lane, Discount, AccountingItem, Port, Country, State, City, ModeOfTransportation
 
-**Without customValues**: Division, EquipmentType, PackageType, Vessel, CustomCode, AccountingAccount, PaymentTerm, WarehouseLocation, JobOrder
+**Fleet**: Equipment (replace semantics — null clears, non-null full-replaces)
+
+**Without customValues**: Division, EquipmentType, EquipmentStatus, PackageType, Vessel, CustomCode, AccountingAccount, PaymentTerm, WarehouseLocation, JobOrder
 
 ### Audit Fields (AuditableEntity)
 

package/skills/cxtms-developer/ref-entity-equipment.md

@@ -0,0 +1,64 @@
+# Equipment Entity Reference
+
+## Contents
+- Equipment
+- EquipmentStatus
+
+---
+
+## Equipment
+
+Physical equipment/fleet units (trucks, trailers, etc.).
+
+| Field | Type | Notes |
+|-------|------|-------|
+| `equipmentId` | `int` | PK |
+| `organizationId` | `int` | |
+| `unitNumber` | `string` | Max 50 chars |
+| `equipmentTypeId` | `int` | FK to EquipmentType |
+| `equipmentStatusId` | `int` | FK to EquipmentStatus |
+| `notes` | `string?` | Max 700 chars |
+| `customValues` | `Dictionary?` | jsonb — replace semantics (null clears, otherwise full-replace) |
+| `isDeleted` | `bool` | Soft delete |
+
+**Navigation:** `organization`, `equipmentType`, `equipmentStatus`
+
+**Audit fields:** `created`, `createdBy`, `lastModified`, `lastModifiedBy`, `createdUser`, `updatedUser`
+
+### customValues Behavior
+
+Equipment uses **replace semantics** (not merge). Sending `null` clears the dictionary entirely; sending a non-null dictionary replaces it completely. This differs from most other entities that use merge semantics.
+
+### GraphQL
+
+- `equipmentId`, `unitNumber`, `equipmentTypeId`, `equipmentStatusId`, `notes`, `customValues`, `isDeleted`
+- `equipmentType` — expanded `EquipmentType` object
+- `equipmentStatus` — expanded `EquipmentStatus` object
+
+---
+
+## EquipmentStatus
+
+Configurable statuses for equipment units.
+
+| Field | Type | Notes |
+|-------|------|-------|
+| `equipmentStatusId` | `int` | PK |
+| `organizationId` | `int` | |
+| `statusName` | `string` | Max 50 chars |
+| `statusDescription` | `string?` | Max 255 chars |
+| `statusStage` | `EquipmentStatusStage` enum | Lifecycle stage |
+| `priority` | `int` | Sort order |
+| `color` | `string?` | Hex color code, max 32 chars |
+
+**Audit fields:** `created`, `createdBy`, `lastModified`, `lastModifiedBy`, `createdUser`, `updatedUser`
+
+No customValues.
+
+### EquipmentStatusStage Enum
+
+`EquipmentStatusStage` — represents the lifecycle stage of an equipment status. Values defined in `TMS.Domain.Enums`.
+
+### GraphQL
+
+- `equipmentStatusId`, `statusName`, `statusDescription`, `statusStage`, `priority`, `color`

package/skills/cxtms-workflow-builder/ref-expressions-ncalc.md

@@ -101,7 +101,8 @@ Functions use two iterator variable names:
 | `now('yyyy-MM-dd', 'en-US')` | Formatted current time as string |
 | `addDays([date], 30)` | Add days (decimal, can be negative). Accepts DateTime, DateTimeOffset, string |
 | `addHours([date], 2)` | Add hours (decimal, can be negative). Same type handling |
-| `formatDate([date], 'dd/MM/yyyy', 'en-US')` | Format date with culture. Accepts DateTime or string |
+| `formatDate([date], 'dd/MM/yyyy')` | Format date using InvariantCulture (culture optional). Returns `null` for null or unparseable input. Accepts `DateTime`, `DateTimeOffset`, or string (including `DateTimeOffset`-shaped strings from `toLocalTime`) |
+| `formatDate([date], 'dd/MM/yyyy', 'en-US')` | Format date with explicit culture |
 | `dateFromUnix([unixTime])` | Unix timestamp (seconds) -> `DateTimeOffset`. Accepts int, long, decimal, string |
 | `dateToUtc([date])` or `dateToUtc([date], 'en-US')` | Convert to UTC. Optional culture for string parsing |
 | `toLocalTime([date], 'America/Chicago')` | Convert UTC datetime to local time in IANA timezone. Returns `null` if date or timezone is invalid |