What it does. Once installed, AUTOPRINT lets you configure your JDE system to do any of the following whenever a UBE runs on the Server:

1. Automatically Print the UBE output.
2. Automatically E-mail it to the submitting user — with optional compression of the PDF / CSV.
3. Both of the above. Scheduled Jobs included.

Plus — independently:

1. Configure E-mail Distribution Lists per UBE | VER to automatically send the PDF to any number of pre-configured recipients — ideal for circulating integrities and trial runs.

Every OneWorld / EnterpriseOne site needs this kind of automation. The ability to automatically e-mail or print certain reports is important and often critical. AUTOPRINT eliminates the human errors that come with manually printing or sending reports, and unattended printing means you get the printed output exactly when you need it.

Any report / version configured for automatic printing will print every time it runs, no matter how it was submitted — manually, via APIs, or by the Scheduler. Both synchronously and asynchronously executed jobs are supported.

For Functional Users

You don’t do anything different. You submit the report the way you always have — manually, through an API, on the Scheduler — and the right thing happens.

What changes for you:

• The report just prints. If your report is configured for printing, every submission lands on the printer your CNC team mapped. No need to remember to print it; no missed runs; no chasing operations.
• The report just arrives. If your report is configured for e-mail, the PDF (optionally compressed) lands in your inbox — same logic, no manual steps.
• Distribution lists. Integrities and trial runs can be sent automatically to a pre-configured list of recipients per Batch Program / Version. Set it up once, every run goes out.
• Both at once is fine. The system can be configured to both print to a printer and e-mail you the PDF for the same run.
• No duplicates. If multiple settings happen to call for an e-mail to be sent for the same run, the e-mail is sent only once.
• No new training. Submission is unchanged. The only difference is that the right things now happen automatically.

For your e-mail to actually arrive, your e-mail address must be defined in Address Book (Line 0, Sequence 1 — not Workflow). Your CNC team handles the rest.

For IT & CNC

AUTOPRINT extends the standard JDE Default Printer mechanism with three new status codes and a small set of lookup combinations. There is no “magic” outside of these — combinations are hard-coded and only the listed ones trigger the AUTOPRINT logic.

New Default Printer status codes:

• PI — print only. The job prints to the printer defined with the PI status, not with the usual AV status (even if an AV mapping exists).
• EM — e-mail only. The job sends its output to the submitting user.
• PE — print and e-mail (does both, in a single mapping).

Lookup combinations (checked in this exact order; the first match wins):

• Specific User / Specific Environment / Specific Batch Program / Specific Version / Specific Host
• User’s Group / Specific Environment / Specific Batch Program / Specific Version / Specific Host
• *PUBLIC / Specific Environment / Specific Batch Program / Specific Version / Specific Host

• Specific User / *ALL / Specific Batch Program / Specific Version / Specific Host
• User’s Group / *ALL / Specific Batch Program / Specific Version / Specific Host
• *PUBLIC / *ALL / Specific Batch Program / Specific Version / Specific Host

• Specific User / Specific Environment / Specific Batch Program / *ALL / Specific Host
• User’s Group / Specific Environment / Specific Batch Program / *ALL / Specific Host
• *PUBLIC / Specific Environment / Specific Batch Program / *ALL / Specific Host

Composition of actions: actions add up. EM configured for a Group plus PI configured for a User produces the same result as a single PE setting on the User — the Group members get the PDF by e-mail and the named User both gets the e-mail and the printout. Actions also do not duplicate: if two applicable settings (e.g. EM and PE) both call for an e-mail, the e-mail is only sent once per job run.

Prerequisites:

• For e-mailing to work, the Host must be configured for e-mail support (same configuration as for Workflow messages to external e-mail). See the JDE Knowledge Garden procedures.
• The submitting user must have an e-mail address defined in Address Book (Line 0, Sequence 1 — not Workflow). Without it, e-mail cannot be sent.
• For optional compression of the output before e-mailing, your platform-specific compression utility is used. This saves both network bandwidth and mailbox space.

Synchronous and asynchronous UBE submissions are both supported. The physical printer setting matters only for printing — for e-mail-only mappings, any printer can be chosen for the mapping; the printer itself will not be used.

Installation: install the Boomerang Package (about 1 minute) and then build and deploy an Update Package containing the delivered Objects for your Logic Servers (about 5 minutes). Then create the Default Printer mappings for the Batch Versions you want printed or e-mailed immediately, with the new PI / EM / PE statuses. No user training and no extensive testing required — instructions are included in the Package, and there is no expensive consulting on top.

AS/400 note: due to historical bugs in the OneWorld implementation of the SendMail API, the e-mailing function did not work on AS/400 servers in older releases. It appears the underlying bugs may have been fixed in later Service Packs, although this has not been re-tested. The printing functionality is not affected on any platform.

JDE Releases: XE (B7333), ERP8 (B7334), B9 (E1 8.9), E810, E811 (including E811 SP1), E812, E900, E910, E920
JDE Tools Releases (pre-Unicode): SP16 onwards
JDE Tools Releases (Unicode): TR891 onwards
JDE Backend Hardware Platforms: hardware-independent — all platforms supported by JDE are supported
JDE Backend Database Platforms: database-independent — all platforms supported by JDE are supported

This software is licensed “Per JDE Installation”, which for all practical purposes means “Per Deployment Server” and supports all Environments and Users running off the same Installation.

The optional Yearly Update / Upgrade Subscription is available at the time of purchase (not available separately) for an additional yearly fee. It is payable in advance per licence, per year. It includes premium support and all software updates released during the paid period. Its cost is calculated as 20% of the product’s list price at the time of invoicing, as may change from time to time. Unless the software is purchased for a single, short-term application, we generally recommend opting in for this Subscription: any future JDE Tools Releases and Releases / Updates may require an updated version of this solution, and the Subscription is generally more cost-efficient than one-off Upgrades.