The database connector is installed as a service, and for its proper functioning it is necessary to configure 2 files:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <appSettings>
    <add key="Application Name" value="XOne ITF Advanced" />
    <add key="Configuration Path" value="C:\Archivos de programa\XOne\XOne ITF Advanced\ITF Config.xml" />
    <!-- Activar Seguridad SSL en el envio de correo -->
    <add key="mailSettings.EnableSsl" value="true" />
    <!-- Tiempo estipulado en segundos para reenviar un mensaje que ya ha sido enviado -->
    <add key="mailSettings.RetrySend" value="300" />
  </appSettings>
  <system.net>
    <mailSettings>
      <smtp from="">
        <network host="" userName="" password="" />
      </smtp>
    </mailSettings>
  </system.net>
</configuration>

<xml>
	<!-- IMPORTANTE MANTENER COMO ESTAN LAS MAYUSCULAS O MINUSCULAS PARA LOS SETTINGS DE LA APLICACION -->
        <!-- Descripción Atributos:
           name: nombre de la interface
           versión: versión de la interface para su mejor visión en el visor de sucesos
           disabled: con este parametro activaremos o desactivaremos la interface
 
        -->
	<itf name="ITF 1" version="1.0" disabled="false">
                <!-- Para controlar el intervalo con el que se ejecuta la aplicación, tenemos dos opciones: Interval o cron-expression.-->
                <!-- Solo se debe de quedar activo uno de los dos nodos. Si estan los dos, predomina el Interval. -->
                <!-- El Interval da el tiempo en segundos. Tiene la limitación de 21600 segundos -->
		<item name="Interval" value="1"/>	
                <!-- El cron es mucho mas amplio y es el que se debe utilizar, ya que tienes un control total del tiempo. -->
                <!-- Mirar este enlace para documentarse: 
                 http://www.xoneisp.com/xonewiki/doku.php?id=f.-herramientas:f02.-xonemonitor:start#anexo_i_expresiones_cron              
                -->
                <item name="cron-expression" value="0 0/30 7-20 ? * *"/>
		<!-- ruta donde se encuentra el xml de configuracion de aplicacion-->
		<item name="XML Path" value="C:\Archivos de Programa\XOne\itf\itf1.xml"/>		
		<!-- Valor maximo de valores cacheados. Los valores que cachea son los filtros a buscar en el mapval -->
	        <item name="MaxCacheValues" value="15000"/>    
		<!-- Valor del MID con el que escribiremos en la base de datos -->
		<item name="MID" value="999"/>		
		<!-- Cuenta de correo a donde queremos que reporte los errores y advertencias que aparezcan -->
		<item name="Mail To" value="correo1@xone.es"/>
		<item name="Mail To 2" value="correo2@hotmail.com"/>
		<item name="Mail To 3" value="correo3@gmail.com"/>
                <!-- Creacion por defecto de la tabla interclient_sync_tables en caso de no existir en la base de datos, para control de cambios -->
		<item name="Inter Sync Create" value="CREATE TABLE interclient_sync_tables (ID int(11) NOT NULL Identity(1,1),   OBJECTNAME varchar(150) NULL,LASTMODIFIED datetime NULL, PRIMARY KEY (ID))"/>
 
                <!-- Parametros de conexion de tabla de eventos. 
                     Si queremos pasar el log a Base de datos en lugar de hacerlo en el visor de sucesos.
                     Habría que poner el nodo itflog en cada itf que queramos guardar log en base de datos.
                     En la siguiente línea, name especifica el nombre de la tabla de log.
                -->
		<itflog name="ITFLOG" provider="System.Data.OracleClient" connstring="Data Source=BASEDATOS;User id=USUARIOQUESEA;Password=CLAVEQUESEA"/>
 
		<!--  Estructura de la tabla ITFLOG:
 
				Nombre       Nulo     Tipo           
				------------ -------- -------------- 
				ID           NOT NULL NUMBER(11)     
				APPNAME               VARCHAR2(50)   
				APPVERSION            VARCHAR2(50)   
				EVENTDATE             VARCHAR2(50)   
				EVENTTYPE             NUMBER(4)      
				TRANSFORM             VARCHAR2(50)   
				EVENTMESSAGE          VARCHAR2(4000)
 
		-->
	</itf>
 
	<itf name="ITF 2" version="1.5" disabled="false">
		<item name="Interval" value="1"/>
		<item name="XML Path" value="C:\archivos de programa\XOne\itf\itf2.xml"/>
		<item name="MaxCacheValues" value="1000"/>
		<item name="MID" value="777"/>
	</itf>
	<!--
	...
	<itf>
	...
	</itf>
	...
	-->	
