Bevan at 03:19, 20 April 2015

2015-04-20T03:19:56Z

← Older revision		Revision as of 03:19, 20 April 2015
Line 2:		Line 2:

	EEE can print transactions dockets such as inter-store transfer slips, goods receipts etc to Enabler POS receipt printers so long as the POS receipt printer uses a Windows print queue (not OPOS). The Windows print queue must be shared on the POS till and EEE must have access to print to that shared print queue. In practice this means the EEE services service account must have access to the print queue. This can be achieved on a domain, or by creating a local Windows account with the same credentials as the EEE services account. It may also be possible by using the Windows credential cache on the EEE server or granting guest or everyone access to the print queue. The most appropriate means of granting access will depend upon a number of factors including the Domain/Workgroup environment, Windows versions and individual preferences re security levels of print queues.		EEE can print transactions dockets such as inter-store transfer slips, goods receipts etc to Enabler POS receipt printers so long as the POS receipt printer uses a Windows print queue (not OPOS). The Windows print queue must be shared on the POS till and EEE must have access to print to that shared print queue. In practice this means the EEE services service account must have access to the print queue. This can be achieved on a domain, or by creating a local Windows account with the same credentials as the EEE services account. It may also be possible by using the Windows credential cache on the EEE server or granting guest or everyone access to the print queue. The most appropriate means of granting access will depend upon a number of factors including the Domain/Workgroup environment, Windows versions and individual preferences re security levels of print queues.

			== Integrated Logins ==

	When Enabler creates an integrated login to EEE to perform an inventory transaction such as inter-store transfers, Enabler passes in the ''share name'' of its receipt printer (Enabler uses the Windows print queue configuration to retrieve the share name and passes this to EEE). Enabler also passes to EEE command strings for enlarged print, receipt cut and so forth. EEE then simply writes its receipt text including formatting strings to the print queue share name passed in by Enabler.		When Enabler creates an integrated login to EEE to perform an inventory transaction such as inter-store transfers, Enabler passes in the ''share name'' of its receipt printer (Enabler uses the Windows print queue configuration to retrieve the share name and passes this to EEE). Enabler also passes to EEE command strings for enlarged print, receipt cut and so forth. EEE then simply writes its receipt text including formatting strings to the print queue share name passed in by Enabler.

Bevan: Summary of how EEE prints IBT and other dockets to Enabler receipt printers.

2015-04-20T03:18:59Z

Summary of how EEE prints IBT and other dockets to Enabler receipt printers.

New page

Created: 20 April 2015. Last Reviewed: 20 April 2015

EEE can print transactions dockets such as inter-store transfer slips, goods receipts etc to Enabler POS receipt printers so long as the POS receipt printer uses a Windows print queue (not OPOS). The Windows print queue must be shared on the POS till and EEE must have access to print to that shared print queue. In practice this means the EEE services service account must have access to the print queue. This can be achieved on a domain, or by creating a local Windows account with the same credentials as the EEE services account. It may also be possible by using the Windows credential cache on the EEE server or granting guest or everyone access to the print queue. The most appropriate means of granting access will depend upon a number of factors including the Domain/Workgroup environment, Windows versions and individual preferences re security levels of print queues.

When Enabler creates an integrated login to EEE to perform an inventory transaction such as inter-store transfers, Enabler passes in the ''share name'' of its receipt printer (Enabler uses the Windows print queue configuration to retrieve the share name and passes this to EEE). Enabler also passes to EEE command strings for enlarged print, receipt cut and so forth. EEE then simply writes its receipt text including formatting strings to the print queue share name passed in by Enabler.

== Non-Integrated Logins ==

For non-integrated logins it is more complicated. If at head office, EEE will send its output to the receipt printer configured for the till code specified for head office printing in the general tab of configuration settings. The Enabler configuration setting for the print queue will need to be specified in \\computer\print-share-name format.

For all other branches, if EEE can find a single till that has a receipt printer with the print queue configured in \\computer\print-share-name format it will send the print job to that queue. Otherwise EEE will display a popup prompt to the user to select a printer - the popup will list all ''receipt'' printers from the branch printer queue table as well as all tills found with an enabled receipt printer where the receipt printer queue name is specified in \\computer\print-share-name format.

Enabler EEE Docket Printing - Revision history

Bevan at 03:19, 20 April 2015

Bevan: Summary of how EEE prints IBT and other dockets to Enabler receipt printers.