WebScanning

Query the scanner for supported values of scanning parameters.

Errors during this operation will normally result in an asynchronous call to the onScanError handler. If anything goes wrong, it invokes callback({ }).

Each property in the object has the name of a Atalasoft WingScan scanning-parameter property e.g. pixelType, dpi, and so on. Each property value is one of the following:

• A enumeration, represented by an array of valid values, for example [0, 1, 3].
• A range represented by an object with min, max and step properties, for example { min: 50, max: 2400, step: 1 }.

Note,

• Note A few models of scanner may provide incorrect or misleading information through this query, such as a flatbed scanner that lists the value 1 for feeder, implying that you can scan from its (nonexistent) ADF.

• Querying the scanner's capabilities requires opening the scanner, which may fail (scanner offline, unplugged, etc.) which may display an error box to the user. For friendly user interface design, make 'choose your scanner' or 'change scanner' into a separate dialog or screen, and call getSupportedValues when the user OK's a new scanner choice.

• Completing the getSupportedValues operation can take several seconds.

Code sample(see, getSupportedValuesCallback for complete list of available properties):

Atalasoft.Controls.Capture.WebScanning.getSupportedValues(null, function(values){
  // if successful might call gotValues with an object like this:
  // {
  //     pixelType: [0, 1, 2],
  //     dpi: {min: 50, max: 1200, step: 1},
  //     duplex: [0, 1],
  //     feeder: [0, 1],
  //     paperSize: [0, 1, 2, 4, 7, 9],
  //     orientation: [0, 1]
  // }
  });

Aborts the current background operation in progress, if any. If there is no current background operation, it does nothing.

Background Operations:

• Scanning (started by scan)
• Importing files (started by importFiles)
• Querying supported values (started by getSupportedValues)
• Displaying the scanner settings dialog (started by showSettingsDialog)

This method should be called to shutdown all Web Capture services gracefully and free all acquired resources (for example, correctly close scanners that web application worked with).

Disposed Web Capture Service could be reinitialized by calling {Atalasoft.Controls.Capture.WebScanning.initialize|initialize}.

This method loads the scanning options (scanningOptions) from a string previously produced by getProfile.

Reloads the internal array of the available scanners and optionally passes it to provided callback.

Query the scanner for current values of scanning parameters.

Errors during this operation will normally result in an asynchronous call to the onScanError handler. If anything goes wrong, it invokes callback({ }).

Gets the name of WebCapture Service installer.

Gets version of JavaScript components of WingScan as an array of numbers.

This method returns a string, containing the current scanning options stored in scanningOptions. The string is in JSON format, but you should not rely on that.

Gets the NetBIOS name of the local scan station.

Gets WingScan client current session id as an string.

Gets WingScan path to persistent storage.

Set's the barcode license.

If license is not set default barcode engine is used. It's possible to enable Honeywell Omniplanar/SwiftDecoder engine, but license key should be purchased separately. Applicable for Web Capture Service for Windows only.

Gets components of WingScan version as an array of numbers.

Begin a background process to import files with the specified options. The options object has the same valid properties as the scanningOptions parameter to the scan method above, however, this method ignores options that control the scanner. If options is omitted, null or undefined, importFiles uses the scanning options stored in scanningOptions.

The user is prompted to select one or more files on the local machine, with a standard multi-select File Open dialog. The supported file formats are those listed in File Formats and File Options above, plus PDF. If the user cancels the File-Open dialog, this is treated as an import of zero (0) files.

The title of the dialog is a localizable string named importFilesPrompt.

The selected files are read image-by-image and processed as if they were being scanned - post-processing options are applied to each image - except for PDF files, which are passed through 'verbatim'.

Files are processed in an order determined by Windows, and not necessarily in the order they appear in the File Open dialog nor the order of selection. If order of processing is important, the user must do separate Import operations.

