Passing data from the PhysicalTransmissionWrapper to the extendedCfg

Each FTM Application will have its own custom PhysicalTransmissionWrapper. FTM provides an area in the Environment where values pertaining to the Inbound PhysicalTransmission are stored:

	Environment.PMP.Variables.LogPT.DBRecord.OBJ
	Environment.PMP.Variables.LogPT.DBRecord.TRANSMISSION

These areas in the environment are automatically populated by FTM Core when logging the Physical Transmission, but it is possible for the PhysicalTranmissionWrapper to add to these areas before the call to log the Physical Transmission. The Inbound ITX Integration flows will take whatever data it finds here and create an ExtendedCfg structure (name = TransmissionProperties) that it passes to the ITX Map. This enables applications to add information about the inbound Physical Transmission that may not automatically get sent to the ITX map (for example, the FILENAME of the source file used to pass large messages in). An example of extendedCfg structure in this case would look like this:

<extendedCfg>
	<name>TransmissionProperties</name>
	<extendedCfg>
		<name>UID</name>
		<value>uidvalue</value>
	</extendedCfg>
	<extendedCfg>
		<name>CID</name>
		<value>cidvalue</value>
	</extendedCfg>
	<extendedCfg>
		<name>OWNER_ID</name>
		<value>owneridvalue</value>
	</extendedCfg>
	<extendedCfg>
		<name>SUBTYPE</name>
		<value>subtypevalue</value>
	</extendedCfg>
	<extendedCfg>
		<name>PARTY_ID</name>
		<value>partyidvalue</value>
	</extendedCfg>
	<extendedCfg>
		<name>FILENAME</name>
		<value>filenamevalue</value>
	</extendedCfg>
	<extendedCfg>
		<name>FILEADDRESS</name>
		<value>fileaddressvalue</value>
	</extendedCfg>
	<extendedCfg>
		<name>CCSID</name>
		<value>ccsidvalue</value>
	</extendedCfg>
	<extendedCfg>
		<name>ENCODING</name>
		<value>encodingvalue</value>
	</extendedCfg>
</extendedCfg>