2025 June Release

Artificial IntelligencePermanent link for this heading

The following chapters describe the configuration options for AI-supported use cases.

Note:

Define AI ConfigurationsPermanent link for this heading

The AI configuration (cloud organization > “Advanced Settings” > “AI Settings”) is needed for following use cases:

  • Provide AI Answers

SettingsPermanent link for this heading

You can define following settings:

  • Endpoint
    Defines the endpoint of your Mindbreeze AI instance. The endpoint defines the index in which the data of the indexed objects are stored. If no endpoint is available for selection, please contact Fabasoft Cloud Support.
    Note: Define only one AI configuration per endpoint.
  • AI Indexing Configuration
    Defines the AI indexing configuration that determines the objects to be indexed (see chapter “Define AI Indexing Configurations”).
  • Index All Objects
    Specifies whether all objects (with and without solution context) are indexed (according to the AI indexing configuration).
  • Index Objects From Following Solution Contexts
    The objects in the specified solutions are indexed (according to the AI indexing configuration).
  • Index Objects Without a Solution Context
    Defines whether objects that are not in a solution context (e.g., objects in Teamrooms) should be indexed (according to the AI indexing configuration).
  • Automatic Delta Indexing
    Shows whether automatic delta indexing is enabled.
  • Automatic Delta Indexing Paused
    Shows whether automatic delta indexing is paused.
  • Endpoint State
    Shows whether the endpoint is reachable.
  • Organization
    Shows the organization for which the configuration has been defined.

ActionsPermanent link for this heading

  • Enable/Disable Delta Indexing
    Defines whether changes are transferred to the index defined in the endpoint.
    Note: If delta indexing is disabled, any changes are not logged and are therefore not reflected in the index even after enabling.
  • Continue/Pause Delta Indexing
    Defines whether changes are transferred to the index defined in the endpoint.
    Note: If delta indexing is paused, any changes are logged and are thus reflected in the index after resuming.
  • Schedule Full Indexing
    Starts a full indexing in the background.
    Note: Run the full indexing to index existing objects. A full indexing is also useful if you have made changes to the AI configuration or AI indexing configuration.
  • Define as Default
    If no AI configuration has been explicitly defined in AI use cases, the default configuration is used. The action is only available for non-default configurations. The first AI configuration created is automatically set as the default.

Note:

  • AI configurations created in a room/app configuration context do not allow full indexing and cannot be defined as default.
  • For app configurations, app rooms, and Teamrooms, the “Tools” > “Index in Background” context menu command is available for users with full control if an AI configuration exists. You can select the desired AI configurations for indexing and define whether you want to be notified by e-mail when indexing is complete. While indexing is in progress, the “Tools” > “Display Indexing Status” context menu command is available.

Define Insight App MappingsPermanent link for this heading

The AI configuration to be used can be specified in the properties of insight apps. If no AI configuration is specified, a mapping can be specified using the “Define Insight App Mappings” action. If also no insight app mapping is defined, the AI configuration defined as default is used.

If necessary, define the insight app mappings in your organization under “Advanced Settings” > “AI Settings” (action “Define Insight App Mappings”):

  • Insight App
    Select the desired Insight app (e.g., “AI Answers App”).
  • AI Configuration
    Defines the AI configuration to be used. The endpoint and thus the index to be used are determined from the AI configuration.

Note: The setting can also be made at room/app configuration level in the properties (“AI Settings” tab).

Evaluation logic:

  • If no entry is found at room level, an entry is determined at app configuration level (if present).
  • If no entry is found at room/app configuration level, an entry is determined at organization level.
  • If no applicable entry is found at organization level either, the AI configuration defined as default is used.
  • The following applies to AI Answers: If there is also no default configuration (with defined AI indexing configuration), the AI Answers actions are not displayed.

Define AI Indexing ConfigurationsPermanent link for this heading

You can use the AI indexing configuration (cloud organization > “Advanced Settings” > “AI Settings”) to define which objects are to be indexed.

Note: The desired AI indexing configuration must be entered in the corresponding AI configuration.

  • Indexing Settings
    Defines the object classes or object aspects that are to be used for indexing (e.g., “Microsoft Word Document”). The object class hierarchy is taken into account (e.g., if “Document” is selected, all content objects are indexed).
    • If a category (release version) is also specified, only objects that have both the object class/object aspect and the category (draft or release version) are indexed.
    • If AI entity definitions are also specified, these are taken into account during indexing (see chapter “Define AI Entity Definitions”).
  • Additional AI Indexing Configurations
    The indexing settings of the specified AI indexing configurations are also taken into account (including the entire configuration hierarchy).

