This enhancement extends the automatic contract expiration logic to support contract and subcontract records without an Option Years End Date.
Previously, contract/subcontract records were automatically marked as Ended/Expired only when an Option Year End Date was populated. If this field was left blank, the record status remained unchanged, even if the Base Period End Date had passed.
With this enhancement, the workflow now uses the Base Period End Date as a fallback when the Option Year End Date is not available. For Contract and Subcontract records in the Administer stage, the workflow automatically updates the record status to Ended/Expired one day after the Base Period End Date. If an Option Year End Date is populated, it continues to take precedence over the Base Period End Date.
Example 1 - Option Years End Date not Available
When a contract is in the Administer stage and the Option Years End Date is not populated, the system uses the Base Period End Date to determine when the contract should be closed. For example, if the Base Period End Date is June 29, 2026, and the Option Years End Date is blank, the flow automatically schedules a status update. One day after the Base Period End Date, on June 30, 2026, the contract status is automatically updated to Ended/Expired.
Example 2 - Option Years End Date Available
When a contract is in the Administer stage and both the Base Period End Date and Option Years End Date are populated, the system prioritizes the Option Years End Date, regardless of which date occurs first. For example, if the Base Period End Date is June 29, 2026 and the Option Years End Date is June 30, 2026, the flow ignores the Base Period End Date and schedules the status update based on the Option Years End Date. As a result, the contract status is automatically updated to Ended/Expired on July 1, 2026, which is one day after the Option Years End Date.
