I have a Workflow with an SDK Script that generates a CSV to a Network Location. When I test the Script in the Script Editor, I am able to save the CSV, but when I run the actual Workflow I get an error that the path is denied. I am logged in as a user named Laserfiche, and I can access the folder. And the Workflow Service is running as the same Laserfiche user. So why wouldn't it be able to save?
I have also tested it with the location mapped to a drive named "I." Again, I can save the CSV in the Script Editor, but when I run the WF, I get an error. This time, "Part of the path was not found."
One possibility I've seen is that the path I'm currently using may not be the server's true name, but an alias. We are looking into this. But I still find it odd that the Script Editor can function if the Workflow cannot. Even if we get a new path, I'm not sure if the same issue will arise or not. Anyone seeing an issue I'm missing?
Update: The client has told us we have the correct server name, but it is not a Windows Server, it is an IBM iSeries Server. Should that change how we format anything in the Script?