The ATL COM module generalInvoiceRequest is capable of
generating electronic and printed invoices & reminders
generating electronic and printed invoices & reminders
Syntax of the printTemplate variable of the Print method
bstrPrintTemplate argument of the IGeneralInvoiceRequestManager::Print is either empty or of the general form given below.[logTpl[4Recipient]][(objectName1=text;...)][=printTemplateFile][#INIPATH=inipath]
where a [] pair defines an optional part. The commands are case insensitive.
Here are some usage examples:
bstrPrintTemplate argument of the IGeneralInvoiceRequestManager::Print is either empty or of the general form given below.
If the bstrPrintTemplate variable is empty then the default print template (using the data language as language switch - see below) is used.
However, bstrPrintTemplate can be used to change the normal printing behavior or changing printing objects dynamically.
The following syntax is used as content of the bstrPrintTemplate variable:
where a [] pair defines an optional part. The commands are case insensitive.
- logTpl: is the logical template name where 2 template names are defined: summary|detail.
- 4Recipient: defines the optional recipient where {4guarantor | 4patient | 4hc} are defined.
For TG summary4guarantor (or just summary) and detail4guarantor (or just detail) are the defaults for the guarantor addressed invoice/reminder form ("Patienten-Rechnung" and "Rückforderungsbeleg")
For TP detail4hc (or just detail) is the default for the insurance addressed invoice/reminder form ("TP Rechnung").
The other combinations basically use the addressed recipient and automatically change the title and other print objects. E.g. detail4patient prints a detailed invoice with the patient as recipient.Please note, that there is a subtle difference between a patient and a guarantor even if it is physically the same person. From a formal point of view the patient is not the payer of the invoice but the guarantor, and that has an influence upon the title and other print objects!
- objectName1=text; does a substitution of the content of the print object objectName1 by text. A print object is terminated by a semicolon and all
print objects together are enclosed in a () pair.
There are 2 predefined pseudo print objects with a special meaning:
- printTemplateFile is an external print template file name (full path + name!). If an external print template is supplied it must be mapped
against a logical template. Therefore detail=full_vps_file must be used!
- #INIPATH=inipath defines a fully qualified path to a directory where the report engine searches the corresponding .vpd print template INI file. This allows for global settings of a print template in a LAN. The default inipath is the install directory of the Dll
Here are some usage examples:
- bstrPrintTemplate: "" or bstrPrintTemplate: Detail
denotes a standard printing situation for the TP case.
- bstrPrintTemplate: (DOCUMENT_TITLE=Alternate title for the invoice;)
prints a substituted title as given above.
- bstrPrintTemplate: summary4hc(DOCUMENT_TITLE=Alternate title for the HealthCare company;)
prints a summary invoice on A4 with ESR attached on the bottom for a health care company. The title is adjusted as given above.
- bstrPrintTemplate: detail=C:\myForms\myPrintForm.vps
uses the print template "C:\myForms\myPrintForm.vps". An optional INI file with the name "C:\myForms\myPrintForm.vpd" is searched under this condition.
- bstrPrintTemplate: #INIPATH=\\host1\\myForms\
the default path for the ini files (place of the installed component) is changed to "\\host1\\myForms\". If "\\host1\\myForms\" is accessible by all hosts of the LAN then the same INI settings can be used.