Imprint

Fabasoft eGov-Suite 2025 Update Rollup 2 (25.0.2)Permanent link for this heading

Build 25.0.2.38.169 (March 17, 2026)Permanent link for this heading

eGov18616, eGov18528

If Workflow rights are inherited from a File and a Subfile Collection to a File Document, these rights are no longer revoked when the Process of the File or Subfile Collection is completed. As long as a higher-level object propagates the Workflow rights, these rights remain in place

eGov18613, eGov17103

If the object name of a document is left blank when creating EDIDOC objects, the object address will be used from now on (Edition AUT)

Build 25.0.2.38.154-168Permanent link for this heading

Internal builds

Build 25.0.2.38.153 (February 27, 2026)Permanent link for this heading

eGov18461

If the first name, last name, or date of birth of a Person object is changed, any existing Area-Specific Personal Identifier (FSCSZRINT@15.1001:bpkbpk) is deleted and an attempt is made to determine it again

eGov18458

A DLL error could occur when retrieving return receipts (Vendo). The problem has been fixed

eGov18577

For organizations, it is now also possible to select “Flexible Corporation (FlexKapG)” as the legal form. In addition, “Flexible Corporation (FlexKapG)” is also taken into account in queries to the Company Register (Edition AUT)

eGov18506

For SOAP requests using SendHttpSoapMessage and REST requests using SendHttpJSONMessage, a default HTTP header is sent along with the request, which contains at least one user agent. This header can be customized in the HTTP connector used via the property “HTTP Header Fields” (FSCOWS@1.1001:httpconndefaultheaders)

eGov18529

The property “Name of Redaction” APPANNOTATIONS@15.1001:redactionname has been defined as a mandatory field. This means that unnamed blackouts cannot be created

Build 25.0.2.38.130-152Permanent link for this heading

Internal builds

Build 25.0.2.38.129 (February 6, 2026)Permanent link for this heading

eGov18452, eGov17201

When importing files using drag and drop, the permitted object classes in definitions are taken into account

eGov18508

Previous behavior: When marking Return Receipts after transfer to Vendo, the delivery profile was not used that the query for available Return Receipts performed. This resulted in the error “You are not authorized to mark this record.”

New behavior: When marking transferred Return Receipts in Vendo, the same delivery profile is now used as when querying available Return Receipts

(Edition CCA, Edition AUT)

eGov18458, eGov17814

Previous behavior: When polling Return Receipts against a Vendo installation, the wrong transfer status was checked when marking the Return Receipts in the Vendo service. This meant that in the event of an error, the same Return Receipt was queried again and again

New behavior: The status check has been adjusted so that the response from the service markNotifications no longer checks the status in the path MarkPollingResponse/Status but in the path MarkPollingResponse/Infos/Info/Status. If either the value ERROR or FATAL is checked here, the transferred return receipt is not saved and an error is output to the AT job

(Edition AUT)

eGov18450, eGov17738

An error in the display of PDF overviews when using Definitions has been fixed and no longer occurs

eGov18493

The generation of the JWT token for KeyCloak now also includes an Expiration Date of 4 minutes

eGov18449

When changing the property “Refers to” (COOELAK@1.1001:referrednumber), recipients created in the same transaction are no longer duplicated

eGov18456

The property “Import Limit for Attachments Governikus MultiMessenger” (FSCGMM@15.1001:gmmimportlimit) on the domain allows you to control how many attachments can be imported per Governikus MultiMessenger message. If the property is empty, then Governikus MultiMessenger messages may contain a maximum of 50 attachments (Edition DEU)

eGov18468

When Re-assigning closed Business Objects, a rights error could occur if the property “Fileplan Folder Subject” (COOELAK@1.1001:filesubj) was longer than 256 characters. The problem has been fixed

Build 25.0.2.33.116-128Permanent link for this heading

Internal builds

Build 25.0.2.33.115 (January 23, 2026)Permanent link for this heading

eGov18419

The dissolution of vBPKs is now supported. To do this, a private key (SOLEGOVCOREARS@111.100:szrprivatekey ) must be specified in the Configuration Concept, which can be used to decrypt the vBPKs. This private key must be in PKCS#8 format. The property “Private Key” (SOLEGOVCOREARS@111.100:szrprivatekey) is only visible to users with administrator privileges (Edition AUT)

eGov18406

When exporting with XDOMEA, the format code of documents is assigned regardless of whether the file extension is uppercase or lowercase. Previously, the file extension had to be lowercase in order to determine the correct format code (Edition DEU)

eGov18408

It prevents Contents from a Document assigned to a File from being re-assigned to a Document that is not assigned to a File. Previously, this re-assigning was possible (Edition CHE, Edition DEU)

Build 25.0.2.33.101-114Permanent link for this heading

Internal builds

