Skip to main content

Greetings, my situation runs as follows:

I have a CLM workflow, in which I'm using the "Send for Signature" step. I have 2 possible paths on this part of the workflow that are chosen by the user; one is sending 4 signatures, and the other is sending only 3 signatures, excluding one. The document remains the same because the order must be in this way.


In the document, I have my tags, as it shows here:

/signer2/ is the optional one. Now the thing is that I don't know how I can control this in DOCUSIGN. When the envelope for signing is sent, it always takes the /signer2/ tag as the second sign, even if it doesn't exist in CLM, and leaves /signer4/ untouched. So the order in this scenario should be /signer1/ → /signer3/ → /signer4/.

So my question is, if there exists a way of handling this? On my CLM workflow, I tried changing the recipients order, but the tags keep going 1-2-3-4, I can't skip the 2 when it's not needed. 

 

Hello Fabian Yeudiel


How do you make the signer dynamic? I mean, when is it showing up and when is it not showing up and how do you declare it? do you mean you have 2 paths already in the workflow that are going into different send for signature step, one has the signer2 and one that does not?


Hello Fabian Yeudiel


How do you make the signer dynamic? I mean, when is it showing up and when is it not showing up and how do you declare it? do you mean you have 2 paths already in the workflow that are going into different send for signature step, one has the signer2 and one that does not?

Hi Alexis.

Yes i have already defined 2 paths in the workflow for this, 2 send for signature steps with the correspondant recipients for each case, the thing is that i only have 1 document as template, so the signer tags must become dynamic, how i gave solution to this was using XML MERGE step creating the tags in real time and his numbers dynamically in the document.

But i find this a nuisanse, you have to create the XML for each signer case, to modify the template matching the number of the tags with the number of signers, you have to duplicate the tags, because you need one for the document generation and then the signer tags, so i ended with 2 XML MERGE, one for generating the usual information that the document should contain and then another one for the sign tags. I didnt find any form of handling this in another way.

There is no problem until the point that i have to make the signers dynamic and keep an specifict order for the recipients, and i ended controlling this with C# code and XML, that makes the building proccess more slow and harder because you add a layer of complexity for handling signers. 

So my question still is if Docusign CLM can handle this by himself in an easier way?


Reply