Last Updated on by
For HighJump users, eFORMz generally uses a database connection to pull all necessary data for the final document to be generated, paired with a “trigger” of some kind that starts the document generation process, such as:
- The printing of a document to a virtual printer
- Directory monitoring for new files
- A timed queue that runs a database call at some interval
- A web service call to eFORMz
First, set up a virtual printer to accept the shipping label. This is described in the following post: Configuring the eFORMz Port Monitor.
Next, set up an eFORMz project that “scrapes” some piece of unique data off of the label. Usually, this means grabbing a tracking number or a reference field. This is necessary to perform the database call that returns the data required for the packing slip part of the document.
To set up this database connection, refer to the following post: Where to Set Up Your Database Connection.
Many HighJump users utilize a stored procedure that returns the necessary fields to fill in the dynamic data of a given form. This permits greater control over what data is sent to eFORMz and facilitates better management of the business process. For more information, consult the following post: Calling Database Stored Procedures.
Alternatively, a similar stored procedure can instead perform a HTTPS POST in XML format of the dynamic data directly to eFORMz. In other words, eFORMz can call a web service to post data to a queue. This is described briefly in the following post: Post Data to eFORMz via a Web Service Call.
This method is particularly useful for HighJump users that want to build more complex documents. XML provides more flexibility on the structure/format of data that can be returned. The XML POST is also recommended for high-volume situations as there is no database connection to be made by eFORMz. The XML contains all the dynamic data needed to generate the document which allows eFORMz to process a document extremely quickly. For detailed documentation on the eFORMz API, consult the following posts:
- eFORMz API (Called as a Web Service)
- eFORMz API .NET Web Service Call
- eFORMz API URL Parameters
- Web Service POST call to “Wake Up” a “Sleeping” Queue: Part 1
- Web Service POST call to “Wake Up” a “Sleeping” Queue: Part 2
- Web Service POST call to “Wake Up” a “Sleeping” Queue: Part 3
- Web Service POST Call Output Advantages
- Web Service POST Call Output