Imprint

Fabasoft eGov-Suite 2025 April Release (25.4.0)Permanent link for this heading

Build 25.4.0.284.50 (June 30, 2025)Permanent link for this heading

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.4.0.284.45-49Permanent link for this heading

Internal builds

Build 25.4.0.284.44 (June 16, 2025)Permanent link for this heading

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.4.0.284.41-43Permanent link for this heading

Internal builds

Build 25.4.0.284.40 (June 5, 2025)Permanent link for this heading

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.4.0.230.37-39Permanent link for this heading

Internal builds

Build 25.4.0.230.36 (May 22, 2025)Permanent link for this heading

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

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

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)

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

eGov17439

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

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

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)

eGov17445

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

Build 25.4.0.230.18-35Permanent link for this heading

Internal builds

Build 25.4.0.230.17 (April 11, 2025)Permanent link for this heading

Release

Download PDF

Download PDF