SAB applications relate to two specific cases:
In the first case, the MAPPING robot detects incoming spool files in a specific Outq and triggers the related process, i.e. remapping, generating a PDF file, emailing, or electronic archiving, etc.
In the second case, which applies to the most recent and still to come releases of the SAB ERP, the system doesn’t produce output spool files anymore. Rather, it stores the information in one or more data files. Then, from these files, MAPREPORT/MAPOFFICE is used to create the documents required by the different departments inside the bank.
Documents are triggered by the SAB Scheduler or a command, and the MAPPING robot handles the rest.
In any case, the whole cycle can be automated without modifying SAB sources. MAPPING Suite actions are transparent for the end-users and are independent from the type of printers and their associated connection modes.
On these platforms, data sources are manifold: text, XML, or database files, etc.
It is imperative to use the MAPREPORT/MAPOFFICE module to create the paginated spool files that will be remapped by the MAPPING module.
Unfortunately, these platforms do not come with a native spooler, which means you would need to reprint everything in case of a paper jam for example.
MAPPING OUTPUT MANAGER is the spooler developed by MAPPING SA to declare all or part of your printers. This way, users can preview or direct their print files to other printers. They can also release, hold or save their files, and of course print them out.
But the special feature about MAPPING OUTPUT MANAGER is that it can react in case of a printer jam by applying various scenarios such as automatically directing a print file from a specific page number to another printer, without the user doing anything at all.
To sum up, MAPPING Suite lets you select the distribution method for each type of document individually: