So depending on the licenses you have in Core, totally doable. So after you crop and create the information strip for the cover, you need to SAVE it somewhere (a temporary file). The challenge might be how many of these jobs you process at the same time? Let me explain. In a simple workflow, you would create your cropped information strip, then SAVE it to a temporary folder with a 'fixed' name. So for the sake of example lets call the temp file 'Infostrip'. Maybe you save it in C:\Temp on the core server. So the temp file created is c:\temp\infostrip.pdf
Now, toward the end of the workflow, where you want to 'apply / insert' the file, you use the WATERMARK component in the workflow - set the type to PDF. The watermark can place PDF or image files. So you would (in this example) set a 'fixed' watermark name. You would say only apply to PAGE 1 (or whatever specific page you want). Then you can also set it to put the watermark ABOVE page content or below (you probably want ABOVE). Then you can use the positioning controls to place the image strip lets say on the right side of the page etc.
The reason I ask how many you process at a time, is that if you submit 5 files at the same time, then the 'fixed' filename for your temp file will NOT work. This is because Core could process several of the files at the same time and it would 'mix' or incorrectly place the wrong infostrip file. So in a multiple file processing example, you will need to switch to using a VARIABLE for the watermark name. So you might use the FFCore JobID number for example. This way the temp file is unique for each job and will not risk getting mixed up. However, you will also need to 'manage' the temporary files - maybe a script to erase them at the end of the workflow via a script (assuming you have an Advanced Automation license in Core).
If processing multiple files and using JobID then in the save preset you would use the variable like this:
The default in the save node is $FFwfJob.jobName$ however, you 'could' submit 2 files into Core with the same jobname (which could mix your images). So rather than use that, maybe use: $FFwfJob.Id$ as this will be unique for every job Core processes.
Then in the Watermark set the type to 'PDF' and the PDF file: C:\Temp\$FFwfJob.Id$.pdf
You MUST add the .pdf at the end or the jobs will fail with a missing resource (the $FFwfJob.Id$ will just be a number with no .pdf at the end).
I have attached a sample workflow and a sample file to show the high level concept (in a zip file). Just numbered pages in the sample file. It will take page 1, split it off, Rotate the single page 90 degrees - this step should not be necessary for your workflow - I did it so that when I place the 'information strip' from page 1 you can see it as a rotated page. It will save it to C:\temp with the JobID, then the booklet gets imposed, the watermark placed, then I save the file to the 'save destinations' folder in a folder named CSR Output - again this is not necessary and can be removed. Then lastly it runs an external component (DOS script) that should remove temporary files that are OLDER than 1 day. I did this so that it is a generic cleanup and will not accidentally remove temporary files that Core might be using for other jobs etc.
Note: the attached workflow can only be imported into the latest version of Core (6.2.7).
Note: Please create a C:\Temp directory before running the workflow or the temp files will not be saved.
Hopefully the sample gives you enough to complete your workflow!
Ken