</xml>

Configuration file where the integration itself will be carried out between the source system, the client's system, and the XOne system.

Once it has been decided in which order the data are transferred, each of the transform nodes begins to be defined, which are the ones that carry out the transfer of data from one table to another.

Node in which the source and destination tables of the data to insert are taken.

The attributes of the node are:

Within the coll node, each and every one of the fields that have to be transfered from a table into another one. For this, we have to put different prop nodes, which will be the ones that have the source field name and the destination field name.
Later, we will put several attributes defining the type or which type of action we need to do.

Node where is defined which field will be transfered and which action will be made in the destination table.
The attributes of this node are:

Once defined which field is the origin and the destination field, with its individual characteristics, we have to define the action to be performed, which will be defined within a node oper within the prop node.

Types of operations that can be performed with the fields that we want to transfer from one table to another, in the prop node.

In this operation, what is done is to put a given value in the destination field. Therefore, the prop node, only has the type of the field, type , and the name of the field that is the destination, dest-name .
In the example, it can be seen that in the IDPADRE field of the destination table, which is of numeric type, N, the value 1 will be saved.

<prop dest-name="IDPADRE" type="N">
	<oper type="setval" value="1"/>
</prop>

In this other example we put the value “xone” in the destination field NAME, which is of type text.

<prop dest-name="NOMBRE" type="T">
	<oper type="setval" value="xone"/>
</prop>

Operation to copy the value of a source field into a destination field.

Example where it is seen how the value of the “delegation” field will be copied to the “LABEL” field. This field is text type. You can also see how it is the primary key, so to find if there is such a record in the destination, you will search for the value of this field. It is also being told to save the value of the source in the ## SOURCEKEYVALUES ## macro, and to save the value of the destination in the ## DESTKEYVALUES ## macro.

<prop source-name="delegación" dest-name="ETIQUETA" key="true" type="T" saved-source="true" saved-dest="true">
		<oper type="copy"/>
</prop>

Node that transfers the value of the “PASSWORD_E” field to the PWD field. As we can see, it has type X, so it is being indicated that it is a password field, and its value keeps it encrypted. Encryption is supported by the XOne Platform, so that users can subsequently enter the application.

<prop source-name="PASSWORD_E" dest-name="PWD" type="X">
           <oper type="copy"/>
</prop>	

Node that transfers the value of the “DESCPTE” field to the “INCIDENCE” field. It is of text type. We also see that it has the attribute “always-update”, so we are forcing it into the “master_replica_queue” replication queue, to insert an update even if its value does not change.

<prop source-name="DESCPTE" dest-name="INCIDENCIA" key="false" type="T" always-update="true">
	<oper type="copy"/>
</prop>	

Node that transfers the value of the “FECCARGA” field to the “DATE” field. The field is a date type. You can also see a new node, format , node that is used within the prop nodes, and that is used to format the value in the destination with the characteristics that are told in the value attribute. In the example, when you put it, we are telling it that in the destination the date has to be inserted in day / month / year mode.

<prop source-name="FECCARGA" dest-name="FECHA" type="D">				
  <oper type="copy"/>
  <format name="dest-name" value="dd/mm/yyyy"/>
</prop>	

Node that transfers the data from the “CODAVISO” field to the “TIPOPARTE” field, and we see that it is of the text type. We can also see that there is the format node. Here we can see that it has a new attribute, trim . This attribute does or does not eliminate the blank spaces that come from the origin in the destination. If the attribute is not defined is “true”, that is, it deletes the blank spaces. In order it works, it is necessary to put the value “NULL” in the “value” attribute.

<prop source-name="CODAVISO" dest-name="TIPOPARTE" type="T">
	<oper type="copy"/>
	<format value="NULL" trim="false"/>
</prop>	

Node that transfers the data from the “PRETAR” field to the “PRICE” field. It is numeric, and specifically with 5 decimals. In order for the copy to be done well, the format node has been set, placing exactly the number of decimals that will be put to it.

