1. Knowledge Base
  2. Best Practice Tips
  3. Utilize custom fields whenever possible

Utilize custom fields whenever possible

The key principle behind Ardoq is “data first”. Although the rich text editor is also a field (Description), the absence of specificity and format makes it unsuited for targeted analysis or for impacting on the visualizations. Therefore, although the rich text editor is sometimes necessary, its use should be kept to a minimum in order to get the full potential out of Ardoq.

Whenever data could fit into a custom field, one should take the time to create the field. For instance, if you are documenting an application landscape and assigning “ownership” of each system to a person, why not create a field called “Owner”, and format it as an email address? This way, you can filter your data based on ownership.

In this example, we show you how we use a “milestone” field to visualize different project phases, something that would not have been possible if the milestones were merely described in the Description field.

Was this article helpful?