importFiles calls the onScanStarted handler before doing anything else, then calls the onImageAcquired handler with each successfully imported image or PDF file, and finally calls the onScanCompleted handler when finished, whether successful or not.

The eventObj parameter to onScanCompleted has a property success that tells you if the import completed successfully. See the onImageAcquired event for details of how PDF files are imported.

If the user attempts to import any files of unsupported type (such as .doc or .psd) the error unsupportedFileFormat is fired to the onScanError handler and the import proceeds, completely ignoring all those files.

If a file of supported type cannot be imported (e.g. corrupted data, access error), an appropriate error is fired to the onScanError handler and the import process is aborted i.e. completes unsuccessfully.

The images and files imported by importFiles are not retained by the control or uploaded automatically to the server.

This method is called (with no parameters) when the user clicks the designated import button, if any.

This method must be called to initialize the WebScanning component. The init object must contain a handlerUrl property, all other properties - listed below - are optional. Initialization is asynchronous! When this method returns, WebCapture is not yet initialized, and may never be. When initialization is complete (licensing has been verified, a scanner list has been constructed and it is possible to initiate scan or import operations) WebScanning calls the onScanClientReady call-back from the init object.

Asynchronously, initialize attempts to install or start the WebCapture plugin or service, verify licensing, and then to initialize scanning on the client, and to collect a list of available scanners. If it is successful, it will populate a scanner-list control and enable a scan button and/or import button, if they exist with the appropriate classes:

• If there is a listbox (select element) with class atala-scanner-list, it is loaded with the list of available scanners and the default scanner is selected.
• Any controls with class atala-scan-button are given a click-handler that calls scan
• Any controls with class atala-local-file-import-button are given a click-handler that calls importFiles

Checks if Web Scanning control is initialized or not.

Initiates a scan, as a background process, with the specified scanning options (see Scanning Options#scanningOptions). If you pass in nothing, null or undefined, it uses the scanning options stored in Atalasoft.Controls.Capture.WebScanning.scanningOptions.

This method is called (with no parameters) when the user clicks the designated scan button.

Use abortScan to abort a running scan.

When a scan is started it calls the onScanStarted handler, and when it ends, normally or not, it always calls the onScanCompleted handler.

Starts a background operation to display the settings-only dialog (custom user interface) of the scanner, if the scanner supports this feature.

Note: no scanner driver provides settings dialog under macOS

This shows a version of the scanner's UI that is only for choosing settings, without a Scan button.

When the operation completes, successfully or not, callback(status) is called, where status is an object. status.complete is true if the dialog was successfully displayed and closed by the user, false if the dialog could not be displayed or the operation was aborted.

If anything goes wrong, the onScanError handler will be called, asynchronously, with details.

The scanner used is:

• options.scanner if that exists and is a string.
• Otherwise scanningOptions.scanner if it exists and is a string.
• Otherwise the scanner most recently selected in the UI.
• Otherwise the default scanner, as reported by scanner device manager (TWAIN on Windows or ImageCapture on macOS).

The onImageAcquired handler is called during scanning, once for each image received from the scanner, with a single parameter which is an image object - that is, an object that represents the received image held by WingScan. The image object provides a rich set of properties and a small set of methods for exporting the image data in various ways.

The onImageAcquired handler is also called by the importFiles method, once for each imported image, and once for each imported PDF file.

Imported PDF files are handled somewhat specially: they are represented by an image object with the distinguishing property filename - which is the full path of the imported file. When the filename property is present, the usual image properties are absent. The image object that represents an imported PDF still supports the methods asBase64String, clear, saveEncryptedLocal, and thumbnail.

Called when Web Capture Services discards image. This can happen, when flag discardBlankPages is set.

This handler is called when scanning initialization is complete. Normally in case of failure the onScanError handler will have been called.

Called when scan or import completed. See Handling Errors for details.

Called when scan or file import completed with error.

Called when scanning starts.

Fired when scanned document upload completed.

Fired when scanned document upload completed with error.

Fired when scanned document upload started.