Case 1: Pass data as Connect XML (client & server)

In this case the data is filled into the Connect schema. primedocs can thus directly trigger the document generation. However, in order to handle the individual data in the documents, primedocs still needs a Connect interface definition. This describes which fields are passed in the call so that they can be placed in the document itself or processed further in predefined logic.

Case 2: Data as Connect XML: Type Data (client & server)

The call with Type Data works similar to case 1, but it does without the Connect interface definition. This affects the possibilities for further processing of data, but at the same time it is helpful if data for a set of templates cannot always be passed identically.

Case 3: Unstructured XML (client only)

It is possible that systems support data export via XML, but cannot format this data in a Connect-compliant way. In this case, there is the possibility to use XSLT transformations in order to transform the unstructured XML directly into Connect XML via primedocs. However, it is important to note that the call of primedocs is subject to certain restrictions.