This topic describes the systematic instructions to configure the transformation.

1. On Consumer Services screen, click the required consumer service tile.
   The Transformation screen is displayed.

   Figure 7-1 Transformation

   
   

   
   Description of "Figure 7-1 Transformation"

   
   

New Transformation

The user can create transformation manually.

2. On Transformation screen, click New.
   The New Transformation - Basic Details screen is displayed.

   Figure 7-2 New Transformation - Basic Details

   
   

   
   Description of "Figure 7-2 New Transformation - Basic Details"

   
   
3. Specify the fields on New Transformation - Basic Details screen.

   Note:

   The fields marked as Required are mandatory.

   For more information on fields, refer to the field description table.

   Table 7-1 New Transformation - Basic Details - Field Description

   Field	Description
   Transformation Name	Specify the name for the transformation. Note: Enter 0 to maximum of 255 characters. No numeric value at beginning and no space allowed.
   Active	ON / OFF If transformation is turned OFF, the user will be unable to choose transformation in routing.
   Product Processor	Select the product processor from the drop-down list.
   Implementation	Select the implementation from the drop-down list.
   Service	Select the service from the drop-down list.
   Service	Displays the service details of the selected service.
   Operation	Displays the operation details of the selected service.

4. Click Next Step.
   TheNew Transformation - Request Validation screen is displayed.

   Figure 7-3 New Transformation - Request Validation

   
   

   
   Description of "Figure 7-3 New Transformation - Request Validation"

   
   
5. Specify the fields on New Transformation - Request Validation screen.

   Note:

   The fields marked as Required are mandatory.

   For more information on fields, refer to the field description table.

   Table 7-2 New Transformation - Request Validation - Field Description

   Field	Description
   Validation Required?	Select the toggle to enable the validation required for request. Note: Validation Model of Oracle Banking Pricing & Decision Service is only supported.
   Product Processor	Select the product processor from the drop-down list.
   Implementation	Select the implementation from the drop-down list.
   Service	Select the service from the drop-down list.
   Template	Specify the template in which validation provider accepts.

6. Click Next Step.
   TheNew Transformation - Request Headers screen is displayed.

   Figure 7-4 New Transformation - Request Headers

   
   

   
   Description of "Figure 7-4 New Transformation - Request Headers"

   
   
7. Specify the fields on New Transformation - Request Headers screen.

   Note:

   The fields marked as Required are mandatory.

   For more information on fields, refer to the field description table.

   Table 7-3 New Transformation - Request Headers - Field Description

   Field	Description
   Name	A list of headers related to the chosen provider, implementation, and service is displayed. The user can only modify the header value.
   Value	Displays the value of the headers. Value can be hardcoded value or velocity mapping.

8. Click Next Step.
   TheNew Transformation - Path Parameters screen is displayed.

   Figure 7-5 New Transformation - Path Parameters

   
   

   
   Description of "Figure 7-5 New Transformation - Path Parameters"

   
   
9. Specify the fields on New Transformation - Path Parameters screen.

   Note:

   The fields marked as Required are mandatory.

   For more information on fields, refer to the field description table.

   Table 7-4 New Transformation - Path Parameters - Field Description

   Field	Description
   Name	A list of path parameters related to the chosen service is displayed. User can only change the path parameter value.
   Value	Displays the value of the headers. Value can be hardcoded value or velocity mapping.

10. Click Next Step.
    TheNew Transformation - Query Parameters screen is displayed.

    Figure 7-6 New Transformation - Query Parameters

    
    

    
    Description of "Figure 7-6 New Transformation - Query Parameters"

    
    
11. Specify the fields on New Transformation - Query Parameters screen.

    Note:

    The fields marked as Required are mandatory.

    For more information on fields, refer to the field description table.

    Table 7-5 New Transformation - Query Parameters - Field Description

    Field	Description
    Name	Query parameter list relevant to the selected service is displayed. User can only change the query parameter value.
    Value	Displays the value of the headers. Value can be hardcoded value or velocity mapping.

12. Click Next Step.
    TheNew Transformation - Request Transformation screen is displayed.

    Figure 7-7 New Transformation - Request Transformation

    
    

    
    Description of "Figure 7-7 New Transformation - Request Transformation"

    
    
13. Specify the fields on New Transformation - Request Transformation screen.

    Note:

    The fields marked as Required are mandatory.

    For more information on fields, refer to the field description table.

    Table 7-6 New Transformation - Request Transformation - Field Description

    Field	Description
    Body Type	Select the body type for the Request Transformation from the drop-down list. The available options are: RAW FORM DATA BINARY Note: This field appears only if the selected service is REST service and RAW option is used for URL-encoded content type.
    Template Type	Select the template type for the Request Transformation from the drop-down list. The available options are: VELOCITY JSLT XSLT
    Template	Specify the template for the Request Transformation in which provider accepts. Refer to Transformation Type for syntax.
    Extended Template	Specify the custom template in order to extend the kernel template. Refer to Extensibility and Transformation Type for syntax. Note: This field appears only if the Body Type is selected as RAW.

14. Click Next Step.
    TheNew Transformation - Response Headers screen is displayed.

    Figure 7-8 New Transformation - Response Headers

    
    

    
    Description of "Figure 7-8 New Transformation - Response Headers"

    
    
