Page 1 of 1

Adding information at a SwitchClient checkpoint?

Posted: Mon Oct 03, 2011 5:32 pm
by mwinker
In one of our flows, imposed PDFs arrive at a checkpoint where the press operator can open and inspect the file in Switch Client before releasing it to the digital press RIP. Th then has the choices of:



1) sending it to the RIP

2) sending it to the rubbish bin

3) sending it to a "problem job" folder



#3 is where I'd like to be able to ad information and send the job back upstream to prepress. ie: no bleed, missing art, or something like that. Probably with another client alert for the prepress department.



When the PDF is opened from the client, changes like notations can't be saved to it. I'm guessing because (according to the manual) the backing folder is auto-managed. I'm also thinking that giving read-write access to that folder might not be a good idea. Can I do that?

I know they could save the file locally and replace it, but I'd rather minimize the steps.



Or… It looks like there may also be a way to require a metadata entry at the checkpoint. Can that be done without disturbing the metadata already traveling with the job? It's unclear from the manual and I'm not much of a programmer, yet. Could it be done by just adding fields to the existing metadata?

Adding information at a SwitchClient checkpoint?

Posted: Tue Oct 04, 2011 11:37 am
by caio
When the PDF is opened from the client, changes like notations can't be saved to it. I'm guessing because (according to the manual) the backing folder is auto-managed. I'm also thinking that giving read-write access to that folder might not be a good idea. Can I do that?



YES I DO IT. Whit SwitchClien8 I save whit name in the auto-managed folder and refresh the switchClient

Now in the switch 10 the client as a button to view job and another button to edit job





It looks like there may also be a way to require a metadata entry at the checkpoint. Can that be done without disturbing the metadata already traveling with the job? It's unclear from the manual and I'm not much of a programmer, yet. Could it be done by just adding fields to the existing metadata?



IS NOT SIMPLE......

the metadata that arrive to ceckpoint as a name (usually 'xml'). If the "name of metadata" in the ceckpoint configuration is the same, the ceckpoint overwrite the metadatafile (in the metadata you will have only ceckpoint field). then....

1) you call the metadata ceckpoint whit the different name. In this way the job will have two different metadata file associate: the old metadata File and the new metadata File

2) you insert in the ceckpoint field all value you need (the new and the old)



I hope help you.

ciao!

Adding information at a SwitchClient checkpoint?

Posted: Tue Oct 04, 2011 6:14 pm
by mwinker
Thanks Caio,



I'll probably try the first option since it's pretty simple.



Mike

Adding information at a SwitchClient checkpoint?

Posted: Fri Oct 07, 2011 12:33 pm
by diwu
SwitchClient 10 indeed has those buttons to view or edit a job.

Viewing comes down to opening a read-only version of the job.

Editing opens the file in it's default application and when saving, the file is replaced in the Switch backing folder so you can process the job right away.

If after saving the file you would notice some problem you can easily revert the job to original. Finally SwitchClient 10 even takes care of user management by automatically locking the file, making sure that no one else can process it when you're editing the file.

All together i definitely recommend using SwitchClient 10 instead of changing the rights of auto managed backing folders.



Updating metadata in a checkpoint became quite simple in SwitchClient 10. On the Switch side where you're designing a flow with submit and checkpoints you will notice that when defining metadata fields for a submitpoint you can add or remove fields. When setting up a checkpoint you'll notice a 3rd option next to adding or removing fields. That's the option you need to re-use or update metadata from a submitpoint. You just have to select the fields you need and define if you like to display or hide that data and define if you allow those fields to be updated or keep them read only.



hope this helps

Dieter