Product Sunsetting. Effective May 29, 2026, all maintenance and support for the VDE Product Line is discontinued; including VDE, VDE+Images, ImagEntry, and LifeWorks.
Existing ImagEntry accounts with active maintenance are eligible to receive a Permanent License Code. By requesting this code, you acknowledge that all associated maintenance and support services end effective May 29, 2026.
Permanent license keys will be available at no cost for six months following that date.
Would you like to access the online or pdf documentation for ImagEntry or your other licensed products? You can do that here.
Product Sunsetting. Effective May 29, 2026, Phoenix Software will transition Viking products to limited support. After this date, established customers will retain access only to the following:
All requests related to this limited support must be submitted through the Phoenix Support Portal using the Create a Case function. Requests will be handled during normal business hours and processed under non-critical severity.
The v4.76 release of VDE/VDE+ and ImagEntry introduces one new feature and no new fixes. The new feature removes the requirement for licenses to be tied to a specific network for workstation ID. Once v4.76 is installed, systems may be moved to new hardware without generating a new license or submitting it to Phoenix for activation.
VDE, ImagEntry and API version 4.76 have only one new feature: once installed the products are no longer tied to a specific network path or workstation ID. This feature could allow an instance of your product to be moved to a new computer without assistance from Phoenix tech support.
We recommend that 4.76 versions not be installed over existing VDE or ImagEntry installations. Instead, the process of installing version 4.76 should be treated as a migration from your existing system. This is particularly true if your existing system is older than 4.7x. Breaking changes can be made between revisions. Installing 4.76 directly into an older instance could result in unpredictable behavior when the 4.76 process tries to access data from files where that data might not exist.
An overview of the 4.76 installation process:
The 4.76 products have been built using Microsoft Visual Studio 2022 with Platform Toolset Visual Studio 2022 (v143). We recommend using the same compiler to rebuild your custom modules.
You will need to provide your Portal logon credentials when you click on any of these links.
The ImagEntry release below is currently available for download.
| Support status: | V4.76 |
| Generally available: | May 29, 2026 |
| Software Bill of Materials: | Download JSON format SPDX Document |
| Support status: | Current |
| Generally available: | May 29, 2026 |
DesktopAny hardware system capable of running a supported version of Microsoft Windows with the minimum RAM recommended for your operating system. Upgraded RAM quantity will increase imaging performance. |
ServerViking products can be installed on any network file server that can provide file services to remote Microsoft Windows-based workstations. These include Windows, Novell, and UNIX systems (using SMB protocol) among others. For thin client installations, remote users can access the server over the Internet with a CITRIX or Microsoft Remote Terminal Server. |
NetworkA 100 Mbit/s network should be adequate to move the images across the network for each transaction. |
Storage CapacityStorage requirements are minimal for data entry batch files, which tend to be small and have a short residence time. As a guideline, assume each operator will generate 100 KB per day. Multiply this by the number of days you will keep the data files on your server to determine the storage capacity requirement. Most document image files, even ones meant for Optical Character Recognition (OCR), are less than 100 KB each and many compressed images are less than 20 KB each, but you must investigate the size of your images and the amount of time they will reside on the server to estimate your disk storage requirements. |