EDI Configuration

After moving EDI to the integration microservice, most of the configuration, such as mailbox identifiers, credentials, etc., has moved from the system journal EDI Configuration. Information on this configuration can be found at Setting up event reception from the Kontur_Diadoc mailbox

Current configuration in the “EDI Configuration” journal:

  • signContentType - specifies which part of the content will be signed with the digital signature. Possible values:

    • content (default) - this means the signature should be built based on the entire document content as a whole.

    • digest - the signature will be built based on the document “digest” calculated on the ECOS backend side. The EDI provider, as far as I know, does not recognize it as a document signature.

  • inboundPackagesProcessing - specifies the rules for processing incoming documents. Possible values:

    • BOX_ID - forces the system, upon receiving an incoming document, to search for the counterparty from whom this document originated. If the counterparty is not found, the document will not be loaded, and the EDI event will be skipped. The counterparty is searched for using EdiCounterpartyService algorithms based on the active provider.

    • ALL (or any other) - ignores the absence of a counterparty. All documents will be loaded into the system.

  • isplitLsdfDocflowByLegalEntities - Mirroring. The enabled flag indicates that an outgoing package sent to one’s own legal entity will also enter the system as an incoming one. Technically, when searching for attachments, packages, signatures - we search not only by identifiers but also by direction. Possible values:

    • true - enabled.

    • false (or any other) - disabled.

  • iallowGenerateLsdfPrintFormsAsyncOnFail - Optimization. Allows generating a print form (PF) asynchronously if the EDI provider could not provide it immediately upon receiving the package. Relevant for projects where customers receive a huge volume of formalized documents. Since for formalized documents, the original XML goes into the association, while generating the PF content takes time. This flag allows not interrupting the integration work and instead setting the eint:needUpdatePrintForm flag. Caution: if the project does not have a job that will regenerate documents with this flag, print forms that were not generated upon receipt will not be obtained at all. See Generating Print Forms.

    • true - enabled.

    • false (or any other) - disabled.