Int4 IFTT Release Notes 1.0 SP09

Release Notes
Expected Date : 17.09.2018 version: 1.0 Service Package 9 (103_0009) 

Notes: The release is scheduled for the 17th September 2018. 

Improvement

  • [IFTT-528] - [PI only] 1 to many mappings improvement. Exclude transited messages that were split. WARNING existing test cases might be affected by this improvement

  • [IFTT-529] - DB configuration - move order of fields for better understanding

  • [IFTT-530] - PI testing - Failed to extract boundary ID for multipart attachment

  • [IFTT-533] - Filtering messages in Message Selector

  • IFTT-537] -  Add product version to cockpit and IMG tcodes

  • [IFTT-538] - [PI - sync] Missing logical port error notification

  •  [IFTT-546] - Displaying folder structure in alphabetical order

  • [IFTT-550] - Start / Stop channels - convert business component of the channel if executed on different landscape

  • [IFTT-551] - Add more execution / debug messages

  • [IFTT-552] – Execution landscape added to API remote test case execution function

  • [IFTT-556] - Improvement to allow simultaneous working on configuration objects

  • [IFTT-513] - Improve test case execution report header

Bug

  • [IFTT-476] - Memory leaks for thousands of test cases execution

  • [IFTT-492] - PI unit testing for PI inbound test cases. Failed test cases when comparing PI content was added after creation of test cases

  • [IFTT-499] – Ignore list for mixed XML and Flat file output

  • [IFTT-506] - For local test cases - RFC shouldn't be called

  • [IFTT-509] - Missing backend validation results in specific case (when included together with PI validation)

  • [IFTT-514] - start / stop channels - error message not fetched to IFTT report

  • [IFTT-515] - Long text needed for SOAP error during PI unit testing

  • [IFTT-525] - Sender system conversion should not occur when header is inherited from reference message

  • [IFTT-532] - Test case overall status for combined PI unit and end to end testing

  • [IFTT-535] - Synchronous testing - request body is empty, info message

  • [IFTT-541] - PI message selector filtering empty values

  • [IFTT-542] - Exit from edit mode / shortdump

  • [IFTT-543] - special characters handling in variables processing

  • [IFTT-544] - Support for Chinese characters. REQUIRES deployment of PI content (attached)

  • [IFTT-549] - PI Unit - Do not display RFC connection in the report

  • [IFTT-554] - No error when communication port missing

  • [IFTT-555] - Export & import - only one PI output is exported / imported

  • [IFTT-536] - [PI testing] seems that IFTT result report calls PI to get some details

  • [IFTT-539] - incorrect full folder path in the report

© 2017 - 2022 Int4 AG All rights reserved