SOURCE DATA CAPTURE FROM AN INDEX FILE
Data on scanned objects are most often captured from an XML file, which is the result of batch scanning with the IMiS/BatchScan product. IMiS/BatchScan stores paths to the batch scanned documents into an XML file, together with bar code information and potential metadata, which serves as input data for the processing in IMiS/Avalanche. An alternative for source data capture is the data that are the result of the generating of digitized contents and are equipped with a relevant bar code (external scanning, documents created in the ERP system, etc.)

AUTOMATED OR INTERACTIVE METHOD OF TASK EXECUTION
IMiS/Avalanche can operate in automatic mode, on the basis of predefined intervals, and execute tasks. If greater control over execution time and the procedure itself is needed,
the operator can execute tasks interactively via the user interface. Execution events are recorded in an event log, which can later be accessed to view the archiving procedure and document routing.

USE IN THE HCL NOTES/DOMINO ENVIRONMENT
IMiS/Avalanche performs the archiving and routing of digitized content into relevant electronic folders of Notes documents, independently of the type of the Notes application solution. Using the paths to source files and potential metadata from the index file, IMiS/Avalanche first stores the source files to IMiS/ARChive Server and then writes the acquired IDs, along with potential metadata, into Notes documents in accordance with predetermined rules and predefined processes.
The digitized content is stored as objects to a physically completely separate IMiS/ARChive Server and NOT as attachments to Notes documents.
After the digitized content is archived, we can optionally trigger adapted scripts, which enable users to execute specific applicative algorithms for the additional processing of documents after archiving.

ENTRY OF SCANNED DOCUMENTS AND DATA INTO THE SAP SYSTEM
During automatic routing, IMiS/Avalanche acquires input data from the index file (bar codes, metadata, a link to source objects). Every object file (one-page or multi-page document or file) is assigned a unique ID upon being stored on the archive server.
The archived object ID and bar code data are entered into the SAP notations via the standardized SAP transactional RFC function ARCHIV_BARCODE_INSERT_RFC.
After establishing a connection between the waiting SAP notation and the archived object, the document is accessible to users via the standardized ArchiveLink interface.
When opening the SAP document, the user can select and view the scanned document (PDF/A, TIFF), depending on the settings, by using the menu function.
After the user clicks on the attachment, SAP acquires the archived object from the electronic archive using its ID and displays it in the integrated SAP viewer.