Create a package from a template with Node js

Hi gui12343,

Thanks for reaching out to us! Two points regarding to your questions:

(1)As per this StackOverflow post as well as my own test, you should put JSON as "body" of the options.

var options = { uri: 'https://myurl.com', method: 'POST', json: true, body: {'my_date' : 'json'} } request(options, myCallback)

Otherwise if you put it as "formData" or "form", OneSpan Sign system would thought the request type is multipart/form-data, therefore threw the "Unsuported media type" error.

(2)The reason why "the package is created, but without any informations about the signer in it" is because the role ID of the placeholder may not be "Signer1" as you thought, in which case if the role ID is a mismatch, OneSpan Sign system will add a new role instead of replacing the placeholder.

If you created the template from UI portal, the "Signer1" only specifies the role name, whole the actual role ID is uniquely generated by system in format of UUID. If you provide me your template ID, I can check the actual role ID for you.

{
  "name": "Package created from template through REST API",
  ......
  "roles": [
    {
      "id": "0be4ccd5-bf89-4bed-9dc1-c47cea76ffeb",
      "type": "SIGNER",
      "signers": [
        {
          "firstName": "myfirstName",
          "lastName": "myLastName",
          "email": "[email protected]"
        }
      ]
    }
  ]
}

Duo

Thank you for your quick answer! Here is my template ID : DdHlV6PprU-_QKoJYIFieb9ewCk=

Thanks for the sharing! The actual role ID is "9ad1728d-2e24-44cd-9f74-0fc534dedd7f"

Duo

Thank you so much, it's working now :)

Hi again!

I still have a problem when I try to send a form with my code... We changed the templates that we send and now I have this error : error.validation.packageActivation.unassignedRole. 

Here are the 2 templates id we use : 

templateIdFr:'f3Y8GI9_KpKaakpR1TdCh6pj40Q=', 

templateIdEn:'HL9zxrDwwPo1AFMyI3UNrg3dzFI=',

Could you help me with that? Maybe we did'nt set up our templates like the last one I guess and I am not able to find the right signer id..

Thank you very much for your help.

Hi gui12343,

This error message "error.validation.packageActivation.unassignedRole" normally indicates that there is a role with no signer (placeholder recipient), so I am guessing your code didn't correctly specify the placeholder role ID like the other time? Could you kindly check if you've specified the placeholder IDs as:

f3Y8GI9_KpKaakpR1TdCh6pj40Q=: 939dbaa2-99b7-4425-beb0-51b058df69ca

HL9zxrDwwPo1AFMyI3UNrg3dzFI=: 5776a676-eba7-42ed-a285-859f28ca763c

Duo

First things first, gather your project templates together. If you haven’t got any templates, it’s time to make one. I started with a simple NPM project with a spec/index.spec.js file, an index.js file, a package.json, and a .gitignore. I filled these files with generic starter code.

FaceTime PC
 

Hi Duo_Liang, 

Thank you, it worked! I found out how to retrieve the information now, I should be able to do it myself next time with postman haha. 

I have an other question, I don't know if I need to open a new post, but I will ask it here ; Do you know if we can do fields injection in the payload of a clone template request? I read that it was not possible in the past, maybe it is now. 

Thank you again,

- Gui

Hi Gui,

Unfortunately it's still not available in the current implementation, while you can use label fields instead, which display the value and are not editable during signing ceremony. After your application clones a package out of the template, bulk update the fields using this API (you can invoke a GET call prior to the PUT call and inject the field values by filtering field names)

Duo

Allright, thank you it should be fine with what we want to do!

-Gui