Skip to content

Why is my document wrong or not generated?

You expect a document in a case, but it is either missing entirely or its content does not look the way you intended. These are two different problems, so work through the matching part below.

First, is it live?

Changes you make during configuration only take effect once you have put them live. Before investigating anything else, make sure your latest changes have been put live. See Put Live.

The document is not generated at all

Is the document part of the process?

A document is only produced in a case if it has been added to the process the case was started with. Go to the process overview screen, open the process, and check the 'Documents' tab. If your document is not selected there, add it and put live.

Is the document's condition met?

A document can carry a condition that decides whether it is used in a case. If the condition evaluates to false, the document never appears. Recheck the condition for logic mistakes and make sure all the information it depends on has been provided.

Isolate a complex condition

If the condition is large, build it up little by little. Start with a small part, put live, and check whether the document appears. Keep adding parts, checking each time, until you find the piece that is wrong.

The document is generated but the content is wrong

A field shows a key instead of a readable value

When you reference the value of a dropdown or a taxonomy, Atfinity gives you the stored key (for example category_b) rather than the readable label. Put a $ in front of the reference to translate the key into its label. See The value of my calculated field has a strange format.

A field is empty

An empty field usually means the information it references was never provided in the case, or the reference points at the wrong information. Confirm the information is asked and answered, and check the field's reference key against the information's actual key.

A calculated value is unexpected

If a calculated information shows a surprising value, the problem is in its formula rather than the document. Open the information and recheck the RuLa expression that produces its value.

The layout or structure is wrong

The structure of a document is defined in ADX. If sections, tables, or spacing render differently than expected, review the document's markup. See What is ADX? and the ADX Elements reference.