you have mail' attachment configuration

The configuration of the attachments is done directly with an XML editor. Please make sure that such an is installed on the computer and linked to the .xml file extension file extension on the computer where you want to edit this configuration. When you click the button "..." at the input field Attachments, an XML editor with the file extension an XML editor with the current configuration is called up directly. Adjust this and save the file, this will be automatically automatically added to the message.

Specification XML for attachments

In the following, the structure of the configuration as a whole and per attachment type is explained below. Please make sure that you enter the XML document correctly and wellformed. The XML structure has a root element, and within the root element for each attachment definition a repeating element.

If the special character < or > occurs within an attribute or the data of an element contains the special character < or >, you have to display this character as in HTML, so that it is not interpreted as an XML control character.
For the character < use &lt;
For the character > use &gt;

<attachments>

<attachment .......>

......

</attachment>

</attachments>

The 4 possible attachment types are described below. are described. All of them have common elements and partly specific attributes. In addition, the element "Naming" is special, as it can be composed can be composed of fixed variables and data variables. It is important to note that for each attachment an additional definition with the <attachment> group must be made, so if, for example, 2 CxReporte or 3 Native Files are attached, then the element <attachment> must be made per report and per native file. be made. Please note the data types which are as follows. used:

Appendix CxReport

This is a CxReport, which is a report of the report of the CodX PostOffice system, which is called up in the background and in the background and generates a report in PDF format from the data PDF format, which is then used as an attachment.

<Attachment Type="1" Summarizing="true">

<CxReport GUID="7A3D1830-C17B-4494-9CF2-01C6E4AB70CF"/>

<Naming>Appendix_&lt;%SBB.strUPOC%&gt;.pdf</Naming>

<Param Name="lID">&lt;%lID%&gt;<Param>

<param name="UPOC">&lt;%strUPOC%&gt;</param>

</attachment>

Appendix Native File

This is one or more arbitrary files from the files from the file system of the computer that is running the 'you have mail' system and generates the messages. Please note that this is usually the computer running the CodX PostOffice application server. So these files must be be accessible on this computer, or you can use as path a network path a network path that is accessible from the application server.

<attachment Type="2" Summarizing="true">

<NativeFile FileName="" Path="" FileMask="" Recursive="false" ZIPFileName=""/>

<naming>&lt;%orgfilename%&gt;_&lt;%datetime%&gt;.&lt;%orgextension%&gt;</naming>

</attachment>

Attachment broadcast image

This attachment type is all the images of the desired type of the desired type, which are deposited to a transmission. All all broadcast image types are supported. These images are saved as attachments with the the same file type as they were saved as an attachment.

<attachment Type="3" Summarizing="false">

<image Type="9" PDF="true"/>

<naming>&lt;%strUPOC%&gt;_&lt;%counter%&gt;.&lt;%orgextension%&gt;</naming>

</attachment>

Annex DM Document

This attachment is a document from the CodX PostOffice document management system. This can be different documents from different modules, e.g. a complaint attachment or a document from the DM etc.

<attachment Type="4" Summarizing="true">

<Document UPOC="" ReferenceUPOC=""/>

<naming>document_&lt;%datetime%&gt;.&lt;%orgextension%&gt;</naming>

</attachment>

Naming

In this element the names of the attachments are defined. These can either be entered directly as text, or they can be composed using substitution characters. These substitutions can be used arbitrarily and mixed with text. text. We distinguish between predefined replacement characters and data replacement characters. These can also be used in all other elements elements, they are replaced at runtime by the data found in the of the trigger and data query at runtime. The following predefined replacement characters exist: