Fabasoft eGov-Suite 2025 (25.0.0)

Build 25.0.0.302.136 (June 27, 2025)

eGov17551

The connection to the SZR has been implemented. This connection must be configured using a “Austrian Register Services Configuration”. If the connection is configured, the “bereichsspezifische Personenkennzeichen (bPK)” of a person can be queried using an action. If the query is successful, this bPK is stored on the person object in the attribute “Area-Specific Personal Identifier” (FSCSZRINT@15.1001:bpkbpk)

In addition, the property “bPK available for” (FSCSZRINT@15.1001:bpkavailable) was created. The property shows whether a area-specific personal identifier exists for the person or the addressee

The new action FSCSZRINT@15.1001:GetAndStoreBpk is used to subsequently query and save area-specific personal identifiers. The action is called up directly on the object intended for the query. That means: If an individual person is to be queried, the action is applied directly to this person. If, on the other hand, all addressees of a business object are to be queried, the action is called up directly on the business object

If an error occurs when the SZR is called up, a technical event is saved on the object

The following changes were made as part of the SZR implementation:

• Extension of the ZMR query process: The query of the area-specific personal identifier (bPK) was integrated into the ZMR query process. This bPK is used for the duplicate check and the unique identifiability of person objects
• Extending SOAP actions: With the SOAP actions “SOAPCreateSubFile” and “SOAPCreateFile”, the addressee filling can be carried out using an area-specific personal identifier (bPK). To do this, the a new node must be defined in the addressee node. This node is used to search for an existing person in the system using the combination of the character string and the Proceedingarea. If a person is found, this person is used as the addressee and the free text fields are automatically filled in with the data of the associated person object

Details:

• If a bPK node is included in the SOAP request, but the business object is not included in a file hierarchy, an error message is issued
• A bPK node must always contain both a Proceedingarea and the bPK-string. If only one of the two is filled, an error message is generated
• If a person is found in the system via the bPK node, initialization is based on the person object found. All other free text values from the addressee node of the SOAP request are ignored
• If a bPK node is filled but no suitable person is found in the system, the addressee lines are created from the remaining free text values of the addressee node
• If a person cannot be found using the transmitted area-specific personal identifier, the area-specific personal identifier is written to the free text property

(Edition AUT)

eGov17600

The icon for freehand highlighting when annotating has been added again

eGov17386

When calling web services via the Fabasoft Protocol Manager (FSCPROTOCOLMANAGER@15.1001), the proxy is now also set via the HTTP header variable “Add information on basic authentication as Authorization to the HTTP header” (FSCPROTOCOLMANAGER@15.1001:basicauthorizationasheadervariable). Previously, this was not the case and the proxy could use the wrong login information for authentication

eGov17594

Text-based blackening is now blackened more generously. As a result, no artifacts should remain visible even with high characters such as Ü or  from certain fonts. Due to the more generous application, certain font, font size and line break combinations may result in parts of characters above/below/next to them being (partially) blacked out. In such cases, the rectangular mode should be used for blackening

Build 25.0.0.302.131-135

Internal builds

Build 25.0.0.302.130 (June 16, 2025)

eGov17585

The new attribute “Tags” (SOLEGOVCOREIFG@111.100:ifgtags) whose values are transmitted to data.gv.at in the node “tags” has been added (Edition AUT)

eGov17492

The following points were adjusted during the implementation of the IFG:

• The attribute “Categories” (SOLEGOVCOREIFG@111.100:ifgcategories) was added, which supports the category according to the EU: http://publications.europa.eu/resource/authority/data-theme. This attribute must be filled in when defining the metadata for the publication
• The following settings have been added to the configuration:
  • Licenses can be created with own objects of the object class “License (IFG)” (SOLEGOVCOREIFG@111.100:IFGLicense) or made available for with “License (IFG) Component Object” (SOLEGOVCOREIFG@111.100:IFGLicenseComponentObject) and set in the attribute “License” (SOLEGOVCOREIFG@111.100:ifglicense) of the configuration
  • A “Publishing Organisation” (SOLEGOVCOREIFG@111.100:ifgpublishingorganisation) can be configured in the configuration. If this is configured, it is transferred to data.gv.at. If nothing is configured, either the “Responsible Organization” or the property “Ownergroup” is used
• The Business Number is added to the title for data.gv.at if it is not already defined. The title can now be freely defined
• When copying documents when creating the Teamroom, the property “Category” (COOTC@1.1001:objcategory) is now also removed

(Edition AUT)

eGov17454

When configuring and transferring a dataset to data.gv.at, the field “Postfix for Attribute "name"” (SOLEGOVCOREIFG@111.100:ifgnamepostfix) was implemented. The string stored here is added to the end of the Business Number and used for the technical attribute “name” in data.gv.at. In addition, the title is now also transferred in order to create a separation here in the data record. The reason for this measure was that the “name” must be globally unique on data.gv.at. Due to the standardization of the Business Numbers in the customer installations, an additional key had to be inserted, which can now be configured (Edition AUT)

