JDE Converter
(As of 3.3.009.01)
../DocOrigin/DO/Bin/Java/JDEConverter.jar
The Base Command
java -jar JDEConverter.jar
Run without options to see usage text.
To see what version of the converter is running, add -v
Production
This converter supports JDE PDF and OSA XML as input data types. The output is a "Data XML"; an XML file compatible with DocOrigin's Merge engine.
JDE PDF to Data XML
-jdePdfToDataXml -in inputPdf -out outputXml [-splitDocsByPage] [-docDefiningNode/-splitDocsByNode "Invoice Number"] [-docDefiningNodeID "8|135"] [-osaXmlInputFixup] [-includeRC] [-excludeCH] [-noIdMode]
Use the appropriate data node specification to determine document splitting. The -docDefiningNode[ID] options can be used in conjunction and repeated to list multiple split nodes.
-docDefiningNode uses Name or Alias (if the Name is missing).
-docDefiningNodeID uses "sectionID|controlID" for when there are possible conflicts or uncertainties with using the object Name.
-splitDocsByNode starts a new document when the specified data node is encountered, regardless of its value. Overrides the -docDefiningNode[ID] options.
-splitDocsByPage starts a new document when the page variable appears in the first header. Use this option to define a new document when the OSA variable Type="PG" (page number) starts at 1.
Use -osaXmlInputFixup to apply corrections to the interim OSA XML, such as fixing whitespace issues in attribute names.
*Use -includeRC to include Report Constant objects from OSA XML into the data file as dynamic data.
*As of 3.4.001.03 use -excludeCH to leave Column Header (CH) objects from OSA XML out of the data file.
Use -noIdMode to emit node names without the JDE section and control IDs, de-duplicated where those names would otherwise collide (applies to Data and Blueprint flows; not valid with -osaXmlToXatw). This option collapses consecutive underscores in pane names to keep them consistent with CFP6 object names and JDE Converter data output. And in order to to prevent naming conflicts:
- Appends the suffix "_RC" for a Report Constant object type
- Appends the suffix "_CH" for a Column Header object type
- Concatenates the object Alias and Name to solve non-unique names of the same object type
- Retains the object Name for RV (Report Variable) object type (or Alias when the Name is not present)
OSA XML to Data XML
The OSA to Data conversion is a step of PDF to Data conversion, and can be invoked separately. There is no -splitDocsByPage option at this step.
-osaXmlToDataXml -in inputXml -out outputXml [-docDefiningNode/-splitDocsByNode "Invoice Number"] [-docDefiningNodeID "8|135"] [-osaXmlInputFixup] [-includeRC] [-excludeCH] [-noIdMode]
Development
JDE PDF to OSA XML
For development, the OSA XML must be explicitly generated to use the OSA XML to DocOrigin XATW option.
-jdePdfToOsaXml -in inputPdf -out outputXml [-fontScale 15]
Increase the default -fontScale value (15) if objects appear too narrow in the next step's resulting XATW.
OSA XML to XATW
Creates an XATW template that matches the JDE PDF design.
-osaXmlToXatw -in inputXml -out outputXatw [-includeRC] [-excludeCH]
*Use -includeRC to treat Report Constant objects from OSA XML as dynamic data.
*Use -excludeCH to treat Column Header (CH) objects from OSA XML as static labels, not data.
JDE or OSA PDF to Blueprint XML
For developers, a full data "Blueprint" of potential fields, regardless of those present in the specific data file.
-jdePdfToBlueprintXml -in inputPdf -out outputXml [-osaXmlInputFixup] [-noIdMode] -osaXmlToBlueprintXml -in inputXml -out outputXml [-osaXmlInputFixup] [-noIdMode]
*These options should be applied consistently for data and design to match.