pp108 : XSLtransform

XSLtransform


This method is used to transform data using the data transformation that is created using the Transformation Modeler. XSLtransform is part of the Methodset DataTransformation 4.2 in the Process Platform Data transformation application package.

SOAP Request

<XSLtransform xmlns="http://schemas.cordys.com/datatransform/4.2">
    <SourceDoc>
        <Order>
            <OrderId>101</OrderId>
            <Customer>David</Customer>
            <Amount>25000</Amount>
        </Order>
    </SourceDoc>
    <StyleSheetLocator>
        <MapName>/Vendor/CustomerInfoToCustomers</MapName>
        <version>user</version>
        <MapID> d1e77c18-7c23-4184-b019-b8871abfbb2e</MapID>
    </StyleSheetLocator>
</XSLtransform>

Request Parameters

Parameter

Description

Data Type

Accepted Input Values

SourceDoc

Contains the instance of the source that you want to transform

XML

If you have more than one source, group them under the SourceEnvelope element.

MapName

Contains the name of the data transformation along with the complete path. This is a mandatory field.

Path

MapID

Contains the unique ID of the data transformation. This is not a mandatory field.

String

version

Contains the space where the data transformation is located. This is not a mandatory field.

String

The supported versions are:

  • user
  • organization
  • isv

SOAP Response


The target is returned as the response with the mapped content.

<XSLtransformResponse xmlns="http://schemas.cordys.com/datatransform/4.2">
    <tuple>
        <CustomerCreditInfo>
            <Customer>101</Customer>
        </CustomerCreditInfo>
    </tuple>
</XSLtransformResponse>

Response Parameters

Note:
When the XSLtransform SOAP request processes a data transformation for the first time, the transformation is stored in a cache. The cached copy is used by the request to process the map for optimum performance. Subsequently, if you edit that transformation in the data transformation modeler and want to use the updated transformation at runtime, ensure that you restart the SOAP processor so that the changes are updated in the cached copy of the data transformation.