Knowledge Discovery 26.3.0
26.3 Release Notes

# View Component

View Component is an ACI server. For details of changes that affect all ACI servers, see ACI Server Framework.

## 26.3.0

There were no new features or resolved issues in this release.

## 26.2.0

There were no new features or resolved issues in this release.

## 26.1.0

There were no new features or resolved issues in this release.

## 25.4.0

There were no new features or resolved issues in this release.

## 25.3.0

### New Features

- The `UniversalViewing` configuration parameters `ConnectorGroupField`, `DistributedConnectorReferenceField`, `WebURLField` and `FileSystemReferenceField` now support nested field structures when searching the Content response for the field values, by separating field names with a forward slash (/). For example, you can set `ConnectorGroupField=GROUPS/CONNECTOR` to find the field value in the following XML:

      <GROUPS>
         <CONNECTOR>MyConnectorGroup</CONNECTOR>
      </GROUPS>

- You can now configure View in universal viewing mode to retrieve document information from a particular field in the Content component index if the connector fails to return the original document. To use this option, set the new `FallbackContentField` parameter to the field name in the `UniversalViewing` configuration section. By default, it uses the `DRECONTENT` field. The parameter also supports nested field structures.

- View has been updated to allow it to fetch documents from NiFi or a DistributedConnector that is protected by OEM licensing.

### Resolved Issues

- When a secure document was added to the View internal cache after viewing with a valid SecurityInfo string, these documents could be subsequently viewed by later requests that did not have a valid SecurityInfo string.

  View now enforces that a valid SecurityInfo string is provided when retrieving secure documents from the cache.

## 25.2.0

### New Features

- View can now read an AES key for data encryption directly from the new `AESKey` configuration parameter in the `[DataEncryption]` section. Previously, it was only possible to read an AES key file from disk (configured with `AESKeyFile`).

  You can use this option to import a key directly from a secret source, such as an environment variable or HashiCorp® Vault. The key protects access to your encrypted data, so OpenText strongly recommends that you do not to supply it as a plain text configuration value. Setting a plain text value returns a configuration validation error, but does not prevent the server from starting up.

- View has been updated to enable it to use NiFi-2 for connector communications.

### Resolved Issues

- The `ProxyPassword` configuration parameter in the `[Viewing]` section accepted only plain text passwords. You can now encrypt this password with the autpassword command-line tool in the same way as for other passwords. Refer to the Knowledge Discovery Administration Guide. to be encrypted (previously, they would only accept this parameter as plain text).

- When on-disk data encryption was enabled, a viewing request with `OutputType` set to `Raw` could return an incorrect value in the Content-Length: HTTP header field.

## 25.1.0

### New Features

There were no new features in this release.

### Resolved Issues

- A View request with highlighting and `Boolean` set to False could fail if the highlight text consisted entirely of non-ASCII characters.

- When using Universal Viewing, retrieving metadata for documents with a large number of sections could be overly slow (possibly causing timeout errors, in the worst case).

## 24.4.0

There were no new features or resolved issues in this release.

## 24.3.0

### New Features

- When you request a raw file (`OutputType` set to raw), View Server now respects the HTTP `Range:` header on the request, and returns a Partial Content (HTTP status 206) response. This change can improve the viewing of video files served from View server.

### Resolved Issues

- View was unable to retrieve certain binary files from NiFi or Distributed Connector when `OutputType` was set to raw.

## 24.2.0

### New Features

There were no new features in this release.

### Resolved Issues

- In the default rendering mode (that is, when `LegacyRendering` was turned off), multibyte Unicode characters were sometimes displayed incorrectly.

## 24.1.0

### New Features

- Two new KeyView options have been added as View configuration parameters to allow you to more easily set the output format for vector and rasterized embedded graphics:

  - `OutputVectorGraphicType`

  - `OutputRasterGraphicType`

  For a full list of available options, refer to the IDOL View Component Help.

  NOTE: These configuration parameters are not available when you set `LegacyRendering` to True. However, you can use the associated KeyView options in a Viewing template, including the new `KVGFX_SVG` option.

### Resolved Issues

- Some `View` actions failed with a HTTP 400 error when the URL returned a redirect response with a #anchor URL fragment.

## 23.4.0

There were no new features or resolved issues in this release.

## 23.3.0

There were no new features or resolved issues in this release.

## 23.2.0

### New Features

There were no new features in this release.

### Resolved Issues

- When using a Memcached cache and page restrictions, View sometimes returned the wrong page.

Copyright 2026 Open Text
Version 26.3.0 | Last updated July 2026

Send documentation feedback

Close

Send documentation feedback

To send feedback using your default email client, open an email window.

Otherwise, send your feedback and the information below to MFI-swpdl.idoldocsfeedback@opentext.com.

We appreciate your feedback!

Product: Knowledge Discovery 26.3.0

Topic Title: View Component