Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Current »

Release Notes

Release Date : 28.09.2020 version: 2.0 Service Package 4 (200_0040H) 

New Features

  • [IFTT-774] - Support for testing Dell Boomi, MuleSoft and other non-SAP integration platforms

  • [IFTT-782] - New result reports

  • [IFTT-828] - New test type to trigger backend messages processing without UI scripting (based on Message Control)

  • [IFTT-778] - Add XSLT transformations as optional test case adaptation

  • [IFTT-799] - SAP PO to CPI migration - tool to convert SAP PO test cases in SAP CPI

  • [IFTT-800] - Template objects for SAP backend business documents - Database rules for the most common business documents in SAP ECC and S/4HANA

  • [IFTT-777] - Handling SAP PO messages with multiple payloads (attachments)

  • [IFTT-846] - File upload for SAP PI/PO test cases for non-SAP to SAP migration scenario

  • [IFTT-783] - Translation of Int4 IFTT system texts to German, French, Spanish

  • [IFTT-816] - Support for Cloud Integration Content in SAP PO

  • [IFTT-844] - New remote comparison of two systems (tcode /INT4/IFTT_REM_COMP)

Improvement

  • [IFTT-827] - Maintenance of container variables values from test case details list

  • [IFTT-717] - Reporting improvements

  • [IFTT-805] - Robotic crawler improvement - store variable value in the test case description

  • [IFTT-764] - SAP CPI adapter - troubleshooting log

  • [IFTT-780] - RFC DB read function module - change the parameter from global to landscape specific

  • [IFTT-806] - IFTT CPI Adapter - Switch API for retrieving list of deployed runtime IFlows

  • [IFTT-807] - IFTT CPI Adapter - Switch API for retrieving list of IFlow endpoint

  • [IFTT-808] - IFTT CPI Adapter - Trace activation handling for CF tenants

  • [IFTT-812] - IFTT Config Wizard - new RFC popup max password length is 40 ( can be 254 in SM59 - note 2020611 )

  • [IFTT-814] - Solution Manager Change Management - removing required SM30 access for setup

  • [IFTT-804] - SAP PI Outbound - messages that has only AM version in staging

  • [IFTT-737] - Support for SAP PI ABAP stack HTTP adapter on SAP PI 7.11

  • [IFTT-775] - CPI Adapter - Support for 1 to many messages (splitter)

  • [IFTT-776] - ECATT adapter adjustments - handling both of Test Scripts and Test Configurations

  • [IFTT-798] - SAP PO: Adding support for asynchronous REST channel testing

Fixes

  • [IFTT-813] - Solution Manager Change management integration - dump when activated by global parameter but without additional configuration.

  • [IFTT-741] - Potential ABAP injection when using CL_XSLT_PROCESSOR

  • [IFTT-773] - Logging in German, French, Spanish - texts not visible

  • [IFTT-784] - Int4 IFTT SAP PI/PO crawler - not saved changes notification

  • [IFTT-786] - CPI adapter does not allow usage of Flat File and XML together

  • [IFTT-787] - Manual editing of test case content from cockpit is not possible for CPI adapter

  • [IFTT-788] - CPI adapter - only one attempt to get responses

  • [IFTT-791] - Creating new test case version copies all message content types from old version

  • [IFTT-792] - Sorting of XML messages before comparison

  • [IFTT-793] - CPI Adapter - creating test cases from landscape different than the landscape assigned to node is not possible

  • [IFTT-802] - CPI adapter - sequence of split messages when saving test case is different than when re-executing it

  • [IFTT-821] - Add HTTP header sending to CPI/PI

  • [IFTT-822] - Payload is not download when iFlow block has more then one trace IDs

  • [IFTT-834] - Testing with asynchronous REST channel - HTTP Header Elements

  • [IFTT-835] - CPI: TC migration from PI synchronous (3) to CPI inbound (12)

  • [IFTT-795] - SAP PI/PO robotic crawler - incorrect automation object associated with error

  • [IFTT-796] - Runtime parameter 'validate PI processing status' doesn't work

  • [IFTT-831] - SAP PI/PO Test case - saving test case fails when initial call to version 0 delivers empty message

  • No labels