The DocuSign REST API has some descriptions that include the width for string fields. But many string fields don't have a width in the description. I have found references here and their site to some of those being 100 characters. Is there a Docusign default max length for these string fields that don't have widths defined?
The reason for this is that some data is going to be extracted, and stored in a database table for analysis.
I've gone over the Swagger, the DocuSign REST API documentation pages, and a bunch of the Stackoverflow pages.
100 is probably a good default maximum length if you don't have any documentation saying otherwise for this specific field.
If you have a need to confirm a specific field maximum length - I can inquire about this for you. I do know this limit (100) as the right maximum for several specific fields.
Related
According to Docusign
Data Population Scope is a great way to speed up the signing process by duplicating their data throughout the document automatically
I want to prevent this replication from happening programmatically.
Is there an argument I can pass to Text that would prevent this? Maybe something like:
Text(data_label="some_unique_label")
I tried doing
Text(name="some_unique_name")
This did not prevent data linking between other Text fields. According to the Docusign documentation I need to set a unique data label for each Field. However, I am not finding a data_label option for Text.
You're looking for the tabLabel parameter.
Data is populated between fields that have the same tabLabel, so if you make those unique, they won't share data.
I'm currently trying to utilize the Templates list API with the search_text query string parameter. When I send a value that exceeds 48 characters, it will not return anything. Does anyone know if there is an assumed/imposed length restriction for using search_text?
Example GET Urls:
Works: /Templates?search_text=Universal Power Purchase Agreement - Massachuset
Does not work: /Templates?search_text=Universal Power Purchase Agreement - Massachusett
You've crossed the maximum length of the search_text parameter. Trying to use a search term that's more than 48 characters will result in the search failing and zero results being returned.
Specifically, we get these errors: "Validation error: The 'http://www.docusign.net/API/3.0:UserName' element is invalid ... The actual length is greater than the MaxLength value." But I have not been able to find any documentation about what the maximum length of this field is. I'd like to warn users of this value so they don't have to do trial and error to get it to work. Specs on all the field limitations would be useful. Or if the error message message said something along the line of "...is greater than the MaxLength value of 50."
The XSD provides this type of information, but I'm not sure whether or not DocuSign makes the XSD available for public consumption. I'll leave it to #Ergin (DocuSign) to comment on that, and to provide the link to the XSD if appropriate. Regarding specifically the UserName field, Max Length seems to be 100.
The API Documentation has info on field limits. You go the DocuSign API Documentation page, open either the Online SOAP API guide or the SOAP PDF guide, and do a search for CreateAndSendEnvelope. See page 40 of the PDF guide for instance.
The guide lists the schema of the call, and if you read the descriptions they state the maximum limits. For instance, it states the email subject is maximum 100 characters, email blurb is maximum 2000 characters, etc.
For envelope recipients you'll see a link that leads you to the Recipients schema (see page 53 of the PDF). On there, you can see that UserName is maximum 100 characters.
Background: We use the DocuSign SOAP API method CreateEnvelopeFromTemplatesAndForms for a very clear reason (mainly, we don't want to keep track of page numbers and X/Y coordinates) and we do not want to stop using this api method (unless there is another method that doesn't force us to keep track of page numbers and X/Y coordinates). I mention this before someone happily suggests I use another method.
Problem: We've recently been asked to send large envelopes through the DocuSign api (could exceed 100 mb). I know that DocuSign doesn't place a limit on envelope size, but rather on size of payload per api call when the envelope is created. I think what we need to do is the following, but I am having trouble:
Step 1: load up to 50 mb in the templates
Step 2: call CreateEnvelopeFromTemplatesAndForms but set the ActivateEnvelope parameter to False
Step 3: load up to another 50 mb in the a new set of templates
Step 4: call CreateEnvelopeFromTemplatesAndForms again but this time set the ActivateEnvelope parameter to True.
Is what I'm trying to do possible? I keep getting an error that says the "TransactionID has already been used." If what I'm trying to do (in general) is possible, any code samples would be much appreciated.
I believe Anchor Tags is a viable and easy to use feature that should solve your issue here. With anchor tags you can still use the CreateEnvelopeFromTemplateAndForms() API call but you won't have to specify page numbers or (x,y) coordinates for your DocuSign Stick-eTabs. Instead, those tabs will get "anchored" to your documents based on content that it finds in the document itself.
For instance, let's say you have a document that needs to be signed and in the document where the signature should go you have the text "Sign Here". You can have the system place a signature tab close to this "Sign Here" text. You could have it place it X amount of pixels to the right, or Y inches or cms to the right, etc.
You can add these tabs at the account level, which means they will get applied whenever their corresponding text is found in ANY envelope you create in your account, OR you could add them in your API request so that they are only used on that particular envelope.
For more info please see the following links:
Previous Stack Overflow Question
Explanation on Dev Center - look at Tab Positioning section
I have a view that pulls in feed items (from various "Owner feeds" to use the feeds module lingo), then sorts them by date (very important). The owner feed has a CCK field for the type of feed (Twitter, Blog, etc.) and a CCK field theoretically to limit the number of feed items displayed in the view. (The reason for the limit is that Twitter dominates, but we want some blogs, etc., so I don't want to have to show 100 tweets before displaying my first blog.)
I'm guessing some sort of Views hook code is in order, but I'm not sure which one. Perhaps the hook that allows direct modification of the query...
Note that the Owner feed nid is being pulled into the view via a Relationship.
Thanks in advance!
Using the Arguments field in the view, you could first select the node type, then node post date.
In this way you could give priority to the blog type, before sorting by date.
You could also consider building two Views, for instance the top 5 blog items and the top 20 Twitter feeds...