How do I explicitly set the “owner” (user account) of files created by Workflow? Why isn’t the owner set to the user running Workflow services?
Let me confirm what is it you want to know. Do you mean the information that is shown on the printer screen for the “job owner”?
If so, then the answer is that unfortunately, not all printers look at the same information. Whether you send your job through a Windows Queue or a LPR queue or using the LPR of Windows, the information sent VS the one read by the printer is not consistent across printers.
What you need to do is to figure out what information is read by a specific printer (by looking at what display on the printer screen) go back to your Workflow and look where this information comes from.
From there, you will be able to figure out a way to “change” that information for what you want to display. Sometime it will be easy, some other will require more complex processing.
Hope that helps.
No sir. The Windows “Owner” of the file. We are having issues where files created by PlanetPress running under user account “pdsupport_rs” do not have “pdsupport_rs” as the OWNER. Those files then cannot be moved/renamed by any other account, even other Adminstrators, without explicitly taking ownership of the file. We have UAC disabled.
So my question is two-part: why aren’t files created by PlanetPress “owned” by the user account running the Workflow/Connect services? Secondly, is there a way, in Workflow, to explicitly set the “owner” of the file, so that we can workaround the problem.
Files created by Workflow are not “owned” by default, which means they inherit their folder’s ownership properties. That’s the default Windows behaviour. If you want to make them accessible, store them in a Folder that’s accessible to all users.
If you don’t want to do that, you can use Workflow’s Call External Program task to launch a Command-Line window that calls the TAKEOWN command. Here’s an example: https://superuser.com/questions/116625/recursively-change-owner-windows-7
Thanks for all the good information here. It took me down the proper rabbit hole.