bizdoc | Object The document you want to digitally sign. The document must be an instance of com.wm.app.tn.doc.BizDocEnvelope. |
flags | Object (optional) Flags that specify the pre-processing actions for the document. If specified, the service uses the verify? flag to determine whether to create the digital signature. The flags must be an instance of com.wm.app.tn.route.PreProcessingFlags. |
Every TN document type is associated with a signing service. The
wm.tn.doc:sign service looks up the appropriate signing service and executes it against the supplied document. The service attaches all resulting errors to the document and logs them to the activity log in the Trading Networks database (if the document is saved to the database). To retrieve the signing errors from the activity log, use the
wm.tn.doc:getEvents service.If the document is an outbound XML document and the receiver's profile in the Trading Networks system contains a private key and digital certificate, the XML signing service generates a PKCS#7 detached digital signature for the supplied document, base 64 encodes it, and inserts it into the document in the location specified by the Signature query. The service uses the SignedBody query to determine what portion of the XML content to sign.If flags is non-null, the service uses the verify? flag to determine whether to sign the document. For the format of flags, see
wm.tn.rec:PreProcessingFlags.