Skip to content
background-image background-image

ISDS outgoing reader

[ | version 3.1]

Building a comprehensive content for you: A Work in Progress...

Connector

The connector is permitted for use of the platform background agent.

Connector processing type: Row by row!

Configuration

ISDS Connection configuration

Username

Defines the login name that is used for CPost messagebox authentication.

Password

Defines the password that is used for CPost messagebox authentication.

Credentials

Supported credential types:

  • ManualInput - login credentials are taken from this configuration properties UserName and Password.
  • TakeFromInput - login credentials are taken foreach input row from input data properties UserName and Password.

ISDS Outgoing Messages Reader configuration

From

Date with time from which take the messages. (format: 2022-02-07T15:30:24.914Z for UTC or 2022-02-07T15:30:24.914 for local)

To

Date with time from which take the messages. (format: 2022-02-07T15:30:24.914Z for UTC or 2022-02-07T15:30:24.914 for local)

Status

All statuses Message passed Message signed Message not validated by antivirus Message sent to recipient Elapse 10 days from delivery Message delivered by signing-in Message read Message marked as undeliverable Message content deleted Message moved to safe

Number of messages to process

Maximum number of messages which will be processed in one task run. When empty, all messages are processed

Include ZFO format

Include ZFO format of signed message

ISDS Messagebox configuration

Recipient ID

ID of message box. Input data can be referred by using placeholders, ie. ${input.ObjectID} will be replaced by value in ObjectID property.

ISDS Environment configuration

Testing Environment

When set to true messages are send to testing environment.

Input & Output Schema

Input

Data schema is optional

The connector does not expect a specific schema. The required data structure can be achieved by correct configuration. Although the selected connector doesn't require a schema generally, the individual integration task step may need to match the output data structure of the preceding task step and use a data schema selected from the repository or create a new input schema.

Output

(krom poslednich 3 polozek je to uplne stejne jako ISDSIncommingMessage)

ISDS outgoing message (ver. 1.1.0)

Column Data type Allow null Description
ID string No
IDSender string Yes
Sender string Yes
SenderAddress string Yes
SenderType string Yes
SenderOrgUnit integer Yes
SenderRefNumber string Yes
SenderIdent string Yes
IDRecepient string Yes
RecepientAddress string Yes
RecepientOrgUnit string Yes
RecepientOrgUnitNum integer Yes
RecepientRefNumber string Yes
RecepientIdent string Yes
ToHands string Yes
Annotation string Yes
LegalTitleLaw integer Yes
LegalTitleYear integer Yes
LegalTitleSect string Yes
LegalTilePar string Yes
LegalTilePoint string Yes
PersonalDelivery bool Yes
AllowSubstDelivery bool Yes
DeliveryTime DateTime Yes
AcceptanceTime DateTime Yes
MessageStatus integer Yes
MessageStatusName string Yes
AttachmentSize integer Yes
SignedFileName string Yes
SignedFileContent base64 Yes
Files ISDS File 1.0.0 Yes
DeliverySignedFileName string Yes
DeliverySignedFileContent Base64 Yes
DeliveryEvents ISDS Delivery Event 1.0.0 Yes

ISDS file (ver. 1.0.0)

Column Data type Allow null Description
Name string Yes Name of file
MimeType string Yes file mime type
MetaType string Yes Meta type
Data Base64 Yes file content

MetaTypes:

  • main - the first document file
  • enclosure - attachment file
  • signature - digital signature file
  • meta - specific XML data formated file

ISDS delivery event (ver. 1.0.0)

Column Data type Allow null Description
Time DateTime Yes cas doruceni udalosti
Description string Yes popis udalosti

Release notes

3.1.2

  • Fixed loading dependant libraries.