nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Allow Parent/Child Relationship with Workflow in Progress

jnhamdorf

Right now, it seems like you can't link the parent/child relationship unless the parent agreement is signed. Can Ironclad consider allowing this link to happen in the "Create" stage? Since we have our MSA and SOW on separate workflows, we are often creating them at the same time, but can't link the SOW to the MSA because it's not yet signed, and have to do it after signature.

Find more posts tagged with

Status: None

Comments

Irina_G

Would love to see this enhancement! It would be so helpful to link at the create stage.

Tuffer_Harris

It is more the rule then the exception that both the parent and child will be created at the same time. This would be very important.

Sophia_Song

Hey Community, hear y'all on this thread!

Our team is doing multi-doc research into how you would like to manage these contract families in Ironclad and we'd love to talk with you this week.

You can book time here: Calendly

Kathleen_Gilbert

Yes please! It would also be helpful if you can add more than one contract at a time in the Repository. When you search for related agreements you have to repeat the search for each additional related contract.

Grace_Barrett

Hi - I am wondering if there is any update on these two topics, appreciate it has not been long since the last post but would like to know if either or both is on a roadmap as I will be considering parent/child relationship in a few weeks time. - Thanks

a) it seems like you can't link the parent/child relationship unless the parent agreement is signed.

b) It would also be helpful if you can add more than one contract at a time in the Repository. When you search for related agreements you have to repeat the search for each additional related contract.

Grace_Barrett

Hi - I am wondering if there is any update on these two topics, appreciate it has not been long since the last post but would like to know if either or both has been agreed for further development as I will be considering parent/child relationship in a few weeks time. -

a) it seems like you can't link the parent/child relationship unless the parent agreement is signed.

Thanks everyone.

Tuffer_Harris

I recommend setting up a call with @Sophia_Song at the link above if you haven't already. It was a great meeting.

Echoing that its important to be able to set it up if both parent and child doc are in flight at the same time.

And if the parent document exists already, two things are necessary to make it useful in latter child workflows (i.e. the MSA already is signed, and you're doing a new SOW or Order Form).

- First, if you start a workflow to create an SOW, the system should be intelligent enough to know which document in the repository is likely the parent agreement for that customer and that type of workflow (If its simply a drop down list of all documents in the repository for that customer, the sales team will not get it right).

-Second, the workflow for a new child agreement needs to be able to read the meta data from the parent agreement for both use in conditionals (If <parent-Country>=US Then insert US data clause in SOW) and as data that can be inserted (insert <parent-EffectiveDate> in SOW intro)

Kshitij_Dua

Agree with everyone's suggestions.

Jon_Klaff

This is critical to us - currently we have to put Order Forms on the MSA workflow if they will be signed together, which causes maintenance headaches and mass confusion amongst our sales and contracting staff.

Shannon_Pedroni

Would love to see an update on this @Sophia_Song. This has come up as a request for our organization as well. Thanks!

Chelsea_Spickelmier

I would love to see this as well. Further, I would LOVE to be able to use the Launch Form data in the parent when creating a child document. AKA information such as names, addresses, closing dates, purchase price, and other key terms only manually entered once on the parent workflow Launch Form and then be able to use that data in a child workflow. I use workflows for RE and Finance deals and these include an initial parent contract and several related contracts all being signed at closing, negotiated separately, and need to be saved as individual records in the repository.

Being able to link the launch form data would be huge in reducing human error and would save a huge amount of time when working on one parent transaction that is made up of several workflows.

Elizabeth_Graf

Do we have a status update on this feature. We've just ran into this as we have a parent record workflow that needs to have 2 additional documents create at the same time. Multiple workflows this would be useful for!

Sharon_Donnigan

Hi @Sophia_Song,

Bubbling this one back up to see if there are plans on the roadmap to allow linkage between two in-flight workflows that are related.

Thanks!

Chelsea_Spickelmier

@Sophia_Song I would also like an update on this. I have a company initiative to create workflows for our acquisition transactions and need to be able to link open workflows and share intake data to make this feasible.

Grace_Barrett

I support this request to create an in-flight relationship link, which has been requested since 2001 in one form or another. Can Ironclad please say if it is on the roadmap or not. Thanks.

Grace_Barrett

Sorry, I meant 2021!

sandra_hernandez

Hello adding a comment of support here for this feature. Our team is in the same boat - we need to be able to link in-flight workflows.

Zarah_Eapen

Hello! Any updates on this one? I believe a lot of us find this challenging. Not being able to link an in-progress contract a parent or a child for that matter. Quite often these are negotiated in parallel. Would be great if this feature can be enabled.