Document Coding Best Practices Pinned

To become an expert in document coding, it takes time and practice. Add these tips and tricks to your toolkit to get there faster!

Use an entity or test entity that you’re very familiar with! 

The better you know the data, the easier it will be to find the corresponding variable when you’re first starting out in your coding journey. Complete the missions here to learn how to create entities from scratch - make it fun by personalizing with your favourite pop culture references! A fan favourite at Athennian is taking details from the American legal drama 'Suits' - we've incorporate Pearson Specter Litt LLC many times when testing.

Populate your entity with lots of different kinds of data! 

The more information you have available entered into Athennian, the more precise your coding can be. Having many different scenarios to test means your document will perform well from record to record! 

Get familiar with the different document generation paths in Athennian! 

Using the correct document generation path for your specific document will ensure its accuracy for all users. This will help guarantee that the variables you’re using to code are actually available where the document is meant to be generated. *Beware: different document generation paths can affect which variables are available for coding!

Learn to use the Developer’s Console, and use it often! 

This powerful tool can be a way to learn the different variables in Athennian, troubleshoot a document coding error, and even help you understand the shape of data as it’s stored in the software! Open it before you merge any document to view more detailed error messages, or simply use it to review what variables you can use in your chosen document generation path. Check out our Help Doc for more on how to access and use the Developer’s Console.

Keep calm and test on! 

Make that template work - just because it generates flawlessly with one entity record doesn’t always mean it will work with all of the others, especially if you coded it with your favourite test entity! Try it with lots of different records, or rearrange your test data to make sure your document performs well under pressure. Remember: the best document, much like any professional, is one that is adaptable to its circumstances.