Find out more about new features and improvements in Fabasoft Approve.
As a user you can expect the following new features.
Fabasoft Approve will rely on the large language model (LLM) Qwen 3.8 going forward. This will allow even extensive documents to be processed more efficiently, and AI-generated responses will be more precise and of higher quality.
AI-supported metadata extraction has been enhanced with several new features that enable more targeted and flexible information extraction.
For a metadata extraction definition, it is now possible to specify other extraction definitions from the same metadata extraction as prerequisites. This ensures that the metadata extraction process is ordered so that these prerequisite extraction definitions are executed first.
Prompts can now access the results of previous extraction definitions. To do this, metadata values that have already been determined can be referenced directly in the prompt using placeholders.
A placeholder consists of two curly braces and the short reference of the desired attribute, for example {{systemstarpointaccessible}}.
The applicability of a metadata extraction can now be controlled via an expression. For example, the GetMetadataFieldValue() function can be used to read existing metadata values and, based on this, determine whether a metadata extraction should be applied to an object.
The prompt itself can now also be generated dynamically. Using an expression, various pieces of information can be combined to create a custom prompt for the respective extraction.
The following new features await you in the correspondence management solution area.
As a user you can expect the following new features.
Quality control points can now be assigned their own status. This allows the current progress of individual control points – or across the entire lifecycle – to be directly visualized and tracked more quickly.
In addition, the process for editing multiple quality control points via the “Edit Schedule” menu has been updated. For easier handling, editing is now performed individually for each document. However, the control points can still be managed via the shared editing feature and the data available there.
You can now control the timing of reminder emails with greater flexibility. For document due dates and other objects, you can specify when a reminder is sent – before or after the due date – and how long reminders continue to be sent after the due date.
These settings can be configured at the configuration, project, or repository level. Settings at the repository level take precedence over those at the project level, which in turn take precedence over those at the configuration level.
You can customize the following:
If no custom settings are specified, the default remains in effect: The first reminder is sent 14 days before the due date, followed by a weekly reminder over a four-week period.
Important: Changes to the timing do not apply retroactively. They apply to new items and take effect after an existing reminder has been sent.
Letters can now be marked as confidential. This allows the attachments to a confidential letter to be restricted to specific users and teams.
To do this, activate the “Confidential” field on the letter. After it is sent, the letter itself and its message remains visible to users in the destination folder. However, only those users and teams listed under “Administrator” or “Full Access” in the permissions settings can view the attachments.