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

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