Adding action to exsiting preflight / flows

[PPNINJA]

We already have several flows with preflight settings already with custom settings (black to 40/40/40/100 or 100k dependent of print type i.e large format or small format).
We want to add our desktop pitstop action of turning off all overprints of files being submitted and or processed by switch.
Is this doable with current preflight / flows?

[loicaigon]

Hi,

You can add either set the action on the PitStop Server app on top of the defined Preflight Profile.
Or you can add this action as an additional Change Action inside the Preflight Profile.

PROS/CONS:
if you set both Preflight Profile and Action Lists, both are not bounded. So you can remove or change actions from Switch alone.
But downside is that you have more resources to manage.

if you set additional Change in your Preflight Profile, you can even make calls to those actions variable (so they can be run or not depending on a variable, like for ex, your black management based on the production type). But if you want to remove the extra action, you need to edit the Preflight Profile.

[PPNINJA]

Thanks loic

I'd rather have the action set in Switch when the file / files are uploaded in the initial stage as from memory the various colour changes in regards to our black are a few stages after preflight. As we can't control how various files are being supplied to us and also our sales are uploading files without being sighted by prepress, we're going with a blanket approach.
My only concern is that I haven't kept up with how many flows have been created in Switch to handle different conditions / print types

[JimmyHartington]

If you need to integrate a new change in many different flows, you should look into Subflow (https://www.enfocus.com/en/appstore/product/subflow).
With this you could make ONE flow removing the overprint and then integrate it into different flows.
Then you just need to maintain one flow with overprint settings.
And perhaps when time permits make one for the preflight if it is the same for many flows.

There is a short video on LinkedIn explaining it: https://www.linkedin.com/posts/rods-and ... 5KcMdGyp44

[Yolanouse]

If you need to integrate a new change in many different flows, you should look into Subflow (https://www.enfocus.com/en/appstore/product/subflow).
With this you could make ONE flow removing the overprint and then integrate it into different flows.
Then you just need to maintain one flow with overprint settings.
And perhaps when time permits make one for the preflight if it is the same for many flows.

There is a short video on LinkedIn explaining it: https://www.linkedin.com/posts/rods-and ... 5KcMdGyp44

Thanks for sharing, I watched the video but still can’t do it. Can you help me?

[JimmyHartington]

You should start with creating a flow containing your processing you need done in the sub-flow.
In your case removing the overprint. Below is one of mine which converts office documents to pdf.
So it needs the "Subflow - Receive" for getting files from the main flow. And end with a "Subflow - SendBack" to return the files to the main flow.



In your main flows for different customers you can use the Subflow-Main element and choose which subflow it should send the jobs to.

[PPNINJA]

That's what i pictured Jimmy but can several subflows be created and be triggered by certain events such as add drill holes x 4 or 8?

[JimmyHartington]

Yes.

In the Subflow-Main you choose which Subflow you want to send the file to.
And you can have many of those. And all metadata follows the job through the subflows.
So if the amount of drill holes is stored in metadata, you could have one flow to add drill holes. And then it chooses the right action based on the metadata on amount of holes.