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

Idea: Public Workflows updates

David_Wieseneck

Context:

We are considering using Public Workflows + Click-to-accept for our MNDA workflow, in order to speed up velocity in the process & also minimize the redlines & maximize acceptance of our standard MNDA (minimize the instances where counterparty asks us to use their paper)

But I have a few concerns on how it would actually work:

Public Workflows seem to work great if the company does not accept redlines, but how can a counterparty recipient kick off a Public Workflow, and then request redlines?
Sometimes our counterparties ask to use their MNDA, so we review & redline & approve their paper.

I would love a Public Workflow that allows for the counterparty recipient to kick off & review our standard paper, but if that is not acceptable to them, then request redlines or submit their paper to us for review. I could imagine this would convert it into a normal Ironclad workflow.

Find more posts tagged with

Status: None

Comments

David_Wieseneck

Also - for Click-to-accept, the document is not sent via eSignature, instead the counterparty is just clicking an accept button. But sometimes the person initiating the Public Workflow & filling out all the questions is not authorized to sign on behalf of the company & needs to route the document to the right signer. Currently, there is no ability to route the "signature" to the correct signatory.

Please add the ability to route the "signature" to the correct signatory.

Jason Brown

Hi @David_Wieseneck , you can route the signature to the right signatory with Click-to-Accept. For Public Workflows you'll just need to disable "Prompt to accept after launch" (see here) and have the launch form submitter fill out the correct signer details on the launch form.

David_Wieseneck

Thanks Jason

Honestly that section is a bit hard to read & understand how that works? If we disable "Prompt to accept after launch" how does the counterparty "sign" the contract? Do they get an email? What happens if that person wants to re-assign to someone else?

Also, this is a bit confusing:

Public workflow do not allow signature blocks. For that reason, you cannot add signer role tags to the document. If you add a signature tag to your document, your workflow errors.

Does this mean that we can not use eSignature with Public Workflows?, we have to use Click-to-accept? I assumed we could use Public Workflows & Click-to-accept independently (ie Public Workflows w/ eSignature & Internal Workflows w/ Click-to-accept)

Jason Brown

Hi David,

You are correct. The signer will receive an email with a link to agree to the contract. Whether this is through Click-to-Accept or eSignature is up to you.

Thank you for the feedback! We've updated the article to help resolve some of the confusion.

As for assigning the signer a second time with Click-to-Accept, this would require reaching out to their contact to reassign the signer in Ironclad and resend the signature request.

David_Wieseneck

Thanks Jason! - can you confirm if we can use Public Workflows & Click-to-accept independently?

1. Public Workflows w/ eSignature

2. Internal Workflows w/ Click-to-accept

Jason Brown

Hey David - both are supported. Once integrated with Clickwrap you will see the following option in all workflows (Internal + Public):

Screenshot 2023-04-12 at 7.13.52 AM.png

Peter_Berkowitz

" 1. Public Workflows w/ eSignature "

@Jason_Brown are you saying that this (above) is possible? Is that a new feature? We had the same questions as David and my understanding was that this was not possible. Thank yo.

Jason Brown

@Peter_Berkowitz , correct using your eSignature provider with Public Workflows is certainly possible and documented here (step 10) .

David_Wieseneck

@Jason_Brown Any update on this feature in the original post?

Jason Brown

Hi @David_Wieseneck, Ironclad allows counterparty signer to "Decline to Sign" and optionally provide a reason for declining (e.g., proposed changes) with the Click to Accept signature method (often used with Public Workflows). Does this solve your needs here?

David_Wieseneck

No, that seems like a pretty heavy experience.

Context:

But I have a few concerns on how it would actually work:

Public Workflows seem to work great if the company does not accept redlines, but how can a counterparty recipient kick off a Public Workflow, and then request redlines?
Sometimes our counterparties ask to use their MNDA, so we review & redline & approve their paper.

Nicole_Dunn

In a related question, I am in the process of designing a Public Workflow where there are no required approvers and click to accept is the execution method but I want to be able to add e signature IF the Agreement is negotiated which means I need signature blocks and fields. I added those and wrapped them in the execution method conditions but it doesn't seem to be working. Has anyone done this before and if so, how?

Anh_Hoang

@Nicole_Dunn Did you find any solution for the above yet?

Nicole_Dunn

Not entirely, I left the public workflow as non-negotiable and created a separate standard workflow in the event the counterparty wants to negotiate.