Benches Uncategorized

3

Custom Workflow Variables Broken

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

You're supposed to be able to define custom metadata by doing the following:

1) Add the name as an item in the userRequirements array of your workflow's template.plist
2) Writing a key/value pair in the metadata.plist you submit along with a file to a workflow.

While the custom metadata shows up in Server Admin > Podcast Producer > Settings > Properties > Custom Properties, and appears in the generated user_metadata.plist file in the Recordings directory, they are completely blank in the properties.plist file.

This properties.plist file is where all the workflow variables are written to, and read from by your workflows. These are $$Base Path$$, $$Admin Email Address$$, among others.

I haven't been able to see any successful use of this feature, and have seen several people just as perplexed as I am at this broken functionality, yet, I've not seen any solution, nor heard any admission by Apple that anything is wrong.

We currently are putting in an Enterprise Support ticket with Apple for this, but I wanted to see if anyone on here had:
1) run into this issue, and/or
2) been able to fix it.

Thanks,
David Poindexter
Indiana University

3 replies

Sign in or join Beachball Help to reply.

  1. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I have seen the same issues on 10.5.8 Server. Although some custom variables still work, others do not. Very frustrating, did you get any further with this?

  2. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Sorry for such a long delay. Yes, we did manage to get through this, and I'll detail how we did it...

    You cannot pass workflow variables through, still. That hasn't changed, and for security reasons, I'm told it will never change. (Note, we're still using 10.5, and haven't tested 10.6, so YMMV).

    When you stop a recording, you write a metadata.plist to send along with it upon submission. This contains your usual author, title, etc info. I use a script that writes some "extra" information into that file when we stop the recording.

    Upon submission, this metadata.plist is copied and renamed into the recording directory ($$Base Directory$$) as "user_metadata.plist"

    So, the step in my workflow where I call a ruby script from my Tools directory, I just pass in the $$Base Directory$$ variable as a parameter. Inside the script, I have that as a starting point, and can find the "user_metadata.plist" which contains this "extra" information I need to complete the task.

    Also, I don't consider this a workaround, since that same tactic can be expanded to solve a great many problems in the future. For example, if you want to "tweet" the release of an episode, you can store the users twitter account info in that file, and parse it in a step of the workflow. Just an example.

    Hope this helps someone who stumbles by it.
    --
    David Poindexter
    Developer
    Indiana University

  3. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Figured out a different solution and posted it in this thread for future searchers.