Relationship between In-Process Workflows and Ability to Send All Documents for Signature Together

Ronnie_Obriant

We have a use case where separate Workflows are preferred, even though the agreements are related. For example, a base master agreement and related addenda—each with its own Workflow due to differing terms or expiration dates. While it's technically possible to combine them in a single Workflow, it’s not ideal. Users would like the flexibility to manage each document individually but still send the full set (base + addenda) together in one final eSignature package. To support this, the Workflow Owner should be able to issue all related agreements together at signature.

I've reviewed other ideas, and see similar requests but not specifically the same. Related: 

https://community.ironcladapp.com/t5/Ironclad-Idea-Exchange/Can-we-relate-an-in-progress-workflow-to-another-in-progress/idi-p/8606

Ashley_Armstrong

This is not ideal, but we allow one workflow for multiple contract documents (MSA, SOWs, DPA, etc.) and then manually split apart the contracts post-archive and create separate Repository records to manage varying term.  This streamlines submission for the business and allows for one signature pack but gives us more flexibility on the backside.