User Manual

2.18 Frequently asked questions (FAQ)

Updated on

Creating Files in the Workflow fails

We are checking in PDF Files from our Fileserver using http/https. But the files in the Workflow are corrupted or cannot be imported.

Sometimes a Fileserver or a Network-attached storage (NAS) is not configured correctly when serving PDF Files and are using a wrong HTTP Header like "Content-Type: text/html". This Content-Type has to be set to application/pdf. You can check out the Content-Type used with Web Development Tools that are included in most Browsers today. Open the full path in your Browser and check the HTTP Headers in the "Network" Tab.

Accessing Network Shares

We are using SMB with credentials. How can we access the files using the Durst Workflow Rest-API?

You can save the Network Share using the Administration > File Management Menu in Durst Workflow. There you can create, edit and manage Shares and Folders. The Rest-API is then using the saved credentials.

Login is not Working

We have created a dedicated External User to acces the API but the Login is not working.

Do not use #, & or ? for username and password, because these are needed characters in the url query string. Ampersand (&) is used as a seperator, the question mark (?) to pass the query string and the hash (#) to further specify a subsection.

Exceeded maxRedirects

We get following error:

Error: Exceeded maxRedirects. Probably stuck in a redirect loop http://xxx.xxx.xxx.xxx:8081/api/v1/pms/ppd-pms/pms/ppd-pms/pms/ppd-pms/pms/ppd-pms/pms/ppd-pms/pms/ppd-pms/pms/ppd-pms/pms/ppd-pms/pms/p pd-pms/pms/ppd-pms/index.html

Please check, if you are using the full base path for Rest-API requests: http://xxx.xxx.xxx.xxx:8081/pms/

External Access to Durst Workflow

Is it possible to access the Durst workflow from outside the internal network?

This is of course possible. The prerequisite for this is in the simplest case the use of a static IP or a host name and a corresponding port forwarding to the internal workflow server on port 8081.

From the network point of view, configurations as follows are possible. The external port number can be arbitrary apart from the frequently used standard ports. Some examples:

workflow.domain.com:8081 → 127.x.x.x:8081
workflow.domain.com:52211 → 127.x.x.x:8081
11.47.87.112:8081 → 127.x.x.x:8081

For security reasons, we recommend that you allow dedicated access from the outside using whitelisting. This means that access to Workflow is blocked by default, the source addresses of Smart Shop or LiftERP are whitelisted individually.

In case of a connection e.g. of an online store to Durst Workflow, it must also be guaranteed that Durst Workflow itself has access to the sources to pull print data from the web/file server (http/https/smb).

The IT service provider is also free to use other methods for securing, e.g. a reverse proxy. Basically, it is only necessary to ensure that Durst Workflow can be reached at destination port 8081.

Comparing Status in Workflow UI versus Rest-API

What are the matching statuses of Articles, Print Items, Orders and Production Jobs of the API output compared to Workflow UI

Articles

Workflow UI Rest-API Description 
Created CREATED Article was initially created
Normalized CHECKED_IN Article was preflighted, Preflight without Errors
Data Check CHECK_REQUIRED Article was preflighted, Errors occured on Preflight Check
Final Artwork FINAL_ARTWORK
Waiting for Approval WAITING_FOR_APPROVAL

Approved APPROVED
Locked LOCKED Article is locked, editing is not possible until it’s unlocked  
Workflow UI Rest-API Description 
Created CREATED Print Item was initially created
Normalized CHECKED_IN Print Item was preflighted, Preflight without Errors
Data Check CHECK_REQUIRED Print Item was preflighted, Errors occured on Preflight Check
Final Artwork READY_FOR_PRINT
Waiting for Approval WAITING_FOR_APPROVAL

Approved APPROVED
Imposed IMPOSED
Sent to Printer SENT_TO_PRINTER
Printed PRINTED
Quantity Reached QUANTITY_REACHED

Production Jobs

Workflow UI Rest-API Description 
Created CREATED Production Job was initially created
Ready for Print READY_FOR_PRINT Job was created succesfully
Output Config Assigned OUTPUT_CONFIG_ASSIGNED An Output Configuration, Color Policy or Substrate Shape was assigned
Imposed IMPOSED
Sent to Printer SENT_TO_PRINTER
Printed PRINTED
Quantity Reached QUANTITY_REACHED
Closed CLOSED
Workflow UI Rest-API Description 
Created CREATED Print Order was initially created
Approved APROVED
In Production (Partial) IN_PRODUCTION_PARTIAL Parts of the Order are in Production (Part of a Production Job)
In Production
IN_PRODUCTION

Produced PRODUCED
Closed CLOSED
Workflow UI Rest-API Description 
- CREATED Print Order Item was initially created
Previous Article 2.17 Definitions
Next Article 3.1 Introduction
Still Need Help? Contact Us