How to use {JC_fw} and {JC_lw}

[Wick]

I am trying to create a download path that uses two words from the job code to create a folder and subfolder respectively.

I set it up this way:

E:\Images\Work\Storer\{JC_fw}\{JC_lw}

But since {J} is not present, DLP will not prompt for the job code. And if {J} is present in the download path, I cannot separate the words asI want to per above. Is there any way around this?

-wick

[Wick]

OK. I came up with this workaround based on help received here.

Instead of trying to put the {J} code into the download path, I buried it in the IPTC data associated with that user profile.

Now DLP prompts me for the job code and I can use the fw and lw codes in the download path as I wanted to do.

If anyone has a more elegrant solution, great. If not, this will work for me.

-wick

[Chris Breeze]

I think I've found the problem: the code was checking for {J_fw} and {J_lw} not {JC_fw} and {JC_lw} when checking whether the job code is used. I'll fix this in the next release.

[Wick]

Always satisfying somehow to know it wasn't operator error.

So, for the time being, could I use {J_fw}?

[DavidB]

So, for the time being, could I use {J_fw}?
Don't think so; from what Chris says, different routines are expecting different values; in those circumstances, it's almost always best to stick with the right (= intended, = documented) one. Actually, I thought your workaround was quite neat, and filed the idea for future reference.

David

[Chris Breeze]

No, it's just a minor bug. When testing for whether one of the job code tokens is being used it's looking for {J}, {J_fw} or {J_lw} when it should be looking for {J}, {JC_fw} or {JC_lw}. I'll fix it the next release, but in the meantime adding {J} in an unused IPTC field is a good workaround.