Build 25.0.0.302.129

Internal build

Build 25.0.0.302.128 (June 5, 2025)

eGov17536

In order to avoid the possibility that, if documents are redacted without first removing the text, this text, which would then only be overwritten, could be made partially visible again through manipulation, a change was made to the Fabasoft eGov-Suite

At the same time, we have made a tool available that can be used to identify potentially affected data and clean it up if necessary. The tools can be obtained from Fabasoft Support if required

eGov17459

A display error in the Signature Client when using certain iOS versions has been fixed

eGov17479, eGov17350

If redactions are applied to PDFs whose content is rotated by a multiple of 90°, this is taken into account when finalizing the redaction

Build 25.0.0.302.126-127

Internal builds

Build 25.0.0.302.125 (May 22, 2025)

eGov17436

In the PDF preview, the first two links per page were not clickable. This problem has been fixed

eGov17439

If a redacted document is published, the redaction is finalized and from now on also OCR converted if an OCR service is stored

eGov17445

The Java library CXF Core has been updated from version 3.3.2 to 3.5.11 (Edition DEU)

Build 25.0.0.302.123-124

Internal builds

Build 25.0.0.302.122 (May 14, 2025)

eGov17379

An error occurred when creating Business Objects via the SOAP interface, when addressees were defined. The problem has been fixed (Edition CCA, Edition DEU, Edition CHE)

eGov17374

The following adjustments were made for the IFG implementation:

• After the metadata has been withdrawn, the properties “Description for Publication” (SOLEGOVCOREIFG@111.100:ifgdescription) and the deadline “Delete Publication (IFG)” are deleted
• When creating the Teamroom for the documents, the owner of the File is added to the property “Full Control” (COOSYSTEM@1.1:objsecsecurity). The “Responsible Organization” (COOELAK@1.1001:fileresporg) and “Group” (COOSYSTEM@1.1:objowngroup) are added to the property “Read Access” (COOSYSTEM@1.1:objsecread)
• The signatures “IFG – Publishing Prepared” (ATPRECONFIG@1.1001:SIGN_IFG_PREPARED) , “IFG – Publishing Executed” (ATPRECONFIG@1.1001:SIGN_IFG_PUBLISHED) , “IFG – Publishing Denied” (ATPRECONFIG@1.1001:SIGN_IFG_DENY_PUBLISHING) and “IFG - Back to Rework” (ATPRECONFIG@1.1001:SIGN_IFG_REWORK_PUBLISHING) now check as a precondition whether an IFG configuration is activated

(Edition CCA, Edition AUT)

eGov17381

The following symbols have been restored as they are used in customer solutions:

• EGOVDESK@15.1001:UISymbolPlusGrey
• EGOVDESK@15.1001:SymbolSearchSubjectAreaFile
• EGOVDESK@15.1001:SymbolRecordFilledYellow
• EGOVDESK@15.1001:SymbolFileWorld
• EGOVDESK@15.1001:SymbolDocumentBubble
• EGOVDESK@15.1001:SymbolFolderYellow
• EGOVDESK@15.1001:SymbolDocumentFolderYellow
• EGOVDESK@15.1001:SymbolRecordFolderYellowFull
• EGOVDESK@15.1001:SymbolTeamRoomCycle
• EGOVDESK@15.1001:SymbolAppTransferTeamRoomFullFramed
• EGOVDESK@15.1001:SymbolWordOnlineEdit
• EGOVDESK@15.1001:SymbolExcelOnlineEdit
• EGOVDESK@15.1001:SymbolPowerPointOnlineEdit

(Edition CCA, Edition AUT, Edition CHE)

The following symbols have been restored as they are used in customer solutions:

• EGOVDESK@15.1001:UISymbolPlusGrey
• EGOVDESK@15.1001:SymbolSearchSubjectAreaFile
• EGOVDESK@15.1001:SymbolRecordFilledYellow
• EGOVDESK@15.1001:SymbolFileWorld
• EGOVDESK@15.1001:SymbolDocumentBubble
• EGOVDESK@15.1001:SymbolFolderYellow
• EGOVDESK@15.1001:SymbolDocumentFolderYellow
• EGOVDESK@15.1001:SymbolRecordFolderYellowFull
• EGOVDESK@15.1001:SymbolTeamRoomCycle
• EGOVDESK@15.1001:SymbolAppTransferTeamRoomFullFramed
• EGOVDESK@15.1001:SymbolWordOnlineEdit
• EGOVDESK@15.1001:SymbolExcelOnlineEdit
• EGOVDESK@15.1001:SymbolPowerPointOnlineEdit
• EGOVDESKDE@15.1001:SymbolPaperProcedure

