Scan limitations and constraints

In addition to the scan settings limitations explained in the Scan Settings section, the following limitations apply when initiating a scan with the application.

  • Currently the application does not support job building (meaning adding additional pages to the currently scanned document), hence scanning multiple pages from the glass into a single document is not supported.
  • Scanning a large number of pages (over 1500) in a single document is not possible. When nearing the limit, warning messages will appear and going over the limit will cause the scan job to be canceled.
  • Device capabilities are currently not verified for displaying the options for scan settings, thus A4 devices will still show larger paper sizes among the options. When selecting an invalid option for the device, the scan will either fail (when scanning from glass), or will be performed with a default valid scan size for the device (when scanning from ADF).
  • A4 devices do not have a page size sensor, that is why these devices cannot detect the page size when scanning from the glass. On the AutoStore server side, the default page size is set to automatic. If you scan from the glass with automatic page size set on the device also, the device reports an error because it cannot recognize the page size automatically.

  • Scan tracking limitation: pages that are A4 and smaller (such as A4, A5, Letter) are all shown in the scan tracking report as A4 size. Larger scans (A3, Ledger) are all listed as A3 in the scan tracking report. Refer to the Known issues chapter of the Release notes for details.

  • When selecting PDF as the file format, the file is created on the device after the physical scanning is finished. For a large document, this can take a long time during while the "Please Wait" screen is shown to the user as this phase is still considered as part of the scanning process by the application. After that, file transfer can happen in the background.
  • If the user selects unsupported scan settings, the device reverts to the platform default settings. A message appears to notify the user that the settings have been adjusted. This is a configuration issue (as designed).