Fabasphere AI Core 2026 March Release

Find out more about new features and improvements in the Fabasphere AI Core (available from March 2, 2026).

Users

As an end user you can expect the following new features.

• Microsoft Windows 11 (ARM64) is supported as client platform.
• If you want to define a different right context for a folder, you can use the “Tools” > ‘Convert to “Teamroom”’ context menu command to convert a folder to a Teamroom. Conversely, you can also convert a Teamroom located in another Teamroom into a folder.
  To perform the conversion, no objects in the entire hierarchy may be locked. If an object is locked, a dialog is shown in which you can either undo the changes or continue in the background. If you continue in the background, a background task will attempt to perform the conversion within the next few hours. You can see the status (e.g., Try conversion Until (UTC)) in the folder properties on the “Conversion” tab in the conversion object. If the conversion is unsuccessful, the folder is automatically restored after the attempt period has expired. To cancel the conversion manually, you can execute the “Tools” > “Restore Folder” context menu command.
  If, for example, there is a high probability that an object is locked in very large structures, you can start the conversion directly in the background (“Tools” > “Plan Conversion” context menu command). Here you can specify the period during which the conversion should be attempted (e.g., on the weekend).
• The new “Reporting User” role is available in the service desk configuration. In addition to app administrators, reporting users can create and view support reports.
• The support coordinator team is selected based on the context in which the support request is submitted. If no support coordinator team is defined in the current context, the hierarchy (app room > app configuration > organization or Teamroom hierarchy > organization) is taken into account to determine a support coordinator team. The support coordinator team of the organization associated with the context is also authorized.
  If the support request is submitted without context, the support coordinator team of the user's managing organization is authorized.
• Default processes can be defined for Teamrooms and app rooms on the “Default Values” tab. The Default Thesaurus for New Terms field can now also be found on the “Default Values” tab of Teamrooms.
• In contact management, business partner roles can be assigned to contacts. Company codes can in turn be assigned to business partner roles.
• The contact management web service also provides the UpdateContactSAP operation. The operation differs from UpdateContact as it offers the following additional options for defining the data:
  • Countries can be defined with “ISO 3166-1 alpha-2” notation.
  • Time zones can be defined by the time zone ID of the time zone object.
  • Industries can be defined by the name of the term object.
• The Show Background Images in Dashboards and Home accessibility setting is also considered for search results.
• The accessibility of the drag-and-drop import area has been improved.
• Headings in context-sensitive help are identified as headings with aria-level="4".
• The calendar allows individual widgets to be shown or hidden.
• The term “Passwords for Applications” has been changed to “API Tokens”.
• In the Restrict “Ask questions” to field, you can also define Teamrooms and folders that are not assigned to the current Teamroom. This means that questions can be asked across Teamrooms. “Ask questions” must be enabled in all affected Teamrooms.
  If a restriction is defined, only documents that are stored directly in the specified folders or Teamrooms are taken into account. Subfolders are ignored.
• For an insight app that is displayed as an action, you can specify whether the insight app should also be displayed on the “Insight Apps” tab (“Usage” tab > Show Only as Action).
• The conference management is no longer available.

Administrators

As an administrator you can expect the following new features.

• If the Automatically Terminate Membership of Inactive External Members After policy is defined, affected users will be notified in advance by e-mail (three e-mails at two-week intervals prior to automatic termination). This gives users the opportunity to log in if necessary to prevent their membership from being terminated.