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; } } }

Launch Workflow Under Existing Repository File

Britt_Killian

Hello everyone!

Our business uses Ironclad primarily for initial MSAs to commence services and as the relationship continues, SOWs, amendments, etc. pursuant to the MSA file. Once a file is in the repository, is there a way for a user to launch a workflow through that existing file? I would love to enable our sales folks to relate back to the MSA and then launch any underlying future documents in a way that relates back to the originating workflow. Can a workflow "come back to life" for this purpose?

I know I can link documents as parent/child once both are archived into the repository. That is good but I think this would be better?

Thanks,

Britt

Find more posts tagged with

Status: None

Comments

Lyndsey_Cain

Hi @Britt_Killian, we had a similar use case when I was at NYT. We configured the launch form so that depending on the type of new contract selected, it would prompt the user to link it to the relevant agreement -parent, child, or related record - in the launch form. It doesn't have to be done after archive. Hope that helps. Feel free to DM me if you need anything else!

Kyle_Rhodes

Echoing @Lyndsey_Cain - We do the same thing, where we require a user to link the parent and/or related record in the launch form if a certain record type is being requested. It's been a great step forward in keeping related things together and for ease of access during review.

Lugar_Choi

@Britt_Killian - if your question is whether you can continue the workflow that is connected to a file in the repo, my understanding is you cannot. Once a workflow has completed, it's done - you cannot go back and "revive" it. Any subsequent SOW / Amendment can be related / referred to the existing MSA like the other comments have commented here, but technically the workflow for the MSA and any subsequent workflows are separate (other than being able to link it as related in the repository).

Tiffany_Reed

This would be a great option, especially if it could pull existing information fields. For example, when creating an amendment to a contract, the basic info (counterparty name, address, original agreement date or whatever else) could be pulled from the original contract/workflow and inserted into the new workflow document. This could also possibly reduce input errors as well (such as typing the Counterparty name slightly different - not including "Inc" when the original contract does, selecting the wrong effective date etc) as well as save time looking up information when creating a new workflow/document for an existing relationship.

Erin_Till

Thank you for the thoughtful feedback, everyone! I am moving this post to the Idea Exchange so we can continue to track it there.

Rachael_Enderle

I think it'd be great to have the ability to start a workflow from a repository record and have that record populate in the workflow's configured related/parent record field. Since the related record search property doesn't work well for us, we often have to find the record in the repository first to copy/paste the Ironclad ID into the workflow's search property. This option would make for a more efficient process, and perhaps ensure the related record selected is the correct one.