<prop source-name="PRETAR" dest-name="PRECIO" type="N5">
	<oper type="copy"/>
	<format name="dest-name" value="0.00000"/>
</prop>

Operation to transfer data from fields related to values ​​that are in other tables. What would be in the mappings fields of type IDEMPRESA or IDUSUARIO. For this, what is done is to take the value of the source field, and look for it in a table, when it finds the value, it puts the value of a field that we say of that table in the destination field of the beginning.

In the example that is seen, the value of the “delegation” field is taken, and compared with the “LABEL” field, which is put in the mapfld attribute, which exists in the “Gen_Business” table, defined in the source attribute. If there is a record that has that value, there only has to be one, since the field by which the search is made in the “Gen_Business” table, must be the primary key of it, it takes the value of the field that is defined in the attribute targetfld , “ID” for this case, and put it in the field dest-name , field “IDEMPRESA”.

In SQL: IDEMPRESA=SELECT ID FROM Gen_Empresa WHERE ETIQUETA=delegacion

<prop source-name="delegacion" dest-name="IDEMPRESA" type=”N”>
	<oper type="mapval" source="Gen_Empresa" targetfld="ID">
		<prop mapfld="ETIQUETA" mapvalue="##SELF##"/>
	</oper>
</prop>	

In this case, several props can be used within the same operation, which is for those cases in which the first key of the record we are looking for is defined by several fields, in this case “COMPANY_ID” and “CAMPO2”.
Example:

<oper type="mapval" source="gen_usuarios" targetfld="ID">
     <prop mapfld="COMPANY_ID" mapvalue="##SELF##"/>
     <prop mapfld="CAMPO2" mapvalue="##FLD_PROPIEDAD##"/>
</oper>  

If we want to send a certain email with fields rescued in the coll query, we will use the type=“mail” oper.
For the other side, in the mailfield attribute we specify which type of value is going to be transfered, by being able to take the values: To, Subject, Message and File.

In the end, there is the value attribute, which is the one that transfers the value chosen in the SQL.

The interface will try to send an email as long as the oper with value To is defined.

<prop source-name="DESTINO" type="T">
	<oper type="mail" mailfield="To" value="##SELF##"/>
</prop>
<prop source-name="ASUNTO" type="T">
	<oper type="mail" mailfield="Subject" value="##SELF##"/>
</prop>
<prop source-name="MENSAJE" type="T">
	<oper type="mail" mailfield="Message" value="##SELF##"/>
</prop>
<prop source-name="FICHERO" type="T">
	<oper type="mail" mailfield="File" value="##SELF##"/>
</prop>

Node that is executed when we finish performing the data transfer from one table to another.

It executes a SQL. This is quite useful to put a field in the source table with a value, to indicate that this value it was already transfered to the destination table.

At the example, we can see that it has two param nodes, so we are telling it which SQL is going to be executed, in the value attribute. Also, in which database is put “dest” to the name attibute, that is in the destination database, and “source”, that is the source database.

Besides, we can see that it uses the ##SOURCEKEYVALUES## and ##DESTKEYVALUES## macros, that have been filled while the data are being transfered from a database into another one.

<action name="execute-query">
<param name="source" value="Update Gen_DetDocumento SET ACTUALIZADO=1 WHERE ##SOURCEKEYVALUES##"/>
<param name="dest" value="UPDATE Gen_Documentos  SET ACTUALIZADO=1  WHERE ID IN (SELECT IDDOCUMENTO FROM GEN_DETDOCUMENTO WHERE ##DESTKEYVALUES##)"/>	
</action>

Node that is executed before starting the data transfer. You can use all the operations that exist in the after-action node.

Node to perform an erasure of the indicated data. We can delete both the origin and destination.

There are several types of “delete” operations to be made, such as:

This is to make the data deletion that coincide with the data searched at the source, from the field or fields which coincide with the primary key we have defined.

Example of use

<delete>
	/* En el ejemplo se realiza el borrado en la tabla “gen_sat” y "gen_usuarios, de la base de datos de destino, 
	   por utilizar el atributo “delete-dest-table”, de aquellos datos que coinciden con la macro ##DESTKEYVALUES##. */
 
	<action name="delete-conditional" delete-dest-table="gen_sat" use-saved-dest="true"/>
	<action name="delete-conditional" delete-dest-table="gen_usuarios" use-saved-dest="true"/>
 
 
	/* Con este ejemplo se realiza el borrado en la base de datos origen. 
	   Para indicar una tabla de origen se utiliza el atributo “delete-source-table”, 
	   con este atributo se utiliza la macro ##SOURCEKEYVALUES##. */
 
	<action name="delete-conditional" delete-source-table="EVUSUA" use-saved-source="true"/>
