Imprint

Fabasoft eGov-Suite 2025 Update Rollup 1 (25.0.1)Permanent link for this heading

Build 25.0.1.51.80 (December 30, 2025)Permanent link for this heading

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.1.47.78-79Permanent link for this heading

Internal builds

Build 25.0.1.47.77 (December 5, 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

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.1.47.74-76Permanent link for this heading

Internal builds

Build 25.0.1.47.73 (November 5, 2025)Permanent link for this heading

eGov17770, eGov17332

For Personal and Authority Signatures, the system checks whether the attribute “Sign approval notice with content” (ATPRECONFIG@15.1001:dosigndynamicnotice) is set on the object to be signed. If so, the “Dynamic Signature Profile” is used as the profile ID instead of the configured profile ID. The “Dynamic Signature Profile” can be configured in the “Personal Signature Configuration” (Edition AUT)

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

eGov17938, eGov17745, eGov17643

The attribute “Approval notice” (ATPRECONFIG@1.1001:approvalnotice) is now evaluated in connection with the Configuration Concept (Edition AUT)

eGov18032, eGov17719

When redacting (officially) signed documents, the redaction is now applied above the signature block

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)

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)

eGov17941

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

eGov17934

When deleting objects, canceled objects (COOELAK@1.1001:cancelledobj) are now also taken into account and deleted (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.1.42.53-72Permanent link for this heading

Internal builds

Build 25.0.1.42.52 (September 16, 2025)Permanent link for this heading

eGov17864, eGov17838, eGov17725

Based on the API documentation from data.gv.at, only alphanumeric characters were previously permitted in IFG keywords. These have now been expanded to include the German characters Öö, Ää, Üü, and ß (Edition AUT)

eGov17874

Problems could occur during finalization if an official signature was applied and the rule “Execute Authority Signature” (COOELAK@1.1001:CtxAuthoritySignature) was enabled on the object class “Object”. This error has been fixed

eGov17836

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

Build 25.0.1.42.46-51Permanent link for this heading

Internal builds

Build 25.0.1.42.45 (September 2, 2025)Permanent link for this heading

eGov17821, eGov17736

When blackening out and annotating documents, an error has been fixed that occurred when the user had a different time zone set on their PC than the server

eGov17844

Blackenings can be applied using the step “Redact Documents” if the step was executed from the activity view. Previously, an error message appeared

eGov17843

With the action ATPRECONFIG@1.1001:CheckIFGDeadlines, an AT job can now be configured that automatically deletes Published Information based on the deletion date (Edition AUT)

eGov17769

The behavior from before the changeover of the Authority Signature was restored, when signing documents during the dispatch of business items (Edition AUT)

eGov17837

Problems could occur during finalization when an Authority Signature was added. The problems have been solved. Furthermore, the evaluation of the Configuration Concept has been adjusted. For documents, the property “Referenced Object” (COOSYSTEM@1.1:objaclref) is also used to evaluate the parent configurations

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

Internal builds

Build 25.0.1.42.39 (August 21, 2025)Permanent link for this heading

eGov17797

Text-based blackening of rotated text has been improved. The selection now works just as well as when blackening out non-rotated text

Build 25.0.1.42.38 (August 13, 2025)Permanent link for this heading

eGov17778

When transmitting information about resources (link to documents in data.gv.at) in the context of the Freedom of Information Act, the specified title was not used for publication, but rather the object name of the business object to be transmitted. As a result, personal data, if included in the title of the business object, was transmitted to data.gv.at

This behavior has been changed so that either the value of the property “Title for Publication” (SOLEGOVCOREIFG@111.100:ifgtitle) or the property “Refers to” (COOELAK@1.1001:referrednumber) is used for this purpose (Edition AUT)

Build 25.0.1.37.37Permanent link for this heading

Internal build

Build 25.0.1.37.36 (July 31, 2025)Permanent link for this heading

eGov17688, eGov17632

The XDOMEA export has been revised. The following XML nodes have been adapted:

  • Akte/AllgemeineMetadaten/Aktenplaneinheit/Kennzeichen, filled with the Numerical Reference Code (COOELAK@1.1001:basenr) of the Fileplan Entry
  • Akte/AllgemeineMetadaten/Kennzeichen, filled with the File Reference (COOELAK@1.1001:filereference) of the File

(Edition DEU)

Build 25.0.1.27.26-35Permanent link for this heading

Internal builds

Build 25.0.1.27.25 (July 7, 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

eGov17638

OCR conversion via Tesseract has been added. To do this, the software "Tesseract" must be used in the property “Software for OCR Transformation” in the domain

In addition, the app “Text Recognition (OCR)” must be set in the domain in the property “Licensed Apps”

Furthermore, an object of the object class “Document Transformation Service” must be created in the property “Configuration for Document Transformation Service” in the Conversion Configuration. The URL to the DTS must be entered in this object in the property “Gateway Address”

Build 25.0.1.21.16-24Permanent link for this heading

Internal builds

Build 25.0.1.21.15 (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)

eGov17584

If Business Data is configured and the Business Data property of the object is empty then the Business Data tab is also displayed if the object has been opened read-only

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.1.19.13-14Permanent link for this heading

Internal builds

Build 25.0.1.19.12 (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.0.1.17.10-11Permanent link for this heading

Internal builds

Build 25.0.1.17.9 (May 23, 2025)Permanent link for this heading

Release