Hello ​@SRY 
 

Could you please share how you've configured the workflow so far? Specifically:

• Which steps are you using to combine the documents or maybe workflow config?

• How are you triggering (or "kicking off") the workflow?

This will help me better understand your setup and suggest the most effective solution.

Thanks!

DocuSign Community Leaderboard Top 5 contributor
Ranked #3 in the Reply Royalty category in DocuSign Community Wrapped 2024
Let’s LinkedIn and roll: Pawan Gangwani - EY | LinkedIn

Hi ​@SRY,

Here is my recommended solution:

• The user will upload the first document via document generation form which will initiate the workflow
• The second document will always be stored on your account in whatever folder makes sense

The build the workflow: 

• Create a new Advanced workflow where the workflow kickoff = Document Generation (choose your Doc Gen Config)
• The first document that was uploaded from doc gen will be represented as the Params variable 
• Add a copy or move document step which will copy the second static document in your CLM Account. Store this as a variable (ex: CopyDocument)
• Use an update variable step to pipe delineate the two document IDs (ex: <%#XmlVariables.Params.Id%>|<%#XmlVariables.CopyDocument.Id%>) into a new variable (ex: CombinedDocuments).
  • Because the documents are dynamic and change every time the workflow runs, you have to store their Ids as pipe delineated list first. You cannot just select the documents to combine. 
• Use a combine document step. In the Document property, reference CombinedDocuments. And set the folder and other properties as you would like.

Here is the piped list from my example to give you an idea of what that would look like:

<%#XmlVariables.CopyDocument.Id%>|<%#XmlVariables.Params.Id%>

We go over the basics of building a workflow in our 3 day Docusign CLM Build Workflows course in case you would like some more foundational knowledge.

Hope this helps!
Kelly

Hi ​@Kelly.Gatling !! 

Thank you for your reply. I am having trouble and I am getting errors with my flow and I think it might be with my variable set up. 

It is still showing as two separate documents.

Hi - Looks like you are on the right track! Offhand, I cannot see what the issue might be. Can you please copy and paste the error message you are getting and the value you have for the combined documents variable? The two separate documents will show in addition to the combined document unless you select the property “Delete the original documents after combining them.” I see you have the combined document output set to Word (.docx). In order for this to work both original documents need to be .docx file types. 

​@Kelly.Gatling 

Here is where it failed and the error message: 

This is the Property step set up variable value: 

<%#Variable.CopyDocument%>|<%#Variable.Params%>

Oh ok! I think it might be that value. Make sure you are referencing the Id node of the variables.

Update your Variable Value 1 step value with this:

<%#XmlVariables.CopyDocument.Id%>|<%#XmlVariables.Params.Id%>

​@Kelly.Gatling 

I did and it’s the same error at the same step. 

This is the output in the expression builder: 

Compilation failed: (1:8) Invalid expression term '<', (1:9) Invalid expression term '%', (1:10) Preprocessor directives must appear as the first non-whitespace character on a line, (1:10) Invalid expression term '}', (1:10) ; expected - Reference Id: 68ea8c0b-c71f-440a-8186-ffafefcae0ed  Source: using System;using System.Xml;using System.Text;using System.Text.Json;using System.Text.Json.Nodes;using ADEXS.ExpressionCompilationService.Templates.Model;namespace ADEXS.ExpressionCompilationService.Templates{	public class UserMetaExpression	{		public object MetaFunction(WorkflowContext _context)		{return <%#XmlVariables.CopyDocument.Id%>|<%#XmlVariables.Params.Id%>;		}			}}

You won’t need the expression builder for this. I’m not sure where you are using it because it doesn’t look like in your screenshots you are using it but you don’t need it. That could be part of the problem. Unfortunately you might have to reach out to Docusign Support on this one as we are limited in our ability to help through the community but you are definitely on the right track according to your screenshots! 

​@SRY , Can you add this to the expression builder

GetVariableValue("Params.Id")+"|"+GetVariableValue("CopyDocument.Id");

This essentially is doing the same thing as mentioned but Kelly but just want to see if the you are able to pass the error and get the Ids concatenated.