I am in the process of building our main agreement contract workflow and I've come upon multiple ways to handle amendments to a published contract. I was curious to see how other companies have successfully dealt with this.
1. We could use the amend button with a amandment process in tasks conditional on appearing for full/terminated/renewal. This processs would need to repeat itself for every amendment 'fire'. This can only be done if a document is associated to the process. This isn't the case...therefore the tasks will not start again for every new amendment.
2. Use follow-on projects but this creates a distinct project and attributes will need to be completed in two places.
3. Use sub-agreements but that would require us changing the original agreement to a master.
How have others created a workable amendment process for multiple users?
Thanks.
Danielle