+ Reply to Thread
Results 1 to 6 of 6

Thread: How to use {JC_fw} and {JC_lw}

  • Thread Tools
    • Show Printable Version
    • Email this Page…
    • Subscribe to this Thread…
  • Display
    • Switch to Hybrid Mode
    • Switch to Threaded Mode
  1. February 4th, 2010 08:29 PM #1
    Wick
    • View Profile
    • View Forum Posts
    • Private Message
    Wick is offlineJunior Member
    Join Date
    Oct 2008
    Posts
    3

    Default How to use {JC_fw} and {JC_lw}

    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
    Reply With Quote Reply With Quote
  2. February 4th, 2010 09:16 PM #2
    Wick
    • View Profile
    • View Forum Posts
    • Private Message
    Wick is offlineJunior Member
    Join Date
    Oct 2008
    Posts
    3

    Default

    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
    Reply With Quote Reply With Quote
  3. February 5th, 2010 06:48 AM #3
    Chris Breeze
    Chris Breeze is offlineAdministrator
    Join Date
    Jan 2005
    Posts
    5,112

    Default

    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.
    Reply With Quote Reply With Quote
  4. February 5th, 2010 03:57 PM #4
    Wick
    • View Profile
    • View Forum Posts
    • Private Message
    Wick is offlineJunior Member
    Join Date
    Oct 2008
    Posts
    3

    Default

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

    So, for the time being, could I use {J_fw}?
    Last edited by Wick; February 5th, 2010 at 03:59 PM. Reason: Added first line.
    Reply With Quote Reply With Quote
  5. February 6th, 2010 08:46 PM #5
    DavidB
    DavidB is offlineSenior Member
    Join Date
    Jan 2005
    Location
    Isle of Wight
    Posts
    1,797

    Default

    QuoteOriginally Posted by Wick View Post
    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
    Reply With Quote Reply With Quote
  6. February 8th, 2010 08:22 AM #6
    Chris Breeze
    Chris Breeze is offlineAdministrator
    Join Date
    Jan 2005
    Posts
    5,112

    Default

    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.
    Reply With Quote Reply With Quote
+ Reply to Thread
« Previous Thread | Next Thread »

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Forum Rules