</delete>

This operation is useful to make the deletion both in the client and in the XOne database, so that besides clearing the normal table, it inserts the deletion in the replica queue.

Example of use:

<delete>
	/* 1.- Se realiza la búsqueda de en la base de datos de destino, en la tabla “gen_colla”(select-dest-table) de los ROWID 
	   que cumplen la condición del “where”(where), con el alias “c”(alias-dest-table). 
 
	   SELECT c.ROWID FROM Gen_Colla WHERE ESTADO=1
 
	   2.- Si hay valores con esa condición, los borra de la tabla “gen_colla”( delete-dest-table).
	   3.- Si se encontró algún registro con el punto 1, existe el atributo delete-source=”true”, el atributo “source-table” 
	       con un nombre de tabla y hay una condición, se realiza el borrado en la tabla “Gen_USUARIOS”( source-table), con la condición
 	       que hay en el atributo “where”. */
 
	<action name="delete-sql" source-table="Gen_USUARIOS" delete-source="true" where="ESTADO=1" delete-dest-table="Gen_Colla" 
	 select-dest-table="Gen_Colla" alias-dest-table="c"/>
</delete>			

Operation useful to make the deletion of a file.

Example of use:

<delete>
	/* Realiza el borrado del fichero que existe en el atributo “PATH”, con lugar y nombre del mismo. */
 
	<action name="delete-fichero" path="C:\Archivos de programa\CGSoft\CGInterclient\Captura\Ficheros\ESPPDA.TXT"/>
</delete>

For changes control.

For this it will be put within the nodo client, with type=“##LASTMODIFIED##“, in which it will enter when finishing the transformation in the interclient_sync_tables table, the values defined in the data-condition, where ##LASTMODIFIEDDATETIME## is the date and the time when the transformation starts.

<data-condition>
	<client type="##LASTMODIFIED##">
		<param name="FECHA" value="##LASTMODIFIEDDATETIME##">
			<format value="MM-dd-yyyy"/>
		</param>
		<param name="HORAINI" value="##LASTMODIFIEDDATETIME##">
			<format value="HH:mm:ss"/>
		</param>
		<param name="HORAFIN" value="##NOW##">
			<format value="HH:mm:ss"/>
		</param>
	</client>
</data-condition>

Within the client node, the “param” node will be put, which has the attributes:

Macros as auxiliary values can be used, both to a source-table level within the coll node, and to performance an action.

Within the source-table attribute, to a coll level.

<coll name="COLL_PASAR" source-table="SELECT t.* FROM Tabla1 t WHERE t.CAMPO='Valor1' and t.FECHA>='##MACRO##'" ...

Here the “macro” node is shown, which will be within the “coll” node.

<macro name="##MACRO##" source-table="XONEPIMAUX" sql="SELECT TIMESTAMP AS X FROM INTERCLIENT_SYNC_TABLES WHERE OBJECTNAME='gen_contactos'" field="X" type="T">
	<format value="yyyy-MM-dd HH:mm:ss"/>
</macro>

The macro node attributes are:

It is an example code about how an interclient.xml file will be.

