SignContent
What to use it for | Prerequisites for usage | Essential properties to set |
---|---|---|
Add a digital signature to documents. The document content can be signed electronically, using the information from a certificate file that contains a private key. |
| Certificate location, and depending on the setting. |
Options for SmartBridge 3
Primary options
Option What is it How to use it Current document Use CurrentDocument to indicate which data you want to process with the current Activity. This option only becomes relevant in case a preceding Activity generated new documents. In general, leave at the default value. In most cases you do not need to modify this option. The only situation in which you might need to modify this option, is when your Workflow produces several new documents based on one incoming original document. Activities that use a single document to produce several documents: These Activities produce several documents, and some of those might require additional, specific processing. To be able to indicate which documents require different processing, you will need to have done the following:Input Options
Certificate location options
Depending on where your certificate is stored there are different primary options for the certificate location settings. Therefore, first select your certificate location. Other option
Option | What is it | How to use it |
---|---|---|
Certificate location | The repository that contains the certificate. This option affects which other options you will need to configure next. | Select an option from the dropdown list:
Click here to expand... The most common options are PFX file and WindowsStorage.
|
Certificate location | Options | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
PFX_file | Click here to expand... Required settings when using a PFX file.
| |||||||||||||||||||||
WindowsStorage | Click here to expand... Required settings when using WindowsStorage.
| |||||||||||||||||||||
PKCS11_Storage | Click here to expand... Required settings when using PKCS#11 storage.
| |||||||||||||||||||||
PKCS11_NSS_Storage | Click here to expand... Required settings when usingPKCS#11 NSS storage.
|
Document type specific options
Option | What is it | How to use it |
---|---|---|
Type of document to be signed | To indicate the type of document to be signed. This option affects which other options you will need to configure next. | Select an option from the dropdown list:
|
Type to be signed | Options | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Click here to expand...
| ||||||||||||||||||||||
EDIFACT | Click here to expand...
The implementation follows the GS1 Spain guidelines. Specific configurations can be created for dealing with specific Spanish parties, as Carrefour Spain.
|
All options
Certificate location options
Option | What is it | How to use it |
---|---|---|
PKCS11 DLL file | The DLL file on the hardware device to be able to use the certificate, using the PKCS#11 protocol. | Provide the absolute path to the PKCS#11 DLL file. |
PKCS11 slot index | Which certificate to use, in case there are several certificates on the device. When stored, PKCS#11 certificates are assigned a slot. Each slot is numbered. | Enter an integer to reference the relevant certificate. |
PKCS11 PIN | The PIN is the access code required to be able to open the PKCS#11 storage. | Provide the PIN code. |
NSS storage folder | The folder that contains the NSS PKCS#11 storage. | Provide the absolute path to the folder. |
Subject common name | The common name of the certificate subject, as listed in the certificate details under 'CN'. | Enter the exact common name ('CN') of the certificate subject. |
Issuer common name | The common name of the certificate issuer, as listed in the certificate details under 'CN'. | Enter the exact common name ('CN') of the certificate issuer. |
Document type specific options
Option | What is it | How to use it |
---|---|---|
Type of document to be signed | Select from the dropdown list:
|
EDIFACT specific options
The implementation follows the GS1 Spain guidelines. Specific configurations can be created for dealing with specific Spanish parties, as Carrefour Spain.
Option | What is it | How to use it |
---|---|---|
Signature profile file path | The absolute path to the file containing the profile to be used during the EDIFACT signing process. | Select the file using the file picker. |
Each segment on new line | Specifies whether the resulting EDI file should have line breaks after each segment. | (Un)check the option:
|
Add last UNT segment if missing | Specifies whether the system should add a UNT segment for the last message in the interchange, in case it is missing. Click here to expand... Every EDIFACT document should end with a UNT segment, as UNT segment indicates the end of a document. A UNT segment contains the following information:
| (Un)check the option:
|
Input Options
Option | What is it | How to use it |
---|---|---|
Current document | Use CurrentDocument to indicate which data you want to process with the current Activity. This option only becomes relevant in case a preceding Activity generated new documents. | In general, leave at the default value.
Read more » The only situation in which you might need to modify this option, is when your Workflow produces several new documents based on one incoming original document. Activities that use a single document to produce several documents: These Activities produce several documents, and some of those might require additional, specific processing. To be able to indicate which documents require different processing, you will need to have done the following:
|
Misc
Option | What is it | How to use it |
---|---|---|
DisplayName | Name of the Activity. | Leave at default, or edit the name to clarify the difference with a similar Activity. |
PDF specific options
Option | What is it | How to use it |
---|---|---|
Type of document to be signed. | To indicate the type of document to be signed. This option affects which other options you will need to configure next. | Select an option from the dropdown list:
|
Signature author | (Optional field) Information to contact the author of the signature. | Example: provide an e-mail address. |
Signature reason | (Optional field) Reason to sign the document. | Optionally, provide a reason for signing the document. Click here to expand... Examples of reasons:
|
Signature location | (Optional field) Information to indicate the location of the party that signed the document. | Enter a location. Examples:
|
Make signature visible | Whether the information provided in these settings should be presented as a visible, textual watermark on the PDF. | (Un)check the options:
|
Create MDP certificate | Feature to sign documents using MDP, a signature for Modification Detection and Prevention. This is an outdated type of signature that is not recommended to be used. | (Un)check the options:
|
Options for SmartBridge 2
All options
Activity
Every Workflow Activity needs to have a name, and be configured to be either on or off. These generic properties are part of the Activity properties.
Option | What is it | How to use it |
---|---|---|
Name
| A unique name for the Activity. Names are used for two reasons:
|
|
Description | Description of the activity, to give others some context about the Activity. | Enter an optional description. |
Enabled
| Specifies if the Activity should be enabled or not. Disabled Activities will be skipped during Workflow execution and validation. | Select option from the dropdown:
Recommended: True |
Certificate location options
Option | What is it | How to use it |
---|---|---|
PKCS11 DLL file | The DLL file on the hardware device to be able to use the certificate, using the PKCS#11 protocol. | Provide the absolute path to the PKCS#11 DLL file. |
PKCS11 slot index | Which certificate to use, in case there are several certificates on the device. When stored, PKCS#11 certificates are assigned a slot. Each slot is numbered. | Enter an integer to reference the relevant certificate. |
PKCS11 PIN | The PIN is the access code required to be able to open the PKCS#11 storage. | Provide the PIN code. |
NSS storage folder | The folder that contains the NSS PKCS#11 storage. | Provide the absolute path to the folder. |
Subject common name | The common name of the certificate subject, as listed in the certificate details under 'CN'. | Enter the exact common name ('CN') of the certificate subject. |
Issuer common name | The common name of the certificate issuer, as listed in the certificate details under 'CN'. | Enter the exact common name ('CN') of the certificate issuer. |
PDF specific options
Option | What is it | How to use it |
---|---|---|
Type of document to be signed. | To indicate the type of document to be signed. This option affects which other options you will need to configure next. | Select an option from the dropdown list:
|
Signature author | (Optional field) Information to contact the author of the signature. | Example: provide an e-mail address. |
Signature reason | (Optional field) Reason to sign the document. | Optionally, provide a reason for signing the document. Click here to expand... Examples of reasons:
|
Signature location | (Optional field) Information to indicate the location of the party that signed the document. | Enter a location. Examples:
|
Make signature visible | Whether the information provided in these settings should be presented as a visible, textual watermark on the PDF. | (Un)check the options:
|
Create MDP certificate | Feature to sign documents using MDP, a signature for Modification Detection and Prevention. This is an outdated type of signature that is not recommended to be used. | (Un)check the options:
|
EDIFACT specific options
The implementation follows the GS1 Spain guidelines. Specific configurations can be created for dealing with specific Spanish parties, as Carrefour Spain.
Option | What is it | How to use it |
---|---|---|
Signature profile file path | The absolute path to the file containing the profile to be used during the EDIFACT signing process. | Select the file using the file picker. |
Each segment on new line | Specifies whether the resulting EDI file should have line breaks after each segment. | (Un)check the option:
|
Add last UNT segment if missing | Specifies whether the system should add a UNT segment for the last message in the interchange, in case it is missing. Click here to expand... Every EDIFACT document should end with a UNT segment, as UNT segment indicates the end of a document. A UNT segment contains the following information:
| (Un)check the option:
|
Document identification
In case you use the Clone Activity, SmartBridge will use this property to identify cloned documents.
Option | What is it | How to use it |
---|---|---|
Document Key | Only relevant for Workflows that contain a CloneDocument Activity. The key of the cloned document to be used for processing. Click here to expand... When creating a clone of the document (using the CloneDocument activity) you need to specify whether SmartBridge should process the clone or the original. When you have specified a Document Key, SmartBridge will assign the Document Key to cloned documents. With the Document Key assigned to cloned documents, you will be able to refer to the clones for further processing. |
Recommended: Leave empty when you are not using a Clone Activity. |
In SmartBridge 3 this option is replaced with 'Input Options'.
On this page
EDIFACT Activities
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
-
Page:
-
Page: