Setting the path for the pdfToolbox Switch apps
If you're using the pdfToolbox Switch apps in your workflows (as opposed to the configurators supported in older versions of Enfocus Switch), determining the path to the application works differently.
(To know how to work with the path to the configurators, read this article).
Where to set the path to pdfToolbox CLI
When using the pdfToolbox Switch apps, setting the application path has to happen on the actual pdfToolbox flow elements in a Switch flow.
The "Application path" property (1) controls which pdfToolbox CLI application is used when this flow element is used in a Switch flow.
Default and specific path
By default, the "Application path" property is empty. In that case, the app searches for the most recent version of pdfToolbox CLI on the system and uses that.
If you don't want to use the most recent version of pdfToolbox CLI on the Switch server, or your pdfToolbox CLI is installed in a non-standard location, put the full path to the pdfToolbox CLI you want to use in the "Application path" property. Make sure the path points to the pdfToolbox CLI application, and not the pdfToolbox Desktop application.
Mixing different versions
The fact that Enfocus Switch enforces this way of working for Switch apps, has advantages and disadvantages. While it means that pdfToolbox CLI version management now needs to happen on a flow element by flow element basis (unless you leave the property empty and use the most recent version automatically), this also means that you can mix different pdfToolbox versions if needed.
You could, for example:
- Leave the "Application path" property empty for almost all flow elements. They automatically use the most recent version of pdfToolbox CLI on the system.
- Set the "Application path" property of the flow elements in one Switch flow, or even a single flow element, to have it use an older version of the application. This can help with troubleshooting or overcoming a problem with the most recent version of the application.