Transact

⌘K
  1. Home
  2. Transact
  3. Features and Functions
  4. Administrator Role and Fe...
  5. Importing Documents
  6. Web Scanner
  7. Encrypting Temporary Web Scanner Images

Encrypting Temporary Web Scanner Images

Applies to: Transact 4.5.0.0 and newer

You can configure Transact to encrypt the images that are stored on your local machine. A checkbox called Encrypt Temporary Images is available in the Scanner Profiles configuration screen. By default, this field is unchecked. If you select this checkbox, the system will encrypt the display images uploaded from the Web Scanner to the local machine.

To configure this property, navigate to the Scanner Profiles configuration screen:

Login -> Batch Class Management screen -> Select a Batch Class -> Scanner Profiles

C:UsersEphesoftAppDataLocalMicrosoftWindowsINetCacheContent.Wordscanner profiles1.png

Scroll to the right side of the page to find the Encrypt Temporary Images checkbox.

C:UsersEphesoftAppDataLocalMicrosoftWindowsINetCacheContent.Wordencrypt field.png

If you select the Local Storage option but deselect Encrypt Temporary Images, the display images will be stored on your local machine without encryption.

C:UsersEphesoftAppDataLocalMicrosoftWindowsINetCacheContent.Wordscreen1.png

If you select both Local Storage and Encrypt Temporary Images, the display images stored on your local machine will be encrypted.

You will still be able to view the images on the Web Scanner screen in the browser:

C:UsersEphesoftAppDataLocalMicrosoftWindowsINetCacheContent.Wordscreen2.png

However, images in the corresponding temp subfolder on the local machine will be encrypted.

C:UsersEphesoftAppDataLocalMicrosoftWindowsINetCacheContent.Wordscreen3.png

If you try to open any encrypted image, you will receive the following message:

C:UsersEphesoftAppDataLocalMicrosoftWindowsINetCacheContent.Wordscreen4.png

Note: Once scanning starts, the value of the encryption property will remain the same until the current batch is finished. Changing the Scanner Profile with a batch in progress will not affect the current batch. The changes will take effect only with a newly created batch instance. This is done to ensure the integrity of images and to make sure that batch processing remains consistent.