Support Portal

Working with the BigPrintJob Setting

Overview:

This document is intended as an overview of the process by which print jobs may be batched together. Several separate print jobs are aggregated into one, which is then sent to the printer. This feature can be especially useful in scenarios where accounting software is being used to monitor and control the flow of material being sent to printers. Without the BigPrintJob setting, using the "Print Summaries' Images" menu item will result in the user being prompted to enter the necessary client/matter numbers once for every record that has an image. Turn the BigPrintJob on and the user will instead be prompted only once.

Details about BigPrintJob:

The .ini files that are modified depending on level are:

User in this case Profiles\Imgprint.Ini
Case level \SwCase.Ini
Admin level \Profiles\all users\swsettings.ini

The key name within the specified .ini is "BigPrintJob" and it is set to 1 if images will be printed in batches and 0 if not. The "BigPrintJob" key name will not exist by default.

Please add the "BigPrintJob" setting to the "[Settings]" section. If that section does not exist in your target INI file, then create that section. The example below enables the "BigPrintJob" behavior.

[Settings]
BigPrintJob=1

Note: Accessdata has received reports of "out of memory" errors (e.g. error 20001 not enough memory) occurring once the BigPrintJob setting was enabled. If this occurs, then please consider submitting fewer documents at once. 

Optional:

Setting of the Value via Scripting:

The interface to BigPrintJob is entirely through scripting entry points (AKA intrinsics), one of which turns the setting on/off (and writes to one of three .ini files) and then two others that can be used to check on the state of the setting. The .ini files that are modified depending on level are:

User in this case Profiles\Imgprint.Ini
Case level \SwCase.Ini
Admin level \Profiles\all users\swsettings.ini

The key name within the specified .ini is "BigPrintJob" and it is set to 1 if images will be printed in batches and 0 if not. The "BigPrintJob" key name will not exist at all until some action is done to turn it on or off, at which point an entry like

[Settings]
BigPrintJob=1

will be written to the appropriate .ini, under the [Settings] section.

You will need to be in the Scripting window in order to use the scripting entry points. Locate the Script menu of Summation and select Scripting. Type in the desired script (see examples below, in blue) and go to File, Run on the Scripting window in order to execute.

The Scripting Entry Points:

1) IMG.WritePrintJobSetting
The first example will set BigPrintJob=1 (True) on the case level and not change how it works on the user and Admin level. The second example will set BigPrintJob=0 (False) on the user level, BigPrintJob=1 on the case level and not change the current setting (whatever that is) on the Admin level. See ReadPrintJobSetting and PrintJobSetting in the IMG object for example on checking status of whether or not images will be printed in batches for the active user/case.

img.WritePrintJobSetting -2,True,-2
OR
img.WritePrintJobSetting False,True,-2

2) IMG.ReadPrintJobSetting
The first line will change the current settings (User = True, Case = False, Admin is unchanged). Second will return a -1, indicating batch print is turned on. Final line shows a message that explains what and why the setting is in place.

img.WritePrintJobSetting True, False, -2
msg img.ReadPrintJobSetting
msg img.PrintJobSetting

3) IMG.PrintJobSetting
The first line will change the current settings (User = True, Case = False, Admin is unchanged). Second will return a -1, indicating batch print is turned on. Final line shows a message that explains what and why the setting is in place.

img.WritePrintJobSetting True, False, -2
msg img.ReadPrintJobSetting
msg img.PrintJobSetting

Applies to:

Summation iBlaze