@d19n/youfibre-odin-sdk 2.0.117 → 2.0.118
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -404,38 +404,26 @@ exports.KCI_EFFECT_ROWS = [
|
|
|
404
404
|
reasonCode: 'AMENDED',
|
|
405
405
|
serviceOrderKind: 'PROVIDE',
|
|
406
406
|
yfEffect: {
|
|
407
|
-
kind: '
|
|
408
|
-
scheduleAppointment: {
|
|
409
|
-
dateFrom: 'provideServiceOrder.appointmentTimeslot.timeslotStartDateTime',
|
|
410
|
-
timeBlockFrom: 'provideServiceOrder.appointmentTimeslot.classification',
|
|
411
|
-
supplierReferenceFrom: 'provideServiceOrder.appointmentReservationReference',
|
|
412
|
-
},
|
|
413
|
-
// Co-effect: AMENDED's dto carries the updated
|
|
414
|
-
// `provideServiceOrder.committedDate` reflecting the new appointment.
|
|
415
|
-
// Update Order.CommittedDate atomically with the WO transition so the
|
|
416
|
-
// YF Order tracks the supplier-committed date for the rebooked slot
|
|
417
|
-
// (same reason as REAPPOINTED — keeps downstream cron / dashboard
|
|
418
|
-
// decisions aligned with the supplier's current commitment).
|
|
407
|
+
kind: 'PROPERTY_WRITE',
|
|
419
408
|
propertyWrite: {
|
|
420
409
|
entityKey: 'OrderModule:Order',
|
|
421
410
|
properties: ['CommittedDate'],
|
|
422
411
|
},
|
|
423
|
-
notes: 'Supplier
|
|
424
|
-
'
|
|
425
|
-
'
|
|
426
|
-
'
|
|
427
|
-
'
|
|
428
|
-
'
|
|
429
|
-
'
|
|
430
|
-
'
|
|
431
|
-
'
|
|
432
|
-
'
|
|
433
|
-
'
|
|
434
|
-
'
|
|
435
|
-
'
|
|
436
|
-
'
|
|
437
|
-
'
|
|
438
|
-
'AMENDED = amendment-accept confirmation (tenant or auto-amend path).',
|
|
412
|
+
notes: 'Supplier confirmation that an amendment has been accepted with a new ' +
|
|
413
|
+
'appointment. In production this KCI always arrives AFTER the tenant ' +
|
|
414
|
+
'has driven the amendment — customer triggers YF /schedule-appointment ' +
|
|
415
|
+
'→ YF moves its WO Pending→Scheduled locally + calls NET amendOrder ' +
|
|
416
|
+
'→ NET responds with AMENDED. By the time AMENDED arrives at YF, the ' +
|
|
417
|
+
'WO is already at Scheduled with the new appointment data populated, ' +
|
|
418
|
+
'so the KCI carries no new state-change responsibility for the WO. ' +
|
|
419
|
+
'Only effect: update Order.CommittedDate from ' +
|
|
420
|
+
'provideServiceOrder.committedDate so the parent order tracks the ' +
|
|
421
|
+
'supplier-committed date for the rebooked slot (the initial COMMITTED ' +
|
|
422
|
+
'KCI set this on first commit; AMENDED overwrites with the post-amend ' +
|
|
423
|
+
'commitment). Earlier in this session a WO_SCHEDULE_APPOINTMENT bridge ' +
|
|
424
|
+
'was tried here but is wrong for production — it would cause a ' +
|
|
425
|
+
'double-amend cycle (YF amends NET → NET emits AMENDED → YF amends ' +
|
|
426
|
+
'NET again).',
|
|
439
427
|
},
|
|
440
428
|
logAgainstOrder: true,
|
|
441
429
|
specRef: 'fibrecafe-docs/pages/orderstate.md (AMENDED) + Frank 2026-05-12 spec quote',
|