We have “generic” processes that rely on the data file, template, data mapper, Job and Output Presets all having the same name (except for the extension, of course).
When the client sends a new Package file, we unzip it and copy the various files to their proper folders.
Is that all that is required? Do the Workflow Services need to be restarted? Does this get the job and output settings file into the proper “repository” (whatever that is, I never have found a good explanation of all the various Connect components, servers, services, engines, instances, etc.)?
To be extra clear: unzip the .OL-PACKAGE file and drop the individual files in the Documents\In folder? Or drop the single package file and Workflow will do the unzipping?
And a restart of the services is NOT required?
And besides this, nothing is needed to get the job and output settings files online, active, and in the proper “repository”?
You can either unzip the file or copy it as-is to the Documents\in subfolder. The Workflow service will take care of extracting its content and store each of them in their appropriate folder.
No need to restart the service, the files are usually processed within seconds.
Workflow 8.7.1 resolved this. In 8.6.1 the files would sit there if they were placed via a program or service. If a USER placed the files, they’d be consumed.
Open a support ticket for that, we’ll need the appropriate logs - possibly the Windows Event Logs as well - to determine what happens in those instances. There is no reason that I can think of why the files would not be picked up, unless the Windows Directory Notification Service stopped working for some reason (that’s how Workflow gets notified of the presence of new files in that folder). The mechanism is exactly the same as it was for PlanetPress Suite.