print organizer: out directory

There is a configuration variable that defines the destination of the printed files.

MS_PLTFILES. The variable is the same in both V8i and CONNECT versions.

Hi,

I use the configVar, but every pset needs to be placed in a separate output folder,

the var goes to the main output- folder for prints, but I want to specify a pset folder.

The result you are looking for depends on how your workspaces are setup. Do you have project specific workspaces setup or just one "generic" workspace for everything. You need to be specific about how your workspace is configured because it will change the suggestions.

You state that every .pset needs to be placed in a separate folder. Do you mean that the .pset has a lot of different plan types contained within and each plan set should go to a different folder?

Maybe it would help if you write down a step-by-step workflow here so we can better determine what your end result should be.

Hi, mwlong,

all projects are building projects, - we use a separate  project config for each project
all output files (eg. pdf prints) are directed to our "shared directory"
but we want to specify in this directory a separate directory for each publication day, or sub-contractor (printed to share the files)
so the beginning of the path is OK (config var in de pcf, but the detailed destination shout be in the pset file

Rik

You might need to look into using Named Expressions or maybe some type of Design Script. I am not too familiar with either of those so I do not know if that is an option.

Personally I would have MS_PLFILES set to the root of your shared directory where you want your output to be placed. Someone would need to go to that directory and add the necessary folder for whatever publication or sub-contractor is needed. At least you will be directed to the root folder so you do not need to navigate through many directories to find the correct folder.

There may be another way to accomplish what you desire, but I like to keep it simple. The root directories are always a good place to start.  As long as you inform your users of the process there should not be a problem with this workflow. Hold people accountable who do not follow proper procedure.

You might need to look into using Named Expressions or maybe some type of Design Script. I am not too familiar with either of those so I do not know if that is an option.

Personally I would have MS_PLFILES set to the root of your shared directory where you want your output to be placed. Someone would need to go to that directory and add the necessary folder for whatever publication or sub-contractor is needed. At least you will be directed to the root folder so you do not need to navigate through many directories to find the correct folder.

There may be another way to accomplish what you desire, but I like to keep it simple. The root directories are always a good place to start.  As long as you inform your users of the process there should not be a problem with this workflow. Hold people accountable who do not follow proper procedure.