Does someone have idea how to regenerate/reprint pages that are destroyed later in production?
We are storing all generated content sets in database with unique ID so retrieving them is not a problem. Also all our documents have unique document number within job stored in document metadata. My idea is to retrieve content set and compare unique document number in metadata with list that need to be reprinted. Retrieving items is not a problem, but how to check document metadata and exclude page from output?
Ley say I had generated 10 records (pdf) from first run. If I want the same exact copy of 1,4,6 only to be regenerated with exact content but only generate three pdfs , how would I do this?
I am aware of Retrieve Items , but every time I retrieve with content set ID, I would still get same amount of pdf from example above which is 10 not 3.
Wow, I never noticed a reply from Phil so our conversation ended 3 years ago
What we did for this problem is that we “print” small json text at the beginning of the page with white color so it’s not visible on paper. In that json we put a unique document number, and if some document must be reprinted all we need is that number.
We’ve created another workflow process that extracts that json with alambic API, compares the number in it with the needed document, and if it matches prints the entire document as generated for the first time. Since that json is in the same position thru all our documents/jobs same workflow works for every job. Simple, but very effective.
From your explanation, Im assuming you would still need the full PDF? And you look for that unique document number, in the full pdf and extracts them? Then you would merge them as 1 pdf output as reprint.
