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:
Details:
(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
Internal builds
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:
(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)
Internal build
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
Internal builds
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)
Internal builds
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:
(Edition CCA, Edition AUT)
eGov17381
The following symbols have been restored as they are used in customer solutions:
(Edition CCA, Edition AUT, Edition CHE)
The following symbols have been restored as they are used in customer solutions:
(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)
Internal builds
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:
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
Internal builds
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:
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”
Internal builds
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
Internal builds
eGov17234
The Configurations tab (CORECONFIGEX@15.1001:PageConfigurations) is visible to users with the following Positions:
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:
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:
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
Internal builds
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
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)
Internal builds
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
Internal builds
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)
Internal builds
Release