Unconfigured document generation actions

Due to upgraded Document generation capabilities, you might encounter that previously configured document generation actions appear as unconfigured in published workflows.

Note: The upgraded Document Generation action has no effect on existing workflows or document templates. The unconfigured action must be reconfigured only when editing and republishing the workflow.

Issue and cause

Document generation actions may appear unconfigured when older workflows are opened. The unconfigured icon indicates that the action must be reconfigured if you want to republish the workflow.

The action will be shown as unconfigured due to upgraded document generation capabilities. If a document generation action was last published before the April 2017 improvements of the action, associated tags, and Nintex Document Tagger, they will have to reconfigured before you can republish the workflow.

Resolution

If you don’t want to republish the workflow and use upgraded Document Generation capabilities, then no action is required. You can run the workflow with its existing configuration.

To republish the workflow with upgraded Document Generation capabilities, do the following:

  1. Open the Document Generation action that you want to reconfigure.
  2. Recreate the table tags. For more information, see Add Tables.

    3. Adding table data is now configured in the action instead of the Nintex Document Tagger. You must recreate your tables in the action and then retag your template in the Nintex Document Tagger.

    Note: The previous tag types "Simple" and "Key" are configured in Table Data. Use Internal column name to add your key.

  3. Replace all variable tags in the template using the updated Nintex Document Tagger: Tag templates.

    4. The updated Nintex Document Tagger changed the tag names.

    When your table tags are recreated in the action and your variable tags replaced in the template, the action configuration is validated and the unconfigured indicator disappears.

  4. Save the action and publish the workflow.

    5. The workflow now uses upgraded Document Generation capabilities.