“doesn’t the nodestate table change during a reconcile? If it did, wouldnt that force a incremental publish for each elist item? That probably isn’t a good thing…”

During Reconcile nodestate table is updated, but if you set up monitoring on date edit field, Event Manager will fire an event only if reconcile brings new data (like import).
Moreover, incremental publish publishes all elists changed since last incremental publish (not reconciled, but with new\changed data). Detecting those elist with data change is internal cognos process

“Does this option hear resolve that problem? Where did you find this option?”

Incremental publish works only after intial table layout publish and if application structure changes (new dlists,cubes) after initial table only layout publish — incremental publish stops working until next full table-layout publish. That was a problem in 8.2, you usually had to republish applications after synchronize.
Option mentioned in the post adds a gtp step, that detects whether such structural occured and if they happend, starts a full table-layout publish automatically.

PS: Too many mentions of “publish” Let me know if this answer isn’t clear.

I read with interest your blog entries regarding reporting in near real time against Contributor with a incremental publish…

I havent tried it yet, but will soon.

I had one question/concern…doesn’t the nodestate table change during a reconcile? If it did, wouldnt that force a incremental publish for each elist item? That probably isn’t a good thing…

Does this option hear resolve that problem? Where did you find this option?