So a content control in MS Word is like the merge tokens that used to be used in MS Word. A Content Control can have more information than just an open and close tag. We use these controls to merge data from a database into the Word document itself. When the merge happens the data is actually placed inside the open and close tags of the content control. This is how MS Word works. You do NOT replace the entire content control with the data. So this was working perfectly for a good year. We would send the merged document with data to DocuSign via the Java eSign API and the document would go out for signature, and in all cases the content control itself would not be visible in the resulting signed document. You would only see the data inside. So Text in between that is data from the database would only show "Text in between that is data from the database" in the signed document. But recently that changed. We have done no code changes on our end, it is the same as it was for the past year, so we are trying to figure out what is causing these "tags" to now show up. Since we don't show or hide content controls in our code, only thing that could have changed is within MS Word or DocuSign API/DocuSign itself.
Are you aware of any change to how docx files are handled on the DocuSign end. I believe before that when you got the signed document it would have been converted to PDF by DocuSign. Maybe that has changed? Any ideas would be grateful as I do't have other ideas of where to look. Thanks.
So a content control in MS Word is like the merge tokens that used to be used in MS Word. A Content Control can have more information than just an open and close tag. We use these controls to merge data from a database into the Word document itself. When the merge happens the data is actually placed inside the open and close tags of the content control. This is how MS Word works. You do NOT replace the entire content control with the data. So this was working perfectly for a good year. We would send the merged document with data to DocuSign via the Java eSign API and the document would go out for signature, and in all cases the content control itself would not be visible in the resulting signed document. You would only see the data inside. SoText in between that is data from the database would only show "Text in between that is data from the database" in the signed document. But recently that changed. We have done no code changes on our end, it is the same as it was for the past year, so we are trying to figure out what is causing these "tags" to now show up. Since we don't show or hide content controls in our code, only thing that could have changed is within MS Word or DocuSign API/DocuSign itself.
Are you aware of any change to how docx files are handled on the DocuSign end. I believe before that when you got the signed document it would have been converted to PDF by DocuSign. Maybe that has changed? Any ideas would be grateful as I do't have other ideas of where to look. Thanks.