Structure without eventsThe following figures show the maximum number of hierarchy levels that can be build with primary links.
The order of the levels is predefined. You can omit levels but you cannot change their order.
The following figure shows an example of an hierarchy without job data records.
The following diagram shows that Appointment data record types must be linked with Projects over a primary link; all other data record types must be linked with Jobs.
Primary links are efficiently used, for example, for project management tasks if you want to assign all data saved in your system to a certain project and the project itself is assigned to a certain customer (address).
For the customer with the Interested in product A project, create a job called Events. Now link appointments for a presentation, the customer's visit to a briefing, a cover letter, phone calls, and so on, to this job.
For the suppliers with the project Print brochures June, create a job called Prepare print. Link all appointments with the design studio, the print agency, the offer, and so on.
The employee creates the jobs Criteria and Implementation. Now link the meetings with colleagues, documents containing suggestions, e-mails, and so on, to these jobs.
There are now buttons available on the General tab for entering primary links in the data record window. Entered primary links are displayed in the data record window.
The Tree tab in the data record window and the Tree view show an overview of the primary links' hierarchical structure. There are also functions available for editing primary links.
You can also view all links and primary links on the Dossier tab.
