Develop > Controller layer > Application developer > Trading subsystem > Extensions to terms and conditions


Import and exporting contracts with extended terms defined

Contracts to be imported can now have terms attached to them. The additional terms and the properties for those terms must already exist in the TCMappingRegistry. In the contract.xml file that is used to import the contract by using WebSphere Commerce Accelerator, you make changes to include the TermCondition element.

In the following example, the 'waiveSurCharge' indicator is set to the Integer value '1' and the 'surChargeAmount' is set to the Double value '50.00'.

<BuyerContract> ...
<TermCondition type='SurChargeTC'>        
<Property name='waiveSurCharge' value='1'>        
<Property name='surChargeAmount' value='50.00'>
</TermCondition> ...
</BuyerContract> 

Note that the "Value" attribute of the TermCondition element is mandatory and its value should match the type that you defined in TCConfigurationExt.xml.

The TradingAgreement.xsd and BuyerContract.xsd files were updated with version 6.0.0.2 to allow for these new entries.

When contracts to be exported contain extended terms, the extended terms are copied to the exported file, as shown in Copy and duplicating contracts.


Related tasks

Add a term to a contract or account

Create an extended term and condition type for contracts and accounts

Deploy custom extended terms

Update extended terms of a contract or account

Related reference

TCConfiguration.xml file


+

Search Tips   |   Advanced Search