IFAY8QPD7B - The fix for SPR NRBY82BS2N in R8.52 simply skipped processing out dated reschedule...

SPR# IFAY8QPD7B - The fix for SPR NRBY82BS2N in R8.52 simply skipped processing out dated reschedule notices for all non-repeating cases. A side effect of the optimizaiton was the "safe to discard" response did not get set for R&R destined reschedule requests. This resulted in outdated reschedule docs staying in the R&R dB and never getting processed or removed. This is most noticable when rooms have owner restrictions because owners try to act on the old requests and nothing happens (and the reservations never go away). Now any R&R outdated reschedule that is going to be skipped is flagged as "safe to discard" and it will be removed from the R&R database as if it had been processed. Note that the fix will only work for cases where the reservation is still in the database. Any requests for reservations that have been purged from the database already will not get discarded because we have no reservation to compare to in order to decide if the request is obsolete or not. The R&R system has no way to detect if the reschedule simply beat the reservation request in or if it was purged from the system.