Skip to content

DMS and ECM Interface#

See also the following ChangeLogs#

28.2.1211.0 - 2026-06-25#

Hotfix

  • Path is truncated to 250 characters when moved via a posting (#17994, KUCON-328)
  • ELO - Ignore references in “Own Documents” (#18044, KUCON-331)
    In ELO, document references can be created independently of BC. Since multiple objects can reference one another, this can result in a fairly deep structure. As long as a search definition is active, this is not a problem. The issue arises when you switch to “Show Own Documents.” At that point, the system attempts to gather all documents located below the configured storage path—including referenced documents. Beyond a certain depth, this not only leads to performance issues in the DMS and ECM interface but also causes an error because the path exceeds the character limit.
  • Check maximum length of filenames - ELO => Short Description (#18046, KUCON-330)
    Within the ELO Suite, a file name—including the file extension—must not exceed 128 characters in length. At the same time, certain characters must not be used in file names when archiving files. This has been corrected. Depending on the DMS system in use, the relevant rules for modifying or shortening file names are ta
  • Automatic Selection of Storage Definitions for Reports (#18061, KUCON-332)
    If no storage definition is assigned during “automatic report archiving,” the DMS and ECM interface searches for a suitable storage definition. At this point, the system should only search for storage definitions with the “Only for background uploads” flag. However, this was not the case. The search was filtered by table only, and the matching entry was selected based on the sort order. This has been corrected. As part of automatic report archiving, the system now uses the first match in the sort order that corresponds to the respective table and has the “Only for Background Uploads” flag set.

28.2.1184.0 - 2026-06-12#

Change

  • Updating Tags with Release of Purchase or Sales Documents may also update posted document entries (#17482, KUCON-319)

28.2.1176.0 - 2026-06-10#

Hotfix

  • Error with missing placeholders at setup import while importing file packages (#17563, KUCON-321)
    When importing a configuration via the “Import/Export Setup” process, the import of the file packages fails with a message stating that placeholders are not defined. This is because the relevant placeholders do not yet exist at the time the file package line is imported. This has been fixed.
  • Placeholder greater 9 will be ignored (#17740, KUCON-324)
  • Commit Error at posting preview on warehouse shipment (#17890, KUCON-327)
    During the posting preview, posting processes are executed that may result in documents being printed automatically. For this reason, the preview status is now taken into account. If a process is initiated from the posting preview, related documents are no longer automatically printed and archived.

Change

  • Translation into Spanish (#17486, KUCON-320)
  • Allow setting of SingleInstance Storage Definition by public procedures. (#17880, KUCON-326)

28.0.1154.0 - 2026-04-20#

Hotfix

  • Missing Data in Import/Export Setup functionality (#17374, KUCON-317)
    When importing setup data within the document storage setup, there were some new logistics fields missing and therefore the setup initalized the values with the default entries. This has been fixed. the new logistics auto-handling fields are also transfered.
  • Error Message when archiving from the logistic documents (e.g. Warehouse shipments) (#17375, KUCON-318)
    Error Message when archiving from the logistic documents (e.g. Wahrehouse shipments) - "The Report could not be automatically archived by the Auto. Report Archiving "XXX". The Auto. Report Archiving refers to table 110 - Sales Shipment Header, but the report does not contain a DataItem for this table.” If posting and printing Warehouse shipments for example, the BC standard logic is using record marks for selection of the shipments and/or invoices to print. Unfortunately marking records in BC is a kind of filter, we can not handle later on in printing. Therefore, the filterview within the payload of the report is not filled. In order to fix this, we need to get the marked records and build a fully automated “real” filter out of this in order to make the filterview work correctly.
  • Saperion: The system attempts to display EML files as JPGs and downloads them as such. (#17387, KUCON-316)
    When emails in EML format with attachments are stored in Saperion, the email is assigned the filename of the last attachment and interpreted as such when searching for and/or downloading the files. This is due to the multipart format used, as the file attachments it contains represent separate entries within the stored file structure. This has been corrected.

28.0.1119.0 - 2026-04-02#

Change

  • General performance and stability improvements.