Hello Team,
I think I figured it out. It seems there is a system property which enables this workflow and if you look at the scripting piece, it seems it is designed not to accept any past date OOTB. This workflow enables more streamlined renewal process and is best suited for organization that tightly manages their renewal process within ServiceNow and initiate these renewal workflows in timely fashion involving collaboration with stakeholder engaged in renewal process. If you only wish to maintain the contract repository to be able to know the term dates, assets attached, contarct TnCs and leverage basic contract reporting, then probably switching back to legacy contract management application makes more sense which allowed us to update the contracts post renewal date as well. One of my clients ran into this issue and although they were able to initiate the renewal workflow for their expired contracts but it didn't let them update the dates post renewal date, it either accepts current or future date so they are switching back to the legacy application which can be done by simply disabling the property (sn_contract_enable_renewal_flow) from system properties.
Thank you,
Parul Chaudhary
