The template is imported and shown with the extension .err and the template is not used by Workflow and Service
This must be a problem with the new Workflow version, since we tested this with templates that are unchanged and could be imported into earlier Workflow versions without any problems. This bug came to our attention, when we had to do a minor change in a PP7 template. Wer tried to import multiple PP7 templates and they can no longer be imported.
This creates massive problems for us, since we are in the early stages of the process to migrate invoice templates to Connect (that process will take months parallel to our usual workload), but still have to do changes in the old PP Suite 7 templates. The ability to import PP7 templates into Workflow was a major selling point for us to decide to buy Connect.
How can we again successfully import PP7 templates into Connect Workflow?
Edit: the templates worked flawlessly in the past and show no error messages in PP7 Designer console.
The details for the error are usually displayed in the Messages pane when you import the PTK file. There is no additional info.
When you say it worked flawlessly before, I assume you mean in PlanetPress Suite. Have these templates ever been imported in any version of Connect? (You mention it worked in previous versions of Workflow, but didn’t specify if those were PPSuite Workflow versions, or Connect).
You also mention the issue came to your attention when you had to make changes to a template. Are you able to import the version of the template before the changes?
My gut feeling - and I may be wrong about this - is that some resource that used to be available in PPSuite Workflow is missing in Connect Workflow. A font, or a resource in the Virtual Disk, for instance. And that would be why Workflow is unable to import the PTK.
There are no messages in the message pane, I checked that first. The message pane stays empty when I import the template.
I meant it worked flawlessly in every Connect Workflow version before 2023.1. We switched to Connect Workflow from Suite way over a year ago. Import of templates edited in Designer 7 into Connect Workflow always worked until now (we had to do that often).
I tried to import an older backup version of the template that worked flawlessly before 2023.1 and was unchanged for months. The same problem.
I tried to import other templates that were not touched for months or even years, they have the same problem.
I do not believe this has an external cause, it started with Workflow 2023.1.
OK thanks, that should make it much easier to investigate. Would you happen to know what version of OL Connect you were using before you updated to 2023.1? Knowing this will allow us to focus solely on the changes made between that previous version and the current one.
As you might well imagine, our QA department runs a series of regression tests with any new version of the application, and they haven’t reported any issue with the import of PTKs. Ever since your original post on the topic, I have tried importing PTKs of my own on my system, and I have not run into any issue (I even imported a fairly elaborate PTK that I created back in 2004 - which already shows how old I am!).
Anyway, if there is any template you could share with me (through private message), that would help us replicate the issue.
We always updated relatively fast because we hoped that all the bugs from earlier versions we reported would be fixed in newer versions.
I will have to talk to the project manager if we are able to share templates because they may include privacy problematic data we cannot share because of GDPR.
I have already updated @Xanathon on the status of this issue, but if anyone else runs into it, here’s the explanation:
The issue only occurs when you import a PTK/PTZ while the Workflow service is running! . And the problem only occurs if the template contains a PDF resource.
If you turn off the service (or if your template does not contain a PDF resource), then you can import the file. Once imported, you can restart the service if you stopped it, and everything works as expected. That’s the reason why it worked every time on my machine: my service was not running!
We will make sure to address this issue in the next release of OL Connect.
Thanks to @Xanathon for helping us investigate the issue… and for his patience!
I’m having a similar situation if I submit a form to Connect Workflow from PPS Designer. The only way I can get around it is to change my PDF in the document to and image. I am currently on the most recent version of PP Connect.
