Imprint

Fabasoft eGov-Suite 2025 September Release (25.9.0)Permanent link for this heading

Build 25.9.0.381.71 (January 29, 2026)Permanent link for this heading

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)

Build 25.9.0.381.67-70Permanent link for this heading

Internal builds

Build 25.9.0.381.66 (January 12, 2026)Permanent link for this heading

eGov18368

When indexing objects for Mindbreeze AI, an optimization regarding the indexing of folders and Teamrooms has been implemented. These are now only indexed if they are marked for indexing

In addition, the White Paper “Konfiguration von Mindbreeze AI” documents the configuration of the AT job, which is necessary for Teamrooms to be indexed in the background when the chat is activated

(Edition CCA, Edition AUT, Edition DEU)

Build 25.9.0.381.64-65Permanent link for this heading

Internal builds

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

eGov18341

Previous behavior: To activate chat in the Teamroom, it was previously necessary to configure the Configuration Concept. This was complex and opaque for the end user

New behavior: In the Teamroom, it is only necessary to select the option “Mindbreeze AI option for “Ask Questions”” on the tab “AI Settings”. The Configuration Concept can still be used, but it is no longer necessary

eGov18345, eGov18068

When using custom rules, the correct signature profile is used for the Authority Signature (Edition AUT)

eGov18344

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

Build 25.9.0.381.58-62Permanent link for this heading

Internal builds

Build 25.9.0.381.57 (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.9.0.381.54-56Permanent link for this heading

Internal builds

Build 25.9.0.381.53 (November 27, 2025)Permanent link for this heading

No changes

Build 25.9.0.372.46-52Permanent link for this heading

Internal builds

Build 25.9.0.372.45 (November 12, 2025)Permanent link for this heading

eGov18001

The property “Precondition” (SOLEGOVCOREEXECUTION@111.100:exprecondition) was added for all execution steps on the form page

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)

eGov18006

Customization points have been added for “Container With User Data”, “Document With User Data” and “Object With User Data” to prevent errors when deleting these objects from Teamrooms

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

eGov18098

When duplicating a Business Object, the Dispatch properties of a copied addressee line were sometimes incorrectly not reset. The problem has been fixed

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)

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.9.0.372.29-44Permanent link for this heading

Internal builds

Build 25.9.0.372.28 (October 16, 2025)Permanent link for this heading

eGov18002

The version number of the software products has been raised to 250900

Build 25.9.0.369.27Permanent link for this heading

Internal build

Build 25.9.0.369.26 (October 9, 2025)Permanent link for this heading

eGov17995

An improved version of the Fabasoft Sans font is now used in the product. If dts-chromium or dts-libreoffice are in use, they must be updated to dts-chromium version 5.9.562 or dts-libreoffice version 4.0.352

eGov17941

An error in the implementation of SZR queries has been fixed (DeliverAddress has been replaced by DeliveryAddress) (Edition AUT)

Build 25.9.0.368.25Permanent link for this heading

Internal build

Build 25.9.0.368.24 (October 8, 2025)Permanent link for this heading

eGov17799

The user help has been converted to the new Fabasoft Sans font. To ensure consistent presentation in the user manuals, all screenshots have also been removed

eGov17961

The action FSCPROTOCOLMANAGER@15.1001:CallService now supports HTTP headers for the HTTP methods Post and Get as well. Previously, these were only taken into account for a Put request

eGov17922

When processing a DualNotificationRequestType during the transfer of a Return Receipt, in the event of an error, the detailed messages are now also stored in the actions performed for the Return Receipt. (Edition AUT)

eGov17934

When deleting objects, canceled objects (COOELAK@1.1001:cancelledobj) are now also taken into account and deleted (Edition AUT)

Build 25.9.0.363.16-23Permanent link for this heading

Internal builds

Build 25.9.0.363.15 (September 29, 2025)Permanent link for this heading

eGov17927

The Insight App and the Pipeline ID can now be controlled via the Configuration Concept of the Fabasoft eGov-Suite. The Pipeline IDs are addressed via the Pipeline Key

eGov17895

The properties “Softwarecomponent (Draft)” (EGOVTEMPLATE@15.1001:ufcompdraft) and  “Softwarecomponent (Released)” (EGOVTEMPLATE@15.1001:ufcomprelease) are not required when creating forms in a Teamroom. The error messages do not apply in this case (Edition CCA)

eGov17930

In certain rare cases, the configuration for individual objects was not calculated correctly in object lists. This could result in Work items for individual activities not being displayed in the Worklist, for example, because certain other activities were in the Worklist. This problem has been fixed

eGov17882

The use case for summarizing business objects with Mindbreeze AI was implemented and activated

eGov17919

Semantic indexing for Mindbreeze AI has been optimized for Files and Teamooms. In addition, the subsequent indexing of objects has also been enabled!

eGov17931

The evaluation of the properties “Visible in Taskpane” and “Visible in Contextmenu” in Applications has been improved for the Teamroom

Build 25.9.0.363.12-14Permanent link for this heading

Internal builds

Build 25.9.0.363.11 (September 25, 2025)Permanent link for this heading

eGov17886

The user manuals have been updated for the September 2025 release of the Fabasoft eGov-Suite

eGov17872

When changing the user in the context of ELAK transactions, it is now also possible to influence the role change. There are now three options:

  • Default Role: The default role of the specified user is used. This corresponds to the current behavior and is the default if nothing is configured
  • Role with Group of Subjectarea: The Group is determined from the property COOELAK@1.1001:ou and compared with the first role of the user. This role is then used
  • Expression: An expression must be defined that has a return value of type FSCGOVXMLAT@1.1001:ELAKTransUserRoleChangeExprType

eGov17871

Low-code/No-code Configurations can now be stored in the properties under “Configurations” in Teamrooms and Rooms with User Data. Hierarchically, these configurations are linked under the Tenant of the Teamroom or Room with User Data

Custom Applications can now also be configured for the following object classes:

  • Document (COOSYSTEM@1.1:ContentObject)
  • Teamroom (FSCTEAMROOM@1.1001:TeamRoom)
  • Folder (COODESK@1.1:Folder)
  • Object with User Data (FSCUSERFORMS@1.1001:ObjectWithUserForm)
  • Container with User Data (FSCUSERFORMS@1.1001:ContainerWithUserForm)
  • Room with User Data (FSCUSERFORMS@1.1001:RoomWithUserForm)

eGov17893

The white paper for Low-code/No-code Configuration has been added

eGov17918

A bug has been fixed where, if an Application was stored in a menu in the Low-code/No-code Configuration, this Application was also displayed in the following menus

eGov17836

If a blackening is finalized that does not actually contain any blackening, the content is still converted to PDF format

eGov17911

In Applications for the Low-code/No-code Configuration, in the Low-code expression is mentioned “Enabled, if”, if the selected objects are available in the variable “objs”

eGov17842

Previously, XDOMEA imports displayed error messages that were not very informative, for example when a package was incomplete. The messages have been improved to make error analysis easier. Among other things, the error message now contains the name and address of the affected XDOMEA package (Edition DEU)

eGov17840

When performing the step “Edit Description” (“IFG - Prepare Publishing” (ATPRECONFIG@1.1001:ActDefIFGPreparations)), a lock error message could occur. This error has been fixed (Edition AUT)

Build 25.9.0.352.4-10Permanent link for this heading

Internal builds

Build 25.9.0.352.3 (September 12, 2025)Permanent link for this heading

Release