With batch processing, JuicedSign creates and sends an agreement without anyone selecting Send to JuicedSign. A Quickbase email notification starts it, for example when a record is added or a checkbox is checked.
What the wizard adds
JuicedSign Batch Arguments: a formula field with the same settings as the Send to JuicedSign button, written for batch. It's empty until the record has a document to send.
JuicedSign Batch Email: the address to send the notification to.
JuicedSign Error Details: shows why a batch agreement couldn't be created.
A batch configuration in the Batch Config Portal, with its key already in the arguments as
configid=. See Batch configuration.
If you used Prefix for Labels in the wizard, the field names start with that prefix. Don't change the values the wizard set in the arguments.
Set up the email notification
The wizard doesn't create the notification. Create it on the table you send from:
Decide what should send the agreement, for example a checkbox Send with JuicedSign Batch. Add the field if you need one.
Create an email notification on the table:
Send to: the address in JuicedSign Batch Email.
Notify when: your condition, for example when the checkbox changes to checked.
Message: a custom message whose body is only the JuicedSign Batch Arguments field.
Save the notification, and test it on one record.
The record needs everything a normal send needs: the document, recipients, tags, and sender. See Send an agreement.
What happens
JuicedSign creates the agreement, adds the JuicedSign Management and Recipients records, and emails the first recipient, just like a normal send. See Manage agreements.
Created with console application is checked on the JuicedSign Management record.
If it worked, JuicedSign Error Details is cleared. If not, it shows the reason.
Differences from Send to JuicedSign
No in-person signer: every recipient gets an email.
Recipients can always both draw a signature and pick a style;
drawandfontaren't used in batch.QB User Email on the JuicedSign Management record stays empty, because no one selected the button.
The arguments are separated by spaces, not
&. Values that can contain spaces, like the file name and document type, are wrapped in quotes. Keep that if you change the formula.
Batch configuration
Every batch run is checked against its batch configuration. The configuration lists the values each locked parameter is allowed to have, like your client ID, app,
docfids, andsigneddocinfo. If a value doesn't match, the run stops, and JuicedSign Error Details shows which parameters didn't match.If you change one of those values, for example to save the signed document to another field, update the configuration's allowed values first.
See Batch Config Portal overview and Use a configuration in batch runs.
If no agreement is created
Check JuicedSign Error Details on the record. The messages are the same as for a normal send. See Send an agreement.
If the field is empty, check that the notification fired, went to the address in JuicedSign Batch Email, and has only JuicedSign Batch Arguments in its body.
Check that JuicedSign Batch Arguments isn't empty on the record. It stays empty until there's a document to send.
For batch configuration messages, see Batch Config Portal messages and troubleshooting.