I have a coupld of Route sin my workflow.
One of the Routes has about 10 or so branches.
Most of my branches do same thing, using same nodes but have different sizes for imposition and watermarking.
I need to know when I put a job through, which branch that job went through.
How do I find this?
I am new to this version, am upgrading from a very early verison of freeflow, very early version.
Early version you can actually see the job goign from one node to the other so you can actually follow the job as it is going through.
FFCore has never shown the job flow through the workflow. We did that with FFProcess Manager. However, that functionality was not carried forward due to performance considerations.
The Job Properties (visible when you select the Info button in the Job Management screen) show the last preset that was used for the specific job. They also show the last imposition preset as well as the current dimensions of the job.
Yes, we still using FFProcess Manager here. Setting up now for this new FF Core though. That feature of folowing the job flow is really nice though.
The way I have the workflow set up all routes have their own imposition presets but then they all funnel back into the same imposition preset. Looking at properties of the Job doesnt give me the info I need.
I have attached image of our workflow.
There's no way to follow the job as you could in FFProM.
However, we store a variable for the last Imposition used in the document. You could add that to the document using the watermark after the first imposition. Alternatively, you could also add that to the name as you are saving the RIP files.
Are you trying to follow the workflow for testing purposes? If I'm understanding correctly, that is the point.
I think a good way to do this in FFCore would be to create a save node off of major points and start with a document where you have the intended process already mapped out.
What I do is create a document that I know will fail at a predetermined point and a save function that saves to a particular folder at a certain point. When the file populates in the save folder, I know it is running the intended path.
It's a bit more work, but it gets the job done. If I didn't understand the question correctly, this is a totally from left field answer.