Multiple recipient types and assigning clientUserId to recipients #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…Id to allow for proper embedded url fetching.
…red by the API anyway.
shijun
added a commit
that referenced
this pull request
Mar 28, 2014
…ient-id Multiple recipient types and assigning clientUserId to recipients
shijun
pushed a commit
that referenced
this pull request
Apr 12, 2014
…ient-id Feature/recipient types and client
plzandtanku
added a commit
to plzandtanku/hacky-docusign-php-client
that referenced
this pull request
Jul 30, 2019
typos are the docusign#1 cause of bugs imo
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The following is a work in progress, but I thought I would get the conversation started. I have added support for multiple client types when creating an envelope from a document. I imagine something similar will need to be done for creating an envelope from a template.
I have also added clientUserId to the recipient model to allow us to properly retrieve an embedded url when we create an envelope using clientUserId on the recipient.