15. Specify the fields on New Transformation - Response Headers screen.

    Note:

    The fields marked as Required are mandatory.

    For more information on fields, refer to the field description table.

    Table 7-7 New Transformation - Response Headers - Field Description

    Field	Description
    Name	User can specify the additional headers that are required to be part of Routing Hub response headers.
    Value	Displays the value of the headers. Value can be hardcoded value or velocity mapping.

16. Click Next Step.
    TheNew Transformation - Response Transformation screen is displayed.

    Figure 7-9 New Transformation - Response Transformation

    
    

    
    Description of "Figure 7-9 New Transformation - Response Transformation"

    
    
17. Specify the fields on New Transformation - Response Transformation screen.

    Note:

    The fields marked as Required are mandatory.

    For more information on fields, refer to the field description table.

    Table 7-8 New Transformation - Response Transformation - Field Description

    Field	Description
    Stop route for failed request	This property is used to handle response for failed request. Note: Only applicable for API chaining scenario.
    Template Type	Select the template type for the Response Transformation from drop-down list. The available options are: VELOCITY JSLT XSLT
    Template	Specify the kernel template in which consumer accepts. Refer to Transformation Type for syntax.
    Mocking required?	Select the toggle if the mocking is required for the Response Transformation or not. If the toggle is ON, the Routing Hub will return the mocked template output (with extended template output if mentioned) to consumer without invoking provider API.
    Mock Template	Specify the kernel template for the Response Transformation in which the consumer accepts. Refer Transformation Type for syntax.
    Extended Template	Specify the custom template in order to extend the kernel template. Refer to Extensibility and Transformation Type for syntax.

18. Click Save to save the details.

Import Transformation

The user can create a transformation by importing the JSON file. The user can also import zip file in order to import all the configuration JSON files together (except parent level configuration JSON files).

19. On Transformation screen, click Import.
    The Import Transformation screen is displayed.

    Figure 7-10 Import Transformation

    
    

    
    Description of "Figure 7-10 Import Transformation"

    
    

    For more information on fields, refer to the field description table.

    Table 7-9 Import Transformation - Field Description

    Field	Description
    File	Select the file using Select button. Note: Allows only to select one file and accepts JSON and ZIP file.
    Overwrite extended templates	Select the respective radio button to overwrite the extended templates. The available options are: Yes - This option overwrites the extended templates. No - This option retains the existing extended templates.

20. Click Import to import the selected file.

View / Edit Transformation

The user can view or more transformation details.

21. On Transformation list, click Edit.
    The Edit Transformation - Basic Details screen is displayed.

    Figure 7-11 Edit Transformation - Basic Details

    
    

    
    Description of "Figure 7-11 Edit Transformation - Basic Details"

    
    
22. Click Next Step.
    The Edit Transformation - Request Validation screen is displayed.

    Figure 7-12 Edit Transformation - Request Validation

    
    

    
    Description of "Figure 7-12 Edit Transformation - Request Validation"

    
    
23. Click Next Step.
    The Edit Transformation - Request Headers screen is displayed.

    Figure 7-13 Edit Transformation - Request Headers

    
    

    
    Description of "Figure 7-13 Edit Transformation - Request Headers"

    
    
24. Click Next Step.
    The Edit Transformation - Path Parameters screen is displayed.

    Figure 7-14 Edit Transformation - Path Parameters

    
    

    
    Description of "Figure 7-14 Edit Transformation - Path Parameters"

    
    
25. Click Next Step.
    The Edit Transformation - Query Parameters screen is displayed.

    Figure 7-15 Edit Transformation - Query Parameters

    
    

    
    Description of "Figure 7-15 Edit Transformation - Query Parameters"

    
    
26. Click Next Step.
    The Edit Transformation - Request Transformation screen is displayed.

    Figure 7-16 Edit Transformation - Request Transformation

    
    

    
    Description of "Figure 7-16 Edit Transformation - Request Transformation"

    
    
27. Click Next Step.
    The Edit Transformation - Response Headers screen is displayed.

    Figure 7-17 Edit Transformation - Response Headers

    
    

    
    Description of "Figure 7-17 Edit Transformation - Response Headers"

    
    
28. Click Next Step.
    The Edit Transformation - Response Transformation screen is displayed.

    Figure 7-18 Edit Transformation - Response Transformation

    
    

    
    Description of "Figure 7-18 Edit Transformation - Response Transformation"

    
    
29. Click Save to save the modified transformation details.

Delete Transformation

The user can delete the transformation.

30. On Transformation list, click Delete.
    The Confirmation - Delete screen is displayed.

    Figure 7-19 Confirmation - Delete

    
    

    
    Description of "Figure 7-19 Confirmation - Delete"

    
    

Export Transformation

The user can export the transformation configuration as JSON file.

31. On Transformation list, click Operation menu (3 dots button), and click Export.
    The Confirmation screen is displayed.

    Figure 7-20 Confirmation - Export

    
    

    
    Description of "Figure 7-20 Confirmation - Export"

    
    

Request Audit

32. On Transformation list, click Operation menu (3 dots button), and click Request Audit.
    The Request Audit screen is displayed.

    Note:

    Refer to Request Audit topic for screen and field description.