Your Nintex DocGen works. But is it healthy?

❮ ❯

1 / 9

The short version: long-running installs accumulate sediment — cloned package versions, missing template files, licenses nobody consumes. The free DocGen Health Assessment audits six areas hands-on and hands you a written report, quick wins, and a prioritized plan — yours whoever does the work.

The deck makes one argument in nine steps, and it survives summarizing. A working DocGen install is not the same as a healthy one: documents still generate while the estate underneath accumulates cloned package versions, templates whose source files have gone missing, delivery options nobody can explain, and licenses that renew without being consumed. None of these stop a button from working today; each makes the next admin handover, the next org change, and the next audit more expensive than it needed to be. The middle slides walk the six areas the free health assessment examines — packages and versions, templates and their files, delivery configuration, usage against licensing, error patterns, and ownership — with the quiet symptom each area shows when it needs attention. The closing slides explain what you receive: a written report that grades each area plainly, the quick wins an admin can clear in an afternoon, and a prioritized plan that is yours regardless of who does the work. For teams that want the same six areas watched continuously rather than annually, the final slide introduces the Horus Eye DocGen module — and for teams weighing a move from Conga instead, the honest answer is that this deck is not that conversation: the migration page is. Either way, the deck’s standard for itself is the same one we ask of the install it examines: every claim traceable to something observable, and nothing asserted that an afternoon in your own org could not confirm.