Using Vault Data API to view DWF files in Viewer
DWF Extension in Viewer: Why the Data API Is the Recommended Approach
When working with DWF files in the Viewer, it is worth understanding the approach that was initially evaluated and the reasons behind the current recommendation.
The Vault Thin Client originally attempted to leverage the DWF extension directly within the Viewer. While this approach worked in certain scenarios, the engineering team identified challenges related to specific DWF-dependent components. As testing expanded across a broader range of datasets, these dependencies resulted in inconsistent behavior and compatibility issues for a significant number of files.
To address these challenges, the recommended approach is to use the Vault Data API.
With the Vault Data API workflow, the server is responsible for translating the file before it is consumed by the Viewer. Once the translation process is completed, the Viewer can render the resulting data more reliably. By moving the translation responsibility to the server, this approach avoids the dependency-related issues observed with the DWF extension and provides a more consistent experience across different datasets.
Key Benefits of the Vault Data API Approach
- Server-side file translation reduces dependency-related issues.
- Improved reliability when working with a wide variety of datasets.
- More consistent rendering behavior in the Viewer.
- Reduced exposure to DWF-specific extension limitations.
For these reasons, the Vault Data API remains the preferred and recommended method for rendering DWF content, particularly in environments where dataset diversity and reliability are important considerations.
For more information on Vault Data API please visit this link:
Note: Please note that the use of Vault Data API starts from 2025.2 onwards. The earlier versions of Vault are not supported
Leave a Reply