Unsupported cases

The following section outlines cases where the OfficeClient functionality is either not supported or subject to limitations. These restrictions apply to specific document types, file formats, or attribute configurations and must be considered when configuring or using the system:

  • Password-protected Microsoft Office documents are not supported by the OfficeClient.

  • Only XML-based Office documents are supported (e.g. “.docx” and “.docm” etc.). The add-in is disabled for other types like “.doc”, “.rtf” or “.odt”.

  • If autoindexing is configured for Microsoft Outlook .eml file types, these cannot be used in combination with OfficeClient in Microsoft Word or Excel.

Attribute type limitations for “Save as new” in the OfficeClient

For the OfficeClient functionality “Save as new” only basic attribute types are fully supported:

  • string

  • decimal

  • boolean

  • date / dateTime

Other attribute types, which are not fully supported in an Office document type, are also considered as “non-basic”, and usage conditions apply:

  • For attributes of non-basic types, no value can be set directly in the Office application.

  • Consequently, in an Office document type, attributes of non-basic types must be optional.

  • If any non-basic attribute type is declared as mandatory in an Office document type, “Save as new” from Office will fail because no value can be set or changed for such an attribute type directly in Office.

It is still possible to handle non-basic attribute types directly in the ImageMaster WorkplaceClient, and to open such a document type from Office via “Open in ImageMaster”, so its attribute values can then be edited in the ImageMaster WorkplaceClient, where attributes of all types are supported.

Note:

This requirement is not detected automatically when attribute types are set up. In scenarios like the following the system won’t be able to automatically reject unsupported constellations:

  • At the time of the creation of a document type (in the AdminClient or via the Admin web service), when attributes are added to a document type or if existing attribute definitions are changed, it is still possible to violate this rule, and to declare a non-basic attribute type as mandatory.

    An administrator must be aware of this and avoid this!

  • If you upgrade from a previous ImageMaster release and want to use the OfficeClient for the first time on an existing document type, document types that violate this rule can already exist.

    In this scenario, if you want to use an existing document type in Office, check whether any non-basic attribute type is mandatory. If so, the mandatory condition must be reconsidered.