(Edition DE)

eGov17398

An error with the actions “IFG - Withdraw Published Metadata” (SOLEGOVCOREIFG@111.100:MenuIFGRevokePublishing) and “IFG – Withdraw Published Documents” (SOLEGOVCOREIFG@111.100:MenuIFGRevokeDocumentPublishing) has been fixed. The actions are now working correctly again (Edition AUT)a

eGov17353

If a Document was deposit independently of the File and the File was later deposit and disposed, the property “Document State” (FSCFOLIO@1.1001:objdocstate) of the Business Object is now also correctly set to “Archived” (DS_ARCHIVED) (Edition CCA, Edition AUT)

Build 25.0.0.288.109-121

Internal builds

Build 25.0.0.288.108 (April 16, 2025)

eGov17351

An error has been fixed in the Personal Signature Configuration and the Authority Signature where the evaluation of the profile ID from the configuration concept was incorrect

eGov17349

The object classes for the configuration concept can be searched for at the Desk from the following Positions and used in the Search Form:

• System Administration
• Administration
• File Plan Administrator
• Department Administrator

eGov17358, eGov17337

The first name is also added to salutations

eGov17369

The Profile ID for signing with a Dynamic Stamp is now also provided for individual documents

eGov17228

The value of the DocProperty Addressees (CCAPRECONFIG@15.1001:ObjectAddressees) is displayed in multiple lines under Linux. Previously, this was incorrectly not the case

eGov17329

If the “Import Conflicts” dialogue appeared during import (which means a document with the same name already exists), it could happen that the existing document was deleted if an error occurred when replacing or skipping. The problem has been fixed

Build 25.0.0.288.100-107

Internal builds

Build 25.0.0.288.99 (April 11, 2025)

eGov17328

When moving Business Objects using the Move button of a Signature Folder, a check is made to ensure that the Business Object being moved is not in either of the two signature folder lists. Only in this case is the Signature Folder removed from the property of the moved Business Object

eGov17176

For the SOAP actions “SOAPCreateSubFile” and “SOAPCreateFile”, the addressee can be filled using an Area-Specific Personal Identifier (bPK). To do this, a new node must be defined in the addressee node. This node is used to search for an existing person in the system using the combination of the character string and the Proceedingarea. If a person is found, this person is used as the addressee and the free text fields are automatically filled in with the data of the associated “Person” object (Edition CCA, Edition AUT)

eGov17324

In the ELAK transactions, a "ReferencedIdentifier" node, which contains an empty "Identification" node, is included in the outer metadata node. This is required according to the schema (Edition AUT)

eGov17333, eGov17312

The complete desktop annotation tools were offered on certain Apple iPads. Now only those are offered that are also supported on mobile devices

eGov17300

The following extensions were implemented to support the implementation of the Freedom of Information Act:

• Creation of the new white paper “Konfiguration und Anpassung der IFG Implementierung”
• Implementation of the new activities including signatures and use cases for mapping of IFG publication in the Fabasoft eGov Suite:
  • IFG - Publish Documents (ATPRECONFIG@1.1001:ActDefIFGPublishDocuments)
  • IFG - Publish Metadata (ATPRECONFIG@1.1001:ActDefIFGPublishObject)
  • IFG - Prepare Publishing (ATPRECONFIG@1.1001:ActDefIFGPreparations)
  • IFG – Approve Publishing (ATPRECONFIG@1.1001:ActDefIFGApproval)
• Excluding object classes for document selection via a Customization Point
• IFG context menus are now only displayed on the File
• Renaming the context menu entries:
  • Publish (IFG) to IFG - Publish Metadata
  • Publish Documents (IFG) to IFG - Publish Documents
• Creation of use cases and menus for deleting publications for metadata and documents
  • IFG - Withdraw Published Metadata
  • IFG - Withdraw Published Documents
• Implementation of preconditions for the 4 IFG menus
• During Disposal the publication is, controllable via the configuration, also automatically withdrawn
• The published documents are displayed on the IFG tabxxx

eGov17277

The property “bPK available” (FSCSZRINT@15.1001:bpkavailable) has been created. The property shows whether an Area Specific Personal Identifier exists for the person or the addressee (Edition AUT)

Note: The property “Area-Specific Personal Identifier” (FSCZMRINT@15.1001:bpkbpk) has been moved from the software component "FSCZMRINT" to the software component "FSCSZRINT”

Build 25.0.0.274.87-98

Internal builds

Build 25.0.0.274.86 (March 26, 2025)

eGov17245

A race condition during personal signing with PrimeSign has been fixed

eGov17276

The Version Number for Software Products has been changed to 250000

eGov17303