Note: All matching entries in the entire AI indexing configuration hierarchy are considered. For example, if the AI entity definitions “Ent1” and “Ent2” are defined for “Microsoft Word Document” and the AI entity definition “Ent3” is defined for “Document,” all three AI entity definitions are taken into account for Microsoft Word documents, and the AI entity definition “Ent3” is taken into account for Microsoft Excel worksheets (since it is derived from “Document”).

Define AI Entity DefinitionsPermanent link for this heading

AI entity definitions are used to provide solution-specific AI functionality. For more information, see the documentation for the respective solution.

Configuration LevelsPermanent link for this heading

AI configurations, AI indexing configurations and AI entity definitions can be defined at the following levels:

  • organization (“Advanced Settings” > “AI Settings”)
    Applies to objects that are assigned to the organization.
  • app configuration (“AI Settings”)
    Applies to app rooms and the objects they contain that are assigned to the app configuration.
  • Teamroom/app room (“Templates and Presettings” > “AI Settings”)
    Applies to objects that are assigned to the Teamroom or app room.

AI configurations are evaluated in the context in which they are stored. Make sure that the Index Objects From Following Solution Contexts field is defined for the respective context if you have not enabled Index All Objects. You can also store the same AI configuration in different contexts so that you do not have to define the settings multiple times.

Provide AI AnswersPermanent link for this heading

Mindbreeze AI's generative AI can be used to answer questions about documents, files and Teamrooms.

To use this functionality, you need:

  • An AI configuration with a defined AI indexing configuration (see chapter “Define AI Configurations”).
  • If necessary, an Insight app mapping for the “AI Answers App” (if you do not want to use the default AI configuration).
  • The enabling of “Ask Questions” in the respective context.
    The Show “Ask Questions” Action by Default option can be enabled in the organization policies (“Actions” tab) or in the properties of a Teamroom (“AI Settings” tab). If nothing is defined at Teamroom level, the organization setting is used.

Provide AI ClassificationPermanent link for this heading

AI services can be used, for example, to classify documents automatically. Navigate in the AI Services to create additional services. If only one service is available, it is automatically the default service. If multiple services are available, a service can be set as default service by using the “Set as Default” context menu command. The default service is used if no service has been explicitly defined in the respective context (the fallback does not apply to an app room context).

You can define the following settings:

  • Name
    The name of the service.
  • Filter Service URL
    The URL to the AI filter service (e.g. https://mbinspire.example.com:8443/filter/23401).
  • Tenant
    The AI prediction service is multi-tenant capable. If a tenant is defined, it will be used.
    Note: In the Mindbreeze Management Center, the Tenant ID Pattern property must have the following value: {{_FSCMINDBREEZE_1_1001_fscmbtenant}}
  • Project
    Within a tenant several projects can be managed. If a project is defined, it will be used.
    Note: In the Mindbreeze Management Center, the Project ID Pattern property must have the following value: {{_FSCMINDBREEZE_1_1001_fscmbproject}}
  • Scope
    Within a project several scopes can be managed. If a scope is defined, the corresponding model will be used. Otherwise, the default model is used.
    Note: In the Mindbreeze Management Center, the Scope ID Pattern property must have the following value: {{_FSCMINDBREEZE_1_1001_fscmbscope}}
  • Authentication
    Defines the authentication type for the filter service.
  • Root and Intermediate Certificate Authorities
    Defines the root and intermediate certificate authorities for the validation of the SSL server certificates of the filter service.
  • Send Feedback to AI Service
    Defines whether feedback about the correctness of the classification will be sent to the AI service. This can improve the future classification.
  • Own AI Service for Feedbacks
    Defines whether the feedback will be sent to a dedicated AI service. If enabled, the data (Filter Service URL, Tenant, Project, Scope, Authentication) can be specified for the dedicated AI service.
  • Own AI Service for Training Data
    Defines whether the training data will be sent to a dedicated AI service. If enabled, the data (Filter Service URL, Tenant, Project, Scope, Authentication) can be specified for the dedicated AI service.
  • Software Component Prefixes for the Mapping of Fabasoft Cloud Keys
    If no full reference is specified in the Key Mapping field, the system attempts to determine the property using the software components specified here (e.g. COOTC@1.1001).
  • Key Mapping
    If the keys defined in Mindbreeze AI do not correspond to the keys in the Fabasoft Cloud, a mapping can be defined. As key in the Fabasoft Cloud the reference of the respective property is used (e.g. COOTC_1_1001_objcategory for the Category property). In the case of user-defined forms the programming name of the property is used as key.
    When using short references (e.g. objcategory), the corresponding software component must be specified in the Software Component Prefixes for the Mapping of Fabasoft Cloud Keys field.

If necessary, contact Fabasoft Cloud Support (cloudsupport@fabasoft.com: new window) to make the specific settings.

Download PDF

Download PDF