Installation guide

Zetadocs for NAV Installation Guide
This edition 5
th
December 2012 © Copyright Equisys plc 2012 All trademarks acknowledged All rights
reserved
Page 87
14. Zetadocs Delivery Plus
The Zetadocs for NAV Addin can be split into 2 main areas, data and processing. The installation guide dealt
primarily with setting up the data that would determine our report formatting and send information when
sent to the Zetadocs Client. We saw how reports could be grouped into Document Sets which share a
common rule for formatting and archiving and we saw how rules can be stored which alter formatting and
send information dependant on who we were sending to. It is assumed then that we have a good
understanding of the information involved in sending a report using Zetadocs for NAV. In this architectural
overview the process of collating the sending information, which we refer to as the “Send Results”, is
explained. This includes a breakdown of the main processing areas and their use in integrating with NAV as
well as an insight into the customization potential and extensibility of Zetadocs for NAV.
14.1 Understanding the SDK Framework
Before continuing it is recommended that you read the Zetadocs for NAV SDK Primer section of this
document.
The three elements to the Zetadocs for NAV Delivery Plus SDK are:
1. Interfaces
 NAV Reports
o Reports need to be modified to call the Zetadocs for NAV Core sending codeunits.
Instructions on this are available in section 4.6 the Zetadocs Report Modification
Tool.
2. Zetadocs Core Codeunits
 Zetadocs Send codeunit
o This codeunit provides functions that are called by the Interfaces.
3. Integration and Customization Codeunits
 Zetadocs Send Integration codeunit
o This codeunit provides functions called by the Zetadocs Core codeunits to
integrate Zetadocs Delivery functionality into bespoke records or other areas of
NAV beyond Sales and Purchase Order Processing
 Zetadocs Send Customize
o This codeunit has functions called by the Zetadocs Core codeunits to allow the
developer to implement bespoke business logic and delivery and archive settings.
14.2 Process Flow
Now let’s look at the flow of data that occurs when sending a report. The following diagram helps to
visualize the process and will aid us in discussing the relevant parts of the product.
As you can see from the diagram it starts with a NAV report that has been modified for Zetadocs for NAV. A
report is generally based on a set of records that are used to produce some report output, a document for
each record. The records contain information that relates to a contact and possibly a company, to whom the
report should be sent (i.e. the recipient). Sometimes that information can be a direct table reference to an
existing table that represents a contact or company for example, or it may contain some other form of
references which can be used to find the contact information from another source. This could be a look up
table of some sort based on some bespoke logic. The Zetadocs Send Results Gen codeunit is the central
processing controller and builds a runtime list of send results in a temporary table of type “Zetadocs Send
Result” for each record in the report.