Build 25.0.2.33.100 (December 18, 2025)Permanent link for this heading

eGov18352, eGov18343

During XML export, documents were not exported when the option “Export Dispatch Objects” was enabled and they were already finalized in the “Contents” list of the exported business document. The implementation has been adjusted so that these documents are also exported

eGov18347, eGov17698

An error when Re-Assigning a File with user-specific forms (from a definition) has been fixed and now works again (Edition CCA, Edition AUT, Edition DEU)

eGov18344

If, when finalizing a redaction, the redaction cannot be applied due to an error, the error is displayed to the user

Build 25.0.2.27.95-99Permanent link for this heading

Internal builds

Build 25.0.2.27.94 (December 5, 2025)Permanent link for this heading

eGov18299

A CSV migration has been added for the following properties in the “PrimeSign Personal Signature Configuration”:

  • SOLEGOVCOREHELPER@111.100:valuedictkey -> SOLEGOVCORECONFIG@111.100:valuedictkey
  • SOLEGOVCOREHELPER@111.100:valuedictvalue -> SOLEGOVCORECONFIG@111.100:valuedictvalue

Build 25.0.2.27.89-93Permanent link for this heading

Internal builds

Build 25.0.2.27.88 (November 17, 2025)Permanent link for this heading

eGov18179

There is a new additional AT job function FSCGOVDLV@1.1001:GetDynamicVendoNotifications that determines all possible delivery profile IDs for an installation and performs a polling query to Vendo for each of them. This now allows you to query all possible variations. The query is transactionally secured and the error messages now also contain the profile ID as information. (Edition AUT)

eGov18208, eGov17835

When using form pages in process definitions, an error occurred when checking mandatory fields during the creation/editing of objects. This error has been fixed

eGov18045

The following improvements have been made to standard electronic delivery (not hpc DUAL):

  • The name of the transmitted documents is adjusted during transmission to the delivery service so that characters that are not permitted according to the specification are replaced by an “_”
  • The “attn” information is now also transmitted in XML for natural

The following improvements have been made to Return Receipt processing:

  • The Return Receipt status “Partially Delivered” (RR_STATE_PARTIALLYDELIVERED) has been renamed to “Open - In Delivery”
  • If the status “Delivered (1920)” is transmitted in a P11 transmission in the hybrid Return Receipt, the status of the Return Receipt is now also set to “Delivered” with the corresponding delivery date

The following general improvements have been made:

  • If an Outgoing has only been partially processed, an additional status symbol is now displayed to alert the user

eGov18071

Previously, no errors were triggered in the IFG functionality “Publish Documents” if the creation of redacted content failed. This issue has been resolved

Additional Information regarding the modified action EGOVBASE@15.1001:GetWebRedactedContentsForPrint :

  • The action is no longer executed on a list of redacted objects. Instead, it is executed on the calling object
  • The action throws an error if it fails. This did not happen previously.
  • The action has been renamed to EGOVBASE@15.1001:GetWebRedactedContentForPrint
  • The action now only returns the redacted content

eGov18111, eGov18036

On Windows Server systems, ANSI-encoded addressee imports are processed correctly in Outgoings (there were problems with umlauts)

eGov18217, eGov17279

The menu “Properties” in the Explore view of a user reopens the properties of the user

eGov17963

Previous behavior: If a deposited delivery item was not picked up during electronic delivery, the delivery status was changed to “Not delivered”, even though the delivery status was previously either “Delivered” or “Deposited”

New behavior: The delivery status is no longer changed. Instead, a workflow is initialized with a note that the delivery item was not picked up

(Edition AUT)

eGov18054

When an XDOMEA package is loaded, the old Business Number of the object (from the XML of the XDOMEA package) is now written to the property “File Reference” (COOELAK@1.1001:filereference) in the XDOMEA protocol (Edition DEU)

eGov17814

Previous behavior: When polling Return Receipts against a Vendo installation, it could happen that the Return Receipt was processed and saved, but the transaction could not be transferred to Vendo. As a result, the same Return Receipt was queried repeatedly

New behavior: Error handling during polling has been improved so that a Return Receipt is now transmitted in a single transaction, including status transmission to the Vendo. This prevents the above-described case from occurring again

(Edition AUT)

eGov18049

The Java library CXF-Core has been upgraded from version 3.5.11 to version 3.6.8 (Edition DEU)

eGov17962

Previous behavior: If an electronic delivery item was picked up on the exact day of the first notification, the delivery date was calculated incorrectly. In this case, the next business day was also used

New behavior: The delivery date is now set to the pickup date because it matches the day of the first notification. This is an exception in the Delivery Act

(Edition AUT)

Build 25.0.2.20.69-87Permanent link for this heading

Internal builds

Build 25.0.2.20.68 (October 24, 2025)Permanent link for this heading

Release