...
Limitations and Known Issues
None.
Snap Views
Type | Format | Number of Views | Examples of Upstream and Downstream Snaps | Description |
---|---|---|---|---|
Input | Document |
|
| This Snap has, at most, one document input view. Each document contains data in the form of JSON. |
Output | Document |
|
| This Snap has, at most, one document output view. Each document contains a corresponding response in the form of JSON. |
Error | Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter when running the pipeline by choosing one of the following options from the When errors occur list under the Views tab:
Learn more about Error handling in pipelines. |
Snap Settings
Info |
---|
|
Field Name | Field Type | Description | ||
---|---|---|---|---|
Label* Default Value: SMIME | String | The name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your pipeline. | ||
Sign Default Value: Deselected | Checkbox | Select this checkbox to enable the digital signing of the data | ||
Signer Algorithm Default Value: sha1 | String/Expression/Suggestion | A signer algorithm is the cryptographic algorithm used in digital signatures to generate and verify the integrity and authenticity of electronic documents or messages. | ||
Encrypt | Checkbox | Select this checkbox to enable the encryption of the data. | ||
Encrypt Algorithm* Default Value: 3des | String/Expression/Suggestion | Specify the algorithm to encrypt the data. | ||
Certificate
Default Value: N/A | String/Expression | Specify the relative path of the X.509 certificate in the SLDB. You can upload the certificate to the SLDB by clicking . An X.509 certificate is a standard format for public key certificates that securely associates cryptographic key pairs with identities such as websites, individuals, or organizations.
| ||
Content Transfer Encoding
Default Value: base64 | String/Expression/Suggestion | Select the Content Transfer Encoding from the suggestions list. Content Transfer Encoding is a mechanism used in email communication and other protocols to encode the content of a message for transmission. | ||
Headers | Checkbox | Select this checkbox if you want the Snap to write SMIME-generated headers to the output. | ||
Snap Execution Default Value: | Dropdown | Select one of the following three modes in which the Snap executes:
|
Snap Pack History
Expand | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
|
...
...