One Attachment Manager
Leverage JDE built-in document management capabilities
Open full read-write access to JDE Media Object Attachments - no need for any external Document Management systems, because JDE already has a built-in one, which this solution makes really usable and useful
Current version: 2.2
- Product Brief
- More Details
- System Requirements
- Any external documents can now be readily attached to their respective entities directly in JDE, so that there is no need to make any external lookups:
a) huge time savings to the users - the files can now be attached automatically from any source, no manual effort is required;
b) as soon as the entity in question is found in JDE, the attachments are all immediately available to the user;
- Programmatic access to all attachments offers an easy way to print them, or e-mail, fax, etc.;
- Any attached text (and not only the first Text Attachement) is immediately available in any UBE, immediately ready to be placed anywhere on the produced reports;
- Immediate availability of the full built-in document management system to any external forms solutions or any other interfaces with any other system.
Before this software was introduced, Media Object Attachments in JD Edwards® EnterpriseOne® were not easy to work with - the data is kept in different places and the pointers to attachments were encoded in database BLOB fields. Additionally, the so called "OLE Attachments" are stored in a complicated file format.
The irony is in the fact that JDE has a reasonable and sufficiently flexible built-in Document Management system, which cannot really be made useful without this add-on software, because JDE does not provide any standard convenient and flexible programmatic interfaces.
One Attachment Manager software introduces an easy-to-use and user-friendly interface to work with attachments:
- Retrieving the text attachments;
- Retrieving the file names of any attached files;
- Retrieving OLE Attachments off the STG files used by JDE;
- Adding new text and file attachments.
The core software is delivered as both a DLL and a set of Active-X Automation objects. Typically, a DLL will be used from C and C++ code, while Active-X objects will be used from Visual Basic and similar languages.
On top of this, we include a few complementary pieces of software, designed to use, as well as to illustrate the use of, the power of One Attachment Manager:
- PrintAttachment.exe - a Windows® console (command-line) utility to print any supported attachments from a command prompt or a script;
- A collection of native JDEdwards® EnterpriseOne® C BSFN wrappers to all functions in this package;
- AddAttachment.vbs - a Windows® VB script to attach a new file to any specified JDEdwards® EnterpriseOne® entity;
- OpenAllImageAttachments.vbs - a Windows® VB script to open all specified JDEdwards® EnterpriseOne® entity's Image attachments - in the imaging applications, associated with the attached files' extensions;
- AutoAttach.exe - a Windows® console (command-line) utility to bulk-attach Image, Text (TXT or RTF) or File attachments from a command prompt or a script. This powerful utility processes all files in a given directory, interpreting the file names to construct the MO Key and optionally copies the attached files into the MO Queue and deletes the original file. The files will need to have all of the MO Key elements in their names, i.e.: all files named "AB ######.JPG" can be bul-attached to the Address Book records, using "ABGT" MO DSTR and interpreting the "######" from the file names as the AB Number of the target record - for each file. Up to 32 MO Key elements are supported.
Typically, the files can be created manually (i.e.: scanned images, named on save accordingly) or automatically generated (i.e.: coming out of Create!Print) and streamed into a pre-defined folder for subsequent processing by the included AutoAttach tool, which can then be scheduled to run periodically through Windows Scheduler, to attach any accumulated files to their respective records, copy the files into the destination MO Queue(s) and then delete the original files, so that it would not process them multiple times.
For example, at one JDE site, Jet Forms is splitting Purchase Orders, Invoices, Dockets, etc. into separate PDF files, changes the file names to include the MO Key elements and saves them into a directory, where a periodically running AutoAttach command is retrieving the files from, copying them into selected MO Queues and attaches the files back to the respective lines in JDE, making all of their documents readily available for re-printing and reference. This entire Document Management system costed under US$1,500, including installation (it only requires MO Writer Object to operate and the other tools are all included in the package) and took 1 day to setup and test! No other document management software is currently capable of delivering anything even remotely comparable. Cost-wise, this would compare to approx. 1-2 man-days of consulting services, to simply start discussing this requirement, let alone implementing it.
- SaveAllOLEAttachmentsForGT.exe - given a MO GT DSTR and a destination directory name, it will scroll through all attachments that use this GT and extract all embedded files into separate files into the given directory. The next step can be to re-attach all these documents as non-OLE attachments back, or use the extracted fies in an external system, depending on the need (this new function is available at an additioonal fee).
Some of the ways this software can be used in are:
- Copy MO Attachments between different JDEdwards® EnterpriseOne® entities, i.e.: read attachments from an Employee and add the same attachments to Address Book records of the same person;
- Copy attachments from an external system, i.e. from Lotus Notes, and add them to JDEdwards® EnterpriseOne® entities;
- Copy attachments to an external system, etc.
- Bulk-print all documents per some entity, e.g.: print all Employees' Driver's Licenses, or print all documents per Customer, or Supplier, etc.
OS: MS Windows (x32 or x64)
OS Versions: 2000, 2003/Vista, 2008/Windows 7
OS Editions: Workstation or Server, excluding Home Edition
CPU: Intel or AMD (x32 or x64)
System Type: Physical or Virtual
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: DB-independent - all platforms supported by JDE are supported
Client requirements: this solution uses JDE "C" API's and so requires local installation of JDE - a Server or a Client
This licensing essentially works "as a book", or "one user at a time" for the client computers and as a "per server" license for servers, depending on where it's used.
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 license, 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 use application, we generally recommend to opt in for this Subscription: any future JDE Tools Releases and Releases/Updates may require an updated version of this solution and it's generally more cost-efficient compared to one-off Upgrades.