Protocol

Configure Protocol, if you want to have logged every EPaper output in a table. Each EPaper output generates one row in the feature service table (that has to be in a Enterprise Geodatabase), which contains the mandatory information creator, creation date, the EPaper template name and the object key(s) of the selected object(s). It may contain further optional information.

Protocol configuration

Property	Description
Table ID	Table ID of the feature-service table used.

Protocol property

Note: Feature access has to be active in the map service that contains the table.

Activating Feature Access

The fields of the table must have the following data types:

Mandatory fields

•CREATOR: Text

•DATE_UTC (creation date according to coordinated universal time): Date

•EPAPER (name of ePaper template): Text

•FIDSET (object IDs): Text; if the user selects more than one object when generating an ePaper, the object IDs written in the field are separated by semicolons (;).

Optional field(s)

•FIELD_1: Text

•FIELD_2: Text

•FIELD_n: Text

Note: It is also possible to name the field names otherwise.

When creating a new node Protocol in SynerGIS Informationssysteme - Technical Documentation Team the child element Protocol fields is automatically created. This node contains the 4 mandatory Protocol fields. If needed further Protocol fields can be added, which were defined in the table.

Protocol field configuration

Property	Description
Field name	Field used when creating the protocol. The field name has to be identical with the defined field name of the table.

Protocol field property

In order that the optional protocol fields are filled, they have to be assigned to function fields. In the configuration seen below the field value of the function field Disclaimer is written in the field FIELD_1.

Assigning a Protocol field to a function field

The following image shows an exemplary Protocol table with 5 logged ePaper outputs. Each row represents one output.

Protocol Table view in ArcMap