A Custom Event/Streams notice is meant to fire when a Historical Work Order gets reopened, but the Status field expected on the Historical Work Order's table doesn't actually appear on that LU, or on the related ActiveSeparate LU, at all — there's no STATUS or ROWKEY-style field to watch there for this purpose.

All FAQ questions / Asset and maintenance management

Answer

A Historical Work Order doesn't retain a usable Status field to watch for a 'reopened' transition, because reopening a Work Order actually removes its record from the Historical table entirely, rather than just changing a status value on it — trigger the Custom Event on the HistoricalSeparate Logical Unit's 'Object(s) Removed' condition instead, since that removal is exactly what happens at the moment a Work Order gets reopened. If that specific trigger doesn't fit your scenario, a more general fallback is to instead watch the broader WorkOrder Logical Unit directly for changes to its WO_STATUS_ID field.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Asset and maintenance management questions