Scrive eSign requires an additional license. Please contact support@documill.com for more information.
Sends the specified document through Scrive for recipients to sign.
Creating meta attribute
The meta attribute defines the Document JSON data structure used by Scrive. The Document JSON is used to create documents, define the signing parties and to set other meta data for the signing process.
Attributes
|
var |
|
|
|---|---|---|
|
Required |
Value type |
EL-evaluated |
|
Yes |
String |
No |
|
Defines the name of the variable holding the metadata for the created Scrive document. |
||
|
value |
|
|
|---|---|---|
|
Required |
Value type |
EL-evaluated |
|
Yes |
File |
Yes |
|
Defines the document that is sent for signing. |
||
|
auth |
|
|
|---|---|---|
|
Required |
Value type |
EL-evaluated |
|
Yes |
String |
Yes |
|
Defines the credentials for Scrive API authentication. |
||
|
meta |
|
|
|---|---|---|
|
Required |
Value type |
EL-evaluated |
|
Yes |
String |
Yes |
|
Defines the Scrive document structure. The value is expected to be a JSON-like structure which sets the signing parties and other data for the signing process. |
||
|
dynDocId |
|
|
|---|---|---|
|
Required |
Value type |
EL-evaluated |
|
Yes |
String |
Yes |
|
Defines the id of the created Dynamo Document. |
||
|
endpoint |
|
|
|---|---|---|
|
Required |
Value type |
EL-evaluated |
|
No |
String |
Yes |
|
Defines the Scrive API endpoint. If left empty, test API is used by default. |
||
Examples
The sendToScrive command can send the composed document to be signed by one or more signers. Define the signers by using the meta attribute. For an example on how to use in a template see here.
<set var="auth" value="oauth_signature_method="PLAINTEXT"", oauth_consumer_key="123", oauth_token="456", oauth_signature="abc&cde" />
<sendToScrive var="statusMap" value="${documentPDF}" auth="${auth}" meta="${documentMap}" dynDocId="${dynDocId}" />