If you encounter any issue with the questionnaire, Weagree Wizard in general or generated documents, here is some general troubleshooting advice that may help you discover the source of the problem.

A. ACCESS
Incorrect access rights settings can great limit what any user and see or do within the Weagree Wizard. It can mean that templates or particular functionalities are not available to users when they should be. Even logging in might prove impossible. Depending on the exact problem, it may be helpful to check whether:

a. the user account is active
b. the user account has not expired
c. the user account is linked to the correct e-mail address
d. if single sign-on is enabled, logging in manually by navigating to https://[your portal].weagree.com/login.aspx (instead of https://[your portal].weagree.com/) works
e. the user is assigned to the correct user profile
f. the user (administrators included) has access to at least one of the same user groups as the template (or entity in the party database)
g. zooming out in the browser window, decreasing desktop scaling or increasing the screen resolution reveals any buttons, fields or other elements of the Weagree Wizard

B. QUESTIONNAIRE
Various issues may emerge during the questionnaire. These are typically related to how the template has been inserted or the project has been configured. Depending on the exact problem, it may be helpful to check whether:

a. the newest version of the template has been published, or template testing has been enabled in the user setings
b. the correct culture is selected in the template settings
c. the parties are correctly configured in the template setttings
d. the definitions are tagged
e. the schedules or annexes are tagged
f. the choice trees are tagged
g. the choice options have the correct content
h. the global questions are linked to the correct clauses or choice trees
i. the global question options’ Replaceable text fields contain text
j. the global question options are linked to the correct local choice options
k. the lookup-table questions and tags are pointing to the correct columns
l. text or components that should always be included have not been made dependent on any question
m. the global questions have the correct Ask when first triggered settings
n. the global questions have the correct Pre-answered settings
o. the workflows have been correctly configured and assigned
p. the templates and questions within the project are correctly linked, as appropriate

C. WYSIWYG VIEW AND GENERATED DOCUMENT
It’s possible that the questionnaire’s WYSIWYG view (‘underwater screen’) and the generated document contain errors. Formatting, indenting or numbered lists may be incorrect, or text may be missing, or inappropriate text may be inserted. Depending on the exact problem, in addition to the above, it may be helpful to check whether:

a. in the template settings, the correct house style and dotx-file (Word template) are selected
b. in the template settings, Show annexes in WYSIWYG is enabled
c. in the house style, headers and footers are configured for the various document sections
d. in the house style, headers and footers are (not) differentiated for the first page and subsequent pages of the various document sections
e. in the house style, the party references and other drafting settings are correct
f. the WYSIWYG view styling matches the formatting, indenting and numbering rules of the dotx-file
g. the building blocks and clauses have the correct styling
h. the building blocks and clauses do not contain manual numbering
i. the building blocks and clauses have the correct Formatting deviations settings
j. the building blocks, clauses or choice options do not contain redundant or incorrect HTML code
k. the tables have the correct class styling, column width and behavioural modifiers in their HTML code
l. the tables are not missing column (<td></td>) tags in their HTML code
m. the tables are correctly linked together or separated by <br> or [EOL] tags, lines of text or clauses, as appropriate
n. optional text exclusions are taken into account for the cross-references
o. the cross-reference tags have the appropriate attributes
p. CRM tags (e.g. [weagreecrm.1.relation.name]) and party tags (e.g. [gq.Party1]) are used consistently to refer to parties, but are not used interchangeably