Workflow, index page, many DCRs, etc.

Andy Knipp

OK, so the good news is that if I am dealing with an issue like this then my implementation must be doing pretty well.

I have a page that reads several hundred DCRs and builds and index page. I only use 1 workarea and like to build this when a DCR is submitted. The workflow steps (that matter) are generateHTML, deploy to test, review, submit, production deploy.

The issue is when to build the index page and where to read from.

Currently I read the WA DCRs and build the index page in the generateHTML section of my workflow. The obvious issue is that unapproved changes may show up on the index.

If I read the DCRs from the Staging area, then the content being reviewed is not in the index and will not be until the next DCR is submitted.

So my thought is to read the DCRs from Staging unless the specific is attached to the job that the index page is. Since I am using iwpt_compile, that is not trivial because the TPL knows nothing about the job.

Other options are to do a generateHTML after submit (for that index page) but then the reviews happen with the updated index. Not stellar.

I could just process the index page every night, hour, etc, so that is is always out of date a bit.


Opinions ? Thoughts ?