Incorrect Work order expiration notification

[Sruthi]

Hi,

Contingent work order expiration notifications are triggered by system even after Work Order have been extended.

The notification is picking old End date .

eg: WO starts from 1/June/2021 to 1/June/2022. First notification is triggered 30 days in advance stating WO about to expire. On receiving this notification, WO is being extended to 31/Dec/2023. System is still triggering notification on 1/June/2022 stating WO expired.

Please assist.

Off cycle batch event configuration:

Parameter: GO WorkOrder

In Then condition , execute Trigger Work Order Expiry Event() function on GO WorkOrder.

This used is called on OFF CYCLE EVENT BATCH, under Associated Rule.

In Off CYCLE EVENT Batch , filter criteria is End Date equals -30 , -1 , 0.

Hence, on receiving first notification issued 30 days in advance, manager extends the Work Order Expiry , unfortunately this notifications are also issued again at -1 and 0 days of old end date.

[MaheshWashikar]

Please check your business rule. It should be with scenario Trigger Alerts for MDF. Once you select that you can use a statement called as "Delete Pending Old Alert Flag" = Yes