<xml>
	<interface>
		<app name="ITF_PRUEBA" logoper="true" rowidfieldname="CGSROWID"  sqlfieldname="SQL" oracle-session="ALTER SESSION SET NLS_DATE_FORMAT='DD/MM/YYYY HH24:MI:SS'">
			<connection>
				<client name="NOMBRE1" provider="System.Data.PROVIDER" connstring="Data Source=ORACLESRC;Persist Security Info=False;User ID=CGSOFT;password=CGSOFT;Unicode=True"/>
				<source name="NOMBRE2" provider="System.Data.PROVIDER" connstring="Data Source=CGSOFTBD;Persist Security Info=False;User ID=CGSOFT_ITF;password=CGSOFT_ITF;Unicode=True"/>
				<optional name="NOMBRE3" provider="System.Data.PROVIDER" connstring="......."/>				
			</connection>
		</app>
		<transforms type="client-to-source">
			<transform name="gen_usuarios_cp">
				<coll dest-table="GEN_USUARIOS"
				source-table="SELECT a.*, 1 AS IDEMPRESA,trim(TARIFA) || '-' AS CODSEC FROM DELEGADOS_CGS a
				WHERE a.CG_ESTADO IN(7)">
					<prop source-name="DELEGADO" dest-name="LOGIN" key="true" saved-source="true">
						<oper type="copy"/>
					</prop>					
					<prop source-name="NOMBRE" dest-name="NOMBRE" type="T">
						<oper type="copy"/>
					</prop>													
					<prop source-name="CODSEC" dest-name="IDTARIFA" type="T">
						<oper type="mapval" source="gen_tarifas" targetfld="ID">
							<prop mapfld="CODSEC" mapvalue="##SELF##"/>
						</oper>
					</prop> 
					<prop source-name="TARIFA_ESPECIALISTA_SN" dest-name="TARIFA_ESPECIALISTA_SN" type="N">
						<oper type="copy"/>
					</prop> 
					<prop  dest-name="TIPO" type="N">
						<oper type="setval" value="1"/>
					</prop>	
					<after-action>
						<action name="execute-query">
							<param name="source" value="UPDATE DELEGADOS_CGS SET CG_ESTADO=5 WHERE ##SOURCEKEYVALUES##"/>
						</action>
					</after-action>	
				</coll>
			</transform>
			<transform name="gen_dettarifacgs_cparcial"> 
				<coll dest-table="GEN_DETTARIFA" source-table="
				SELECT a.*,trim(a.TARIFA) || replace(a.SECUENCIA,' ','-') AS CODSEC
				FROM TARIFAS_CGS a,ARTICULOS_CGS a2
				WHERE a.ARTICULO=a2.ARTICULO AND a.CG_ESTADO IN(7)">
				<data-condition>
						<client type="##LASTMODIFIED##">
							<param name="FECHA" value="##LASTMODIFIEDDATETIME##">
								<format value="MM-dd-yyyy"/>
							</param>
						 	<param name="HORAINI" value="##LASTMODIFIEDDATETIME##">
							 	<format value="HH:mm:ss"/>
							</param>
							<param name="HORAFIN" value="##NOW##">
							 	<format value="HH:mm:ss"/>
							</param>
						</client>
					</data-condition>
					<prop source-name="ID" dest-name="IDTARIFA" key="true" saved-source="true" type="N" saved-dest="false">
					</prop>
					<prop source-name="CODSEC" dest-name="IDTARIFA" key="true" type="N">
						<oper type="mapval" source="gen_tarifas" targetfld="ID">
							<prop mapfld="CODSEC" mapvalue="##SELF##"/>
						</oper>
					</prop>
					<prop source-name="ARTICULO" dest-name="IDARTICULO" key="true" type="N">
						<oper type="mapval" source="gen_articulos" targetfld="ID">
							<prop mapfld="REFERENCIA1" mapvalue="##SELF##"/>
						</oper>
					</prop>
					<prop source-name="SECUENCIA" dest-name="SECUENCIA" key="true" type="T">
						<oper type="copy"/>
					</prop>			
					<prop source-name="U_MAXIMA" dest-name="CANTMAX" type="N">
						<oper type="copy"/>
					</prop>
					<after-action>
						<action name="execute-query">
							<param name="source" value="UPDATE TARIFAS_CGS SET CG_ESTADO=5 WHERE ##SOURCEKEYVALUES##"/>
						</action>
					</after-action>
				</coll>
			</transform>
			<transform name="gen_dettarifacgs_cparcial"> 
				<coll dest-table="GEN_DETTARIFA" source-table="
				SELECT a.*,trim(a.TARIFA) || replace(a.SECUENCIA,' ','-') AS CODSEC
				FROM TARIFAS_CGS a,ARTICULOS_CGS a2
				WHERE a.ARTICULO=a2.ARTICULO AND a.CG_ESTADO IN(7)">
				<prop source-name="ID" dest-name="IDTARIFA" key="true" saved-source="true" type="N" saved-dest="false">
					</prop>
				<prop source-name="CODSEC" dest-name="IDTARIFA" key="true" type="N">
					<oper type="mapval" source="gen_tarifas" targetfld="ID">
						<prop mapfld="CODSEC" mapvalue="##SELF##"/>
					</oper>
				</prop>
				<prop dest-name="UTARREM" type="N">
						<oper type="setval" value="9"/>
				</prop>
				<prop source-name="U_TAR_REM" dest-name="UTARREM" type="N">
						<oper type="copy"/>
				</prop>
				<after-action>
					<action name="execute-query">
						<param name="source" value="UPDATE TARIFAS_CGS SET CG_ESTADO=5 WHERE ##SOURCEKEYVALUES##"/>
					</action>
				</after-action>
				</coll>
				<coll dest-table="GEN_DETTARIFA" source-table="
				SELECT a.*,trim(a.TARIFA) || replace(a.SECUENCIA,' ','-') AS CODSEC,b.ID
				FROM TARIFAS a,CARGA_PARCIAL b,ARTICULOS a2
				WHERE b.ARTICULO=a2.ARTICULO AND a.ARTICULO=b.ARTICULO AND a.TARIFA=b.TARIFA AND a.SECUENCIA=b.SECUENCIA
				AND b.TABLA='TARIFAS' AND b.ESTADO='B'">
				<prop source-name="ID" dest-name="IDTARIFA" key="true" saved-source="true" type="N" saved-dest="false">
				</prop>
				<prop source-name="CODSEC" dest-name="IDTARIFA" key="true" type="N" saved-dest="true">
					<oper type="mapval" source="gen_tarifas" targetfld="ID">
						<prop mapfld="CODSEC" mapvalue="##SELF##"/>
					</oper>
				</prop>
				<prop source-name="SECUENCIA" dest-name="SECUENCIA" key="true" type="T" saved-dest="true">
					<oper type="copy"/>
				</prop>
				<after-action>
					<action name="execute-query">
						<param name="source" value="UPDATE TARIFAS_CGS SET CG_ESTADO=5 WHERE ##SOURCEKEYVALUES##"/>
					</action>
				</after-action>
				</coll>
			</transform>
		</transforms>
		<transforms type="source-to-client">
			<transform name="clientes_ent_cgs">
				<coll dest-table="CLIENTES_ENT_CGS" 
				source-table="SELECT c.*,
				SUBSTR(c.CP,1,5) AS CP,SYSDATE AS MAP_FMODIF,
				SUBSTR(replace(replace(c.CUENTABANC,'-',''),' ',''),1,20) AS MAP_CUENTABANC,u.LOGIN AS DELEGADO,t.CODIGO AS TARIFA,g.CODIGO AS GRUPO_COMPRAS,p.CODIGO AS POTENCIAL_MERCADO,
				NVL(c.FORMAPAGO,'_') AS MAP_FORMAPAGO
				FROM ((((Gen_Clientes_Mod c
				LEFT OUTER JOIN Gen_Usuarios u ON c.IDUSUARIO=u.ID)
				LEFT OUTER JOIN Gen_Tarifas t ON c.IDTARIFA=t.ID)
				LEFT OUTER JOIN Gen_GruposCompra g ON c.IDGRUPOCOMPRA=g.ID)
				LEFT OUTER JOIN Gen_PotencialMercado p ON c.IDPOTMERCADO=p.ID)
				WHERE (c.MODIFICADO=1 or c.MODIFICADO=3) AND u.LOGIN IS NOT NULL AND c.EXPEDIENTE IS NOT NULL AND c.EXPEDIENTE&lt;&gt;''
				">
					<prop source-name="EXPEDIENTE" dest-name="CLIENTE" type="N" key="true">
						<oper type="copy"/>
					</prop>
					<prop source-name="DELEGADO" dest-name="DELEGADO" key="true" type="T">
						<oper type="copy"/>
					</prop>		
					<prop source-name="TIPO" dest-name="TIPO_CLIENTE" type="N">
						<oper type="copy"/>
					</prop>					
					<prop source-name="ACCIONISTA" dest-name="ACCIONISTA" type="N">
						<oper type="copy"/>
					</prop>
					<prop source-name="MAP_FMODIF" dest-name="F_MODIF" key="true" type="T">
						<oper type="copy"/>
						<format name="dest-name" value="dd/MM/yyyy HH:mm:ss"/>   
					</prop>																																												
				</coll>
			</transform>
		</transforms>		
	</interface>
</xml>