You can create print code in two ways.
- Use URI scheme to build it manually
- Use the built-in Integration Code utility in the Desktop Application. We recommend this option.
If you wish to build it manually, here is the URI scheme integration. The URI scheme is written in a language called JSON.
The built-in integration code is best suited when you have:
- a Microsoft Excel sheet of recipient information
- a Microsoft Word document meant for all recipients listed in the Excel sheet
In order to use this method, you need to download the Desktop application and the printer extension, Introduction to the Desktop application. This method also requires Microsoft Word and Excel because of the mail merge function.
How to set up printer codes
To start a new code you can build and write it all yourself. However the easiest way to start a new code is to open the desktop application and fill it out as you would a normal case file using a template.
- Open the Desktop application.
- If you have static fields, meaning for example that you want the same name for each case file you create, input the name of the case file in the respective field. Otherwise, you put placeholder names that will later be replaced in the code. You could also make the tile partly static. For example, you could choose that the name of the case file should be “Contract”, but you want to add the signer’s name at the end, this does not need to be added manually, simply add a merge field after the static text in the later code.
- Choose the settings for your case file in the first step as you normally would.
- Add a placeholder document. The document itself, the PDF, will not be saved.
- Add a placeholder signer, for example you can name them “SignerName” and set the email to “email@example.com”, the SSN to “1234567890”. We will replace these fields with merge fields later. Also decide on the settings for the signer, ex. reminders.
- If you wish to select a specific email template for these send outs, go to the next page.
- Your desktop application might now look like this.
- In the top menu bar, click on Developer, and then Create Integration Code. Copy the code and paste it into the document you wish to send out through Penneo. If you wish to know more specifics about the code, see the glossary below.
- While still in Word, click on the tab Mailings.
- Click on Select Recipients and choose Use an existing list in the drop-down.
- Locate and select your prepared Excel sheet, it might look something like this:
- When you click on Insert Merge Field, you should have a selection of choices depending on the structure of your Excel sheet.
- If you have places in the document the information from the Excel sheet should appear, simply place your mouse in that spot, click on Insert Merge Field and choose the corresponding one, see the example below.
- Now, the code you pasted into this document needs to be changed. Replace the placeholder names in the code that you entered the Desktop app. If you look back to step 5, and you remember that you saved the signer name as SignerName, replace it where you find it in the code with the corresponding merge field, see an example below.
- The last thing you need to do is replace the local path, it is currently directing to the placeholder documents location, but you want to print the file the code is in. The path will start off with something like this C:\\Users\\[USERNAME]\\Documents\\Test%20dokument.pdf, replace the entire path with #printfile#. The code in your document should now say “localPath”:”#printfile#”.
- To hide the code in the final document, make it white and minimize the font size.
- Click on Preview Results, you can use the arrows on the right side of this button to go between the signers. Choose which signing request you want to send out first and go to the corresponding number.
- Before the next step, make sure that your Desktop application has been cleared. If not, click on Advanced options and choose Clear fields.
- In Word, go to File, then choose Print. Select the Penneo Printer in the dropdown menu and then click on Print.
- In the Desktop application, your document will have loaded and it’s ready for send out.
- Click Next and then Send documents.
- Repeat step 16-20 and go to the next signer in the Preview Results.
Integration Code Glossary
Spaces in the code %20: The code should not have any spaces so if you have text where there might be a space such as a name, Name Surname, you use %20 instead of the space e.g. Name%20Surname.
Penneo: is being used to call Penneo. This is always needed in the front of the code.
templateId: This is the ID for the case file type you wanna set.
name: You will see “name” several places in the code. Here it is for naming the case file. Remember the rules about spaces. merge field can be used here.
language: Set the language of the case file. Options are, en = English, da = Danish, sv = Swedish, no = Norwegian.
folderId: Set the folder ID for the folder you wanna save the case file to. The default is your selected standard folder.
signOnMeeting: Select to activate the feature, Sign documents at the meeting. Variables are, true or false. Default is false.
sensitiveData: Select if the case file has sensitive data activated. Variables are, true or false. Default is false, unless it is activated on a company level. Ask your administrator about this.
visibilityMode: Sets what documents the signers can see. There are 2 settings, all_documents and certain_documents. Default is all documents
messageTemplate: Write the name of the email template you want to use.
messageSubject: Set the subject of the email you want to send to the signers. Not necessary if you have selected an email template.
messageText: Set the body of the email that you want to send to the signers. Not necessary if you have selected an email template.
documents: This next section is all about the documents that are added to the case file.
name: Once again we see name, but this time it is for naming the document. Remember the rule about spaces, merge field can be used here.
order: This sets the order in which the documents are added to the application. It counts from 0, e.g. 0 will be the first document, 1 will be the second document and so on.
type: The ID of the document type that is available from the case file type. This is dependent on the case file type that is selected with templateId.
localPath: This is the file path for the PDF you want to add. If the document you want to add is already the document this code is in, and you are printing it, you use #printfile# to tell the system that it is the text document you are in.
signers: The next is about the signers that are being added to the case file in the desktop application.
name: This is the name of the signer. Remember the rule about spaces, merge field can be used here.
email: The email address of the signer, merge field can be used here.
onBehalfOf: Inputs data in the field for “on behalf of” for the signer. Remember the rule about spaces. merge field can be used here.
isPrivate: Enable the private setting for the signer. Can be either true or false.
enableTouch: Enable touch signature for the signer. Can be either true or false
roles: Set the ID’s for the roles the signer should have. These are dependent on the document types that have been selected with documents. ID’s are separated by a comma (,).
ssn: Set the Social Security Number for the signer, merge field can be used.
vatin: Set the company number for the signer. This is only for certain Danish signers, merge field can be used here.
reminderInterval: Set the reminder interval for the signer. Default is 2, unless something else has been selected for your company. Ask your administrator about this.
copyRecipients: You can set copy recipients if you have any of those. They are set up the same way as signers but only with name and email address.
name: Set the name of the copy recipient. Remember the rule about spaces, merge field can be used here.
email: The email address of the copy recipient, merge field can be used here.
sendAt: Set the date and time for when you want to activate the case file. If you want it activated right away, ignore this setting. Remember to account for summertime. If you want to set a date such as 31/12-2020, the format should be: 2020-12-31T12:00:00+01:00
The last part with +01:00 is the summertime off. If it is on, it should be +02:00.
expireAt: Set the date and time for when the case file should expire. Cannot be earlier than activation date and time. Same rules for sendAt date and time apply for this.
reference: Set the reference you want here. Remember the rule about spaces, merge field can be used here.