When exporting e-mail addresses, the Identification Node in the XML is no longer generated in the context of the ELAK transactions, as this is not contained in the PersonData of the ELAK transactions (Edition AUT)

eGov17146

The fonts for generating PDF reports have been adapted and NotoSans is now used instead of Arial

If unsupported characters are detected during generation, the cell is filled with (Not supported charset)

eGov17295

In the ELAK transactions, an Identification Node is included in the outer metadata node. This is required according to the schema (Edition AUT)

eGov17309

Modified (e.g. moved) annotations displayed ‘Invalid Date’ as the modification time when hovering the annotation. The correct modification time is now displayed

eGov17298

An error when receiving messages from Governikus Multimessenger has been fixed. The error occurred under Linux when PDF documents were sent in certain versions (Edition DEU)

eGov17299

When deleting blackenings, it is no longer possible to open the context menu for a blackening when selecting a blackening. As the metadata and other functions of a blackening are not relevant for the end user here, the context menu has been deactivated

Build 25.0.0.268.68-85

Internal builds

Build 25.0.0.268.67 (March 7, 2025)

eGov17234

The Configurations tab (CORECONFIGEX@15.1001:PageConfigurations) is visible to users with the following Positions:

• System Administration
• Administration
• File Plan Administrator
• Department Administrator

eGov17238

In a HTTP Connector Configuration, an object of the object class “”PKCS #12” Certificate" can also be created in the property “Client Certificate”

eGov17200

The WSDL for the SOAP connection to the eGov Suite has been corrected

eGov17205

When FInalizing Subfile Documents containing Mail Merge that are to be Authority Signed, the Configuration Concept is evaluated for the correct object

eGov17221

The following obsolete properties are displayed again:

• Endpoint for PrimeSign Signature (FSCPRIMESIGN@15.1001:primesignendpoint)
• Parameters for dynamic stamp (PrimeSign) (FSCPRIMESIGN@15.1001:primesigndynamicstampmapping)
• Sigantureprofile (DLVDUAL@15.1001:signatureprofile)
• Signature profile with dynamic text (DLVDUAL@15.1001:dynamicsignatureprofile)
• Endpoint for authoritysignature (DLVDUAL@15.1001:hpcsignendpoint)

The properties are obsolete and are only shown to make it easier to transfer data to the new configuration option (Edition CCA, Edition AUT)

eGov17270

A problem when editing configuration of a user has been fixed

eGov17037

The object class “Configurationtemplatecollection” (CORECONFIGEX@15.1001:ConfigCollection) can be created on the desktop and is used to create configuration templates. Default settings can be made in these and stored in objects of the Configuration Concept

The new object class is available for the following Positions:

• System Administration
• Administration
• File Plan Administrator
• Department Administrator

eGov17232

An error has been corrected in the Dynamic Stamps in the PrimeSign configuration

eGov17253

An endless loop that occurs when a Document (e.g. Outgoing) and a Subfile Collection have the same Subfile Type has been fixed

eGov17250

Evaluation of the new Configuration Concept: If no Fileplan or higher-level Subject Area is assigned to a Subject Area, the objdomain of the Subject Area is used

Build 25.0.0.245.38-66

Internal builds

Build 25.0.0.245.37 (February 12, 2025)

eGov17202

Evaluation of the new configurations: If no Fileplan or higher-level Subject Area is assigned to a Subject Area, the objdomain of the Subject Area is used

Build 25.0.0.245.36 (February 10, 2025)

eGov17177

The updated White Paper ‘Configuration of PrimeSign’ with the description of the PrimeSign integration of the component SOLEGOVCOREPRIMESIGN is now also available in the hotfix

The upgrade document for the Fabasoft eGov-Suite 2025 version has been added

eGov17162

An error in Return Receipt processing (DeliveryRequestStatusType) via Vendo has been fixed and now works correctly (Edition CCA, Edition AUT)

Build 25.0.0.225.28-35

Internal builds

Build 25.0.0.225.27 (January 28, 2025)

eGov17163

The selection of the printer when printing after dispatch has been optimised. Previously, the printer had to be selected for each document to be printed. This has been improved so that the printer only needs to be selected once

An error when printing via the print icon in the viewer has been fixed

Build 25.0.0.225.25-26

Internal builds

Build 25.0.0.225.24 (January 23, 2025)

eGov17160

Following the removal of the Business Data, the chapter on Business Data was removed from the white paper “Use cases zur Fachanwendungsintegration in der Fabasoft eGov-Suite”

eGov17076

The Stamp tool for annotating is now also available on mobile devices

eGov17096

When calling up the parent object via the context menu, the current role of the user is now also specified. This means that the new window is also opened in the correct role and behaves in the same way as in the original window (Edition CCA)

Build 25.0.0.208.19-23

Internal builds

Build 25.0.0.208.18 (January 10, 2025)

Release