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
eGov18117, 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)
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 :
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)
eGov18049
The Java library CXF-Core has been upgraded from version 3.5.11 to version 3.6.8 (Edition DEU)
eGov18299
A CSV migration has been added for the following properties in the “PrimeSign Personal Signature Configuration”:
Internal builds
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
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)
Internal builds
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)
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
eGov17797
Text-based blackening of rotated text has been improved. The selection now works just as well as when blackening out non-rotated text
Internal builds
eGov17745, eGov17643
The attribute “Approval notice” (ATPRECONFIG@1.1001:approvalnotice) is now evaluated in connection with the Configuration Concept (Edition AUT)
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)
eGov17741
OCR conversion via Tesseract has been added. To use this feature, the software “Tesseract” must be set in the property “Software for OCR Transformation” in the domain
In addition, the App “Text Recognition (OCR)” must be stored in the domain in the property “Licensed Apps”
Furthermore, an Object of the Object Class “Document Transformation Service” must bei stored in the Conversion Configuration in the property “Configuration for Document Transformation Service”. In this object, the URL to the DTS must be entered in the property “Gateway Address”
An email address must be stored in the service user that is used for the conversion
eGov17771
Redactions can be applied using the Work Item “Redact Documents” if the Work Item was executed from the activity view. Previously, an error message appeared
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)
Internal builds
eGov17685
Redactions can be applied when in a property form
eGov17688, eGov17632
The XDOMEA export has been revised. The following XML nodes have been adapted:
(Edition DEU)
Internal builds
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 builds
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
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
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:
(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)
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)
Internal builds
Release