Contract Renewal Validation and Preventing Contracts from Permanently Being Locked for Renewal
The Contract renewal script (R05) performs validation to determine if a contract is renewable.
R05 resets the value of the Queued for Renewal hidden field to 'False' for contracts that failed validation due to the following reasons:
-
no contract date,
-
no renewable items, or
-
the original contract set to Inactive.
This prevents contracts that failed validation from having the value of Queued for Renewal permanently set to ‘True’, which causes an issue.
With Queued for Renewal = True, contracts that failed validation due to the said reasons, will always be locked for renewal. They will not be processed in succeeding renewal runs, indicating the error "Contract [xxx] is already locked for renewal. Skipping this contract".
Previously, before April 2024, R05 did not reset the Queued for Renewal hidden field to 'False'. Therefore to prevent the issue with contracts permanently being locked for renewal, you should perform a mass update of your contracts being renewed by the R05 script, to set the value of Queued for Renewal to 'False'.
On the other hand, for contracts that only have perpetual items and are expired, which will eventually fail renewal validation and trigger the issue, the R05 script does the opposite by setting the initial value of the Renewals Exclusion field of these contracts to 'True'. This means these contracts will not be processed by the R05 script anymore in the next batch of renewals, therefore also preventing these contracts from being permanently locked for renewal.