Prior to Lifecycle Properties being introduced, we created our own Auto-Renew Date field. Our Auto-Renew Date field has not been automatically updating once the date passes in the repository.
After working with Ironclad Support, it's our understanding that since our Auto-Renew Date field is a custom property, it will not be automatically updated by the lifecycle engine.
The recommendation was to use the system Expiration Date as the contract end date.
Question: If you have experienced this, how did you merge your custom Auto-Renew Date field into the Expiration Date field that automatically updates through Lifecycle Properties? Pros/Cons? How did this affect your repository data?