Integrations

PDF generation available in all Automation editions

Loftware Automation now includes Redirect printing to PDF action in all editions of the Automation module. This action allows you to generate a PDF representation of your label template.

Loftware API improvements

Available in Loftware Cloud Business or above.

Internal optimizations in the Cloud Trigger API and Cloud Print API enable handling hundreds and even thousands of simultaneous requests. Customers running a high-throughput print operations will see a big increase in their real-time print scenarios. The HTTP status code 429 (Too Many Requests) will no longer show for the legitimate API requests.

NOTE: The overall throughput of the Loftware APIs is dependant on the product tier and add-ons enabled in your Loftware Cloud account.

Loftware Workday API updates

Available in Loftware Cloud Business or above.

A new API endpoint is available with the Workday API – PrintFromXmlBatched. The processing behind this endpoint will enable “session print” for all label templates printed to the same printer. This is the optimization technique to combine the compatible print requests together in order to speed up the print process. The printer will receive one print stream with the batched labels instead of the separate print stream.

Optimizations in registering the custom fonts

When your label templates use non-standard fonts, you must store them in the /System/Fonts folder in your Document Storage to make them available to the Lofware Cloud. Once you copy the fonts, the background process will register them with the Loftware Cloud infrastructure so we we can use them in the label previews and for cloud printing.

The optimized and revised process ensures fast registration of the custom fonts mitigating the problem of printing labels without the required fonts.

Adjusting number of threads for Loftware Automation

Loftware Automation is the integration system that automatically responds to the changes in the monitored events with execution of the preconfigured actions. The processing greatly depends on the hardware you use to run the Loftware Automation. The more powerful the processor is the more requests can be executed concurrently and/or in the given time interval. In technical terms, the integration system will use more threads to run more activities. Spawning more threads takes time and resources and should not happen during the processing, threads should be prepared in advance.

With high-throughput scenarios the real-time processing becomes more important. Loftware Automation uses the number of threads from the operation system defaults. In some cases, the defaults might cause a processing bottleneck. With this release, you can adjust the thread numbers in the product configuration (product.config file) if needed.