2025

2509.1

  1. [Common] Update of dependencies with recently found vulnerabilities.

2509

  1. [DevOps, B2B] Implemented DevOps of TPM objects.

    Supported objects are Company Profile, Subsidiary, Trading Partner, Agreement Template, Agreement, B2B Scenario. The import is performed for Agreements and objects linked with the agreement attached to the transport will be imported to target system.

    It is recommended to use the feature in the following way:

    1. Import MIGs/MAGs manually using export/import operation on Integration Suite environment from source tenant to target tenant.

    2. Create CPI composite landscape (see that section to learn how to do that) if it is not configured yet.

    3. Create ticket and attach TPM objects to it.

    4. Process import to target system.

    There are also several important notes that we recommend to be aware of:

    • If TPM objects already exist on target system and were created manually (not using Figaf tool transport), the transport will fail and it is expected.

    • If some TPM objects attached to the ticket aren’t linked with any agreement attached to the ticket, these TPM objects will be skipped in the transport.

    • It doesn’t really matter if other TPM objects except Agreements are attached to the ticket or not. Agreement will be imported together with all other objects always. So, the fact whether other TPM objects are linked to the ticket or not, affects only the fact if the target objects will be linked to the ticket after transport and it doesn’t affect the content of the archive at all.

    • Idempotent landscapes aren’t supported.

    • Rollback isn’t supported.

    • Identifiers, systems, etc. will no be deleted on target objects after transport if they are deleted on source objects. This is SAP standard behaviour, deletion is not included, only create or overwrite.

    • B2B agreements archive import operation has timeout that could be configured by bootstrap parameter irt.devops.b2b-import-archive-timeout. Default value might be not enough for transports with a lot of agreements.

  2. [Change Management, CPI] Integrated Figaf Bot into Groovy IDE.

  3. [Testing Tool, CPI] Enhanced run send message request for recording to support ProcessDirect endpoints as well.

  4. [Testing Tool, CPI] Added navigation to CPI Message Monitoring from send message request page.

  5. [Testing Tool, CPI] Improved baseline testing to support ordering of inbound messages (read e2e flow description here).

  6. [DevOps] Added a possibility to mark that transport is under review of the reviewer.

  7. [FIX, Testing Tool, CPI] Fixed an issue occurred during running Send Message Requests related to IFlows having many endpoints.

  8. [FIX, Change Management, CPI] Fixed an issue when groovy script couldn’t be updated from the Groovy IDE if script was linked with a shared script.

  9. [FIX, Change Management, CPI] Fixed an issue when groovy script couldn’t be updated from Groovy IDE if the script name contained dots.

  10. [FIX, DevOps, CPI] Fixed an issue when IFlow configuration of the source IFlow could be attached to the ticket wrongly.

  11. [FIX, Monitoring, CPI] Fixed an issue when artifacts weren’t loaded correctly during message monitor creation.

Notes for upgrade from 2508 to 2509

  1. It’s required to process forcible synchronization (options Synchronize objects forcibly and Rebuild links for the latest versions forcibly) of TPM registry for CPI agents from Change Tracking Tool → Tracked Objects page to initialize structure needed for TPM objects transports.

  2. It’s required to update each CPI composite landscape and reconfigure object name mappings and technical tags related to current composite landscape to attach technical tags to TPM objects.

2508.2

  1. [FIX, Change Management, CPI] Fixed an issue when Cloud Integration Tenant report couldn’t be generated due to too many characters in one of the cells.

2508.1

  1. [PI→CPI Migration, Change Management, PRO] Added new option Skip Statistics for migration overview report and PI agent report generation. If report is generated with new option, message statistics will not be added to the report.

  2. [FIX, UI] Fixed an issue when not all users were shown in the reviewers list.

2508

  1. [B2B] Added B2B migration overview for Operation Mappings available for migration to B2B scenario.

  2. [B2B] Added test case migration on B2B migration overview. Test cases related to ICOs linked with Operation Mapping are available for migration.

  3. [B2B] Extended PI to CPI migration configuration with B2B Migration Settings.

  4. [B2B] Added csv export report on B2B pages.

  5. [Testing Tool, CPI] Added a possibility to run send message request for recording.

  6. [Testing Tool, CPI] Added navigation to send message request page from Recordings tab on Test Suite page, Recording Requests tab on Integration Object page, Last result tab on Test Suite page (for BASELINE test cases) and Test run results page (for BASELINE test cases).

  7. [Testing Tool] Improved PI→CPI test case migration process to run migrated test cases on a different integration object.

    It is supported by new bootstrap parameter irt.testing.enable-non-strict-dynamic-message-interface-update. It enables dynamic message interface update when test case is run in the first time on a different integration object (go to Application properties for more information).

  8. [Testing Tool] Simplified order number configuration during test case creation from recording.

    The update of order numbers is performed for recording and test configuration of integration object from recording used for test case creation. Shared configuration isn’t supported.

  9. [Common] Updated frameworks and dependencies versions.

Notes for upgrade from 2507 to 2508

  1. It’s required to process forcible synchronization (options Synchronize objects forcibly and Rebuild links for the latest versions forcibly) of TPM registries for CPI agents from Change Tracking Tool → Tracked Objects page to initialize Country/Regine Code value for TPM objects.

2507.2

  1. [Testing Tool, CPI] Provided a possibility to poll messages in trace mode (available on Recording Request Details page and Test Run Details page). The polling automatically started in this mode if there is only 1 recording or only 1 test run and no more than 10 messages.

  2. [Testing Tool, CPI] Improved message properties comparison to support case-insensitive keys with multiple values per property.

  3. [Monitoring, CPI] Enhanced loading of message monitor filters. There are two new bootstrap parameters irt.monitoring.cpi-message-monitor.disable-messages-count-requests and irt.monitoring.cpi-message-monitor.messages-count-request-timeout configuring the behavior (go to Application properties for more information).

  4. [FIX, PI→CPI Migration] Fixed an issue occurred during migration with Pipeline All profile when all Inbound IFlows were excluded.

  5. [FIX, PI→CPI Migration] Fixed an issue occurred during Receiver/Interface Determination XSLT comparison when there was a condition with quotes.

2507.1

  1. [Testing Tool, CPI] Improved Run steps filter configuration for chain objects on Recording Configuration tab, Test Configuration tab and in recording dialog.

  2. [Common] Enhanced email integration with secondary email in user management.

  3. [FIX, PI→CPI Migration, B2B] Fixed an issue when agreement templates could be listed several times in Agreement Template selection.

2507

  1. [PI→CPI Migration, B2B] Implemented migration of operation mapping to B2B Scenario (read E2e migration of Operation mapping to B2B Scenario for more details).

  2. [Testing Tool, CPI] Restricted send message requests management and execution for agents with Production system enabled.

  3. [Testing Tool] Added Export Test Data report with test run report and inbound/outbound messages payloads. It is available on several pages: Test Run Details page, Test Case page → Testing Results tab, Test Case Runs page, Test Suite Run page, Test Suite page → Last result tab.

  4. [DevOps] Added a possibility to fetch external tickets through send message request (read the configuration here).

  5. [Change Management, Integration Suite] Added change tracking for Subsidiary (check supported objects here).

  6. [Common] Supported email integration through SMTP server using oauth on SAP BTP (read article for more details).

  7. [FIX, Testing Tool] Fixed an issue when xpath for XML attributes comparison was generated incorrectly for element with namespace.

  8. [FIX, PI→CPI Migration] Fixed an issue when commented functions from CPI function library were handled incorrectly during migration when Cloud Integration Resources modes are Use migrated CPI function library or Map functions individually.

  9. [FIX, PI→CPI Migration] Fixed an issue when only one Java class was linked with the Message Mapping after migration.

  10. [FIX, Common] Fixed an issue when email notification failed when SMTP password had an &.

Notes for upgrade from 2506 to 2507

  1. PI libraries are fully excluded from the build. So test configuration for PI agents and add sap.comtcloggingjavaimpl.jar and sap.comtcexception~impl.jar client libraries in libs folder if you use DevOps.

  2. It’s required to process forcible synchronization (options Synchronize objects forcibly and Rebuild links for the latest versions forcibly) of TPM registries for CPI agents from Change Tracking Tool → Tracked Objects page to initialize and link Subsidiary tracked objects.

  3. It’s required to replace LOGBACK_TOTAL_SIZE_CAP by LOGS_TOTAL_SIZE_CAP in manifest.yml and vars.yml file and update approuter/package.json files if Figaf Tool is deployed to SAP BTP, Cloud Foundry. You can download new archive from repository.

    Deploy the application by command cf push --vars-file vars.yml.

2506.2

  1. [Change Management, CPI] Added an option to Initialize externalized parameters of deployed IFlows during synchronization.

2506.1

  1. [FIX, Change Management, CPI] Fixed the error happened during synchronization of IS system when ModifiedBy field is missing or null (this is not standard case, normally that field is initialized).

2506

  1. [B2B] Supported Partner Profile creation (see Create Trading Partner Profile).

  2. [Testing Tool, CPI] Added a possibility to send messages to IFlows (see Send Message Requests for more details).

  3. [Testing Tool] Implemented support of XML attributes comparison (see XML attributes comparison option Test Configuration on Integration Object Details page and Shared Configuration page).

  4. [Testing Tool, CPI] Improved error handling for deployment of test (Figaf and Mock) IFlows.

  5. [Testing Tool, UI] Improved navigation to test case details page.

  6. [Change Management, CPI, Api Management] Added a possibility to include/exclude Partner Directory objects on Landscape Overview page.

  7. [Change Management, Integration Suite] Linked Trading Partner tracked objects with Agreement tracked objects.

  8. [Support Tool] Added a possibility to send all attachments for configured integrations (see Rules).

  9. [PI→CPI Migration] Supported B2B Scenario, Pipeline All and Pipeline Outbound migrations of ICOs having the same receiver declared more than once.

  10. [FIX, Testing Tool] Fixed statistics browsing amount of messages that are sending in progress, scheduled sending, comparison in progress, scheduled comparison, …​

Notes for upgrade from 2505 to 2506

  1. It’s required to process forcible synchronization (options Synchronize objects forcibly and Rebuild links for the latest versions forcibly) of TPM registries for CPI agents from Change Tracking Tool → Tracked Objects page to link Trading Partner tracked objects with Agreement tracked objects.

2505.1

  1. [FIX, Change Management, PRO] Fixed an issue when forcible synchronization of External Definition and Operation mapping objects with the flag Forcibly process payload dependent initializations for not updated objects could lead to inconsistent state in metadata and affect dependent functionalities like PI→CPI migration.

2505

  1. [Testing Tool] Added new statuses FAILED and TIMEOUT_ELAPSED for test suite runs and test case runs:

    1. FAILED means that messages were sent with error or the corresponding root MPL or B2B interchange was found but some test run results were not received after polling.

    2. TIMEOUT_ELAPSED means that test run is in unfinished state longer than expected. The time is configured irt.testing.test-run-timeout-for-regression-test-cases and irt.testing.test-run-timeout-for-baseline-test-cases bootstrap parameters (go to Application properties for more information).

  2. [Testing Tool, CPI] Supported ESCALATED messages polling during recording and testing.

  3. [Testing Tool, Integration Suite] Improved B2B Scenarios Integration Objects to have links to related MAGs and MIGs.

  4. [Testing Tool, CPI] Supported undeployment from NEO system during deletion of test IFlows.

  5. [Testing Tool, PRO] Implemented deletion of AFD ids from caches when recording is deleted in order to record same messages again.

  6. [Testing Tool, PRO] Provided a possibility to poll messages in trace mode (available on Recording Request Details page and Test Run Details page).

  7. [Change Management, Integration Suite] Improved synchronization of TPM objects to detect versions correctly.

  8. [Change Management, CPI] Enhanced management and comparison of zip binary parameters.

  9. [Change Management, UI] Improved searching by type and registry.

  10. [PI→CPI Migration] Supported 1.0.11 of pipeline concept.

  11. [PI→CPI Migration] Supported Extended Receiver Determination for Pipeline All migration profiles.

  12. [PI→CPI Migration] Added comparison of existing receiver/interface determination XSLTs and prepared for upload.

  13. [PI→CPI Migration] Improved B2B Migration profile to allow headers * in migrated IFlows.

  14. [PI→CPI Migration] Replaced xmlns:ns namespace to xmlns:nsx for migrated IFlows.

  15. [PI→CPI Migration] Changed SplitMessageID exchange property value to ${header.UniqueID} or ${header.UniqueID}_${header.CamelSplitIndex}.

  16. [PI→CPI Migration] Added partnerId header to the Inbound IFlow created during migration with Pipeline All or Pipeline Inbound Processing profiles.

  17. [Common] Added public API for next ticket creation, transport preparation and ticket resolution Figaf Tool public API.

  18. [FIX, Change Management, CPI] Fixed an issue when deleted PD_PARTNER wasn’t restored after recreation of related partner directory on CPI/IS system.

  19. [FIX, Change Management, Integration Suite] Fixed an issue occurred during synchronization when B2B scenario had several links to the same IFlow.

  20. [FIX, Change Management, Integration Suite] Fixed an issue when CTT objects links weren’t updated when only linked objects of agreement were changed (agreement itself wasn’t changed).

  21. [FIX, DevOps, CPI] Fixed an issue when reference to function library wasn’t updated in message mapping according to actual landscape mapping rules.

  22. [FIX, PI→CPI Migration] Fixed an issue when migration failed with "Can’t find element by xpath //p1:libstorage" error.

Notes for upgrade from 2504 to 2505

  1. It’s required to process forcible synchronization (options Synchronize objects forcibly and Rebuild links for the latest versions forcibly) of TPM registries for CPI agents from Change Tracking Tool → Tracked Objects page to initialize versions of TPM objects and update B2B Scenarios Integration Objects to initialize links to related MAGs and MIGs.

2504.4

  1. [Testing Tool, Integration Suite, B2B] Added Waiting for acknowledgement and Acknowledgement overdue statuses to the allowed list of statuses during the test message polling.

2504.3

  1. [Infrastructure, BTP deployment] Updated default memory configuration to prevent unexpected failures on BTP environment. Variable XMX_VALUE from vars.yaml is replaced with MAX_RAM_PERCENTAGE. Default value: 50. Also added a new variable INSTANCE_MEMORY that is a RAM allocated for the backend app. Default value: 4G. For trial accounts it must be decreased to 3700M. Use the latest deployment descriptor from https://github.com/figaf/Figaf-BTP-Deployment to apply these changes on your environment.

2504.2

  1. [Common, Integration Suite] Enhanced support of Integration Suite systems when the url has .integrationsuite-<identifier>..

2504.1

  1. [FIX, Change Management, CPI] Fixed fetching of all partner directory parameters due to default limit of 1000 items that API returns.

2504

  1. [Testing Tool, Integration Suite] Added support of B2B Scenarios (see E2e testing of B2B Scenario for more details).

  2. [Change Management, Integration Suite] Added change tracking for B2B Scenarios (check supported objects here).

  3. [Change Management, CPI] Added management of alternative partners: creation, copy, update and deletion operations (see Management of Partner Directory parameters).

  4. [Change Management, CPI] Supported linking of receiver determinations with embedded interface determination.

  5. [Support Tool] Enhanced alerts retention policies with Max amount of alerts and Max total alert attachments size (GB) settings. AlertsCleaner job will be enabled automatically once SupportToolAlertsHandler job is enabled.

  6. [DevOps, CPI, Api Management] Added an option on landscape level (Enable 'Inherit from source' by default for existing target objects) to change default behavior of inheritance flag for existing objects to 'Inherit from source'.

  7. [DevOps] Added landscapes archiving operation. Once the landscape is archived, all related tickets, transports, releases will be canceled and it will no longer be available for any operations with them. This operation is irreversible.

  8. [PI→CPI Migration] Added test cases migration from ICO to B2B Scenario (see Migrate test cases from ICO to B2B Scenario for more details).

  9. [PI→CPI Migration] Moved EDIXML conversion step and related parameters initialization step at the beginning of migrated IFlow (B2B profile).

  10. [PI→CPI Migration] Improved operation mapping migration:

    1. Grouped warnings related to All Values of Queue and commented functions per script.

    2. Commented imports from the list:

      List

      com.sap.aii.mapping.api, com.sap.aii.mapping.lookup, com.sap.aii.mappingtool.tf7.rt, com.sap.aii.tpm, com.sap.aii.af.service.cpa, com.sap.aii.af.lib.mp.module, com.sap.aii.af.lib.mp.processor, com.sap.aii.af.lib.ra.cci, com.sap.aii.af.lib.util, com.sap.aii.af.service.administration.api, com.sap.aii.af.service.administration.api.cpa, com.sap.aii.af.service.administration.api.i18n, com.sap.aii.af.service.administration.api.monitoring, com.sap.aii.af.service.cpa, com.sap.aii.af.service.headermapping, com.sap.aii.af.service.idmap, com.sap.aii.af.service.resource, com.sap.aii.mapping.api, com.sap.aii.mapping.lookup, com.sap.aii.mappingtool.tf7.rt, com.sap.aii.security.lib, com.sap.engine.interfaces.messaging.api, com.sap.engine.interfaces.messaging.api.ack, com.sap.engine.interfaces.messaging.api.auditlog, com.sap.engine.interfaces.messaging.api.exception, com.sap.engine.interfaces.messaging.api.pmi.

    3. Commented functions containing LookupManager, container or Thread.currentThread and added return @@@ from them (for void functions, result.addValue is added).

    4. Replaced StreamTransformationException with Exception.

    5. Skipped TPMArchive.jar, CPAServiceArchive.jar, EJBJEEArchive.jar during migration.

  11. [Common] BTP installation improvements:

    1. Updated NodeJS version for app router.

    2. Increased session timeout from default 15 min to 60 min.

    3. Changed version of PostgreSQL DB engine to 16.

  12. [Common] Improved configuration of object licenses for event mesh topics in order to load them by request.

  13. [Common, Integration Suite] Enhanced agent connection tests to check event mesh configuration.

  14. [FIX, Change Management] Fixed an issue when integration objects were always synchronized forcibly.

  15. [FIX, DevOps, CPI] Fixed an issue when sender and receiver parameters were lost during IFlows transport.

  16. [FIX, PI→CPI Migration] Fixed an issue when exclusion of a particular Operation Mapping handled incorrectly in migrated IFlows with Extended Receiver Determination.

Notes for upgrade from 2503 to 2504

  1. Build has data migration of Alerts lifetime period (days) config.

  2. It’s required to process forcible synchronization (options Synchronize objects forcibly and Rebuild links for the latest versions forcibly) of All registries for CPI agents from Change Tracking Tool → Tracked Objects page to initialize B2B Scenarios and link them with other objects.

  3. It’s required to update approuter\package.json and approuter\xs-app.json files if Figaf Tool is deployed to SAP BTP, Cloud Foundry. You can download new archive from repository.

    Deploy the application by command cf push --vars-file vars.yml.

2503.3

  1. [DevOps, CPI, Api Management] Added a possibility to exclude objects denied by 'Deny if matches' criteria on first landscape from dev scope of composite landscape.

    Define bootstrap parameter irt.devops.exclude-denied-objects-from-dev-scope = true in order to exclude denied objects from dev scope of composite landscape,

  2. [DevOps, CPI, Api Management] Extended object name pattern criteria configuration to specify object types.

2503.2

  1. [DevOps, CPI] Improved version comparison algorithm to support comparison of major.minor.micro.timestamp versions.

    Only versions having the same signature can be compared, otherwise object will be imported to target system.

2503.1

  1. [PI→CPI Migration] Added S_UNB elements support for B2B scenario migration.

  2. [FIX, PI→CPI Migration] Fixed an issue when receivers/interfaces inclusion could work incorrectly when there were more than 10 receivers.

2503

  1. [Testing Tool, PRO] Added a possibility to forcibly use BI caption for inbound message during recording (see Recording Configuration tab). Supported only for SAP Log Module message retrieving way.

  2. [Testing Tool, CPI] Changed sender adapter type to ProcessDirect for Figaf IFlows created during testing (e.g. Mock IFlows) if original IFlow has Allowed Headers configured *.

  3. [Testing Tool, CPI] Improved mock testing of IFlows having Send step. Now related test run result will not be created because Send step is replaced by RequestReply (because HTTP call to a mock server can be done only with a RequestReply) in mock IFlow.

  4. [Testing Tool, Api Management] Implemented manual (forcible) API Proxy policies addition/deletion on Integration Object page.

  5. [Change Management, CPI] Added change tracking for alternative partner objects (check supported objects here).

  6. [DevOps, CPI] Added OAuth2 Client Credentials type to the supported security content reference types configured on transport configuration of the IFlow.

  7. [DevOps, PRO] Added traces of directory WS warnings in transport traces.

  8. [DevOps, CPI, Api Management, UI] Simplified configuration of technical/display name rules for parameter mapping rules of the landscape adding possibility to use the same mapping for all technical/display name rules.

  9. [PI→CPI Migration] Extended modes for function libraries migrations to be able to map functions individually (see Shared artifacts mode for more details).

  10. [PI→CPI Migration] Supported 1.0.9 of pipeline concept.

  11. [PI→CPI Migration] Added PO-CPI XML conversion for B2B scenario migration.

  12. [PI→CPI Migration] Improved migration and replaced Figaf MappingParameters.groovy script with direct parameters usage.

  13. [PI→CPI Migration] Added a comment in the migrated Groovy script above functions having a type "All Values of Queue".

  14. [PI→CPI Migration] Added EdiXmlConverter.groovy to the script collection in the DevOps connector package and added its usage to B2B scenario migration.

  15. [FIX, Testing Tool, CPI] Fixed recording with fetch policy Message Processing Log IDs. Sometimes messages were recorded partially.

  16. [FIX, Change Management, CPI] Fixed BPMN model diagram in scenario documentation.

  17. [FIX, DevOps, CPI] Fixed an issue when versions with timestamp couldn’t be compared successfully.

  18. [FIX, Monitoring, CPI] Fixed average computation time on CPI Statistics Overview.

  19. [FIX, Common] Fixed integration objects Figaf Tool public API to work correctly for CPI objects.

Notes for upgrade from 2502 to 2503

  1. It is required to process forcible synchronization for CPI agents from Integration Objects page to initialize collection of Send steps that should be ignored in mock testing.

  2. It is required to process forcible synchronization for Api Management agents from Integration Objects page to initialize Has Figaf Policies parameter.

2502.3

  1. [FIX, Common, CPI] Fixed integration suite url recognition when integrationsuite token is included in the id of the system. It leaded to the issue because public API url was also recognized as integration suite url.

2502.2

  1. [FIX, PI→CPI Migration] Fixed an issue occurred during Message Mapping conversion.

2502.1

  1. [PI→CPI Migration] Upgraded JMS component version for JMS retry channel mapping templates.

  2. [PI→CPI Migration, DevOps, CPI] Extended limit of JMS queue name upto 80 characters.

  3. [FIX, Testing Tool, CPI] Fixed an issue when JMS queue name was truncated in the test object when it contains externalized parameter.

The tool doesn’t update JMS component version during creation of test IFlows, import, rollbacks, etc. So if JMS component version isn’t the latest in IFlows used for testing and devops, the IFlows might have problems with JMS queue name due to previous limit 20 characters used in older JMS component versions.

Notes for upgrade to 2502.1

  1. Build has data migration of JMS component version for JMS retry channel mapping templates.

2502

  1. [Testing Tool, Api Management] Supported recording and testing of API Proxy objects. See requirements, description and example e2e testing of Api Proxy (Api Management).

  2. [Testing Tool, Integration Suite] Supported recording and testing of Event Mesh topics. See description and example e2e testing of Event Mesh topics.

  3. [Testing Tool, PRO] Implemented recording of additional message stages from PI system to be able to use them during PI→CPI test case migration. The stage 1.1 is recorded for additional inbound EDI XML message payload if:

    • sender channel is EDI Separator;

    • sender channel has EDI conversion modules.

  4. [Change Management, Integration Suite] Added a possibility to skip synchronization of TPM registry configured on CPI agent configuration).

  5. [Monitoring, Integration Suite] Added Event Mesh Monitoring.

  6. [PI→CPI Migration] Supported migration license for Operation Mappings without linked ICO.

  7. [FIX, Testing Tool, CPI] Fixed an issue when messages were sent to wrong endpoint in case of Sender IFlow usage. It is required to recreate the test case.

  8. [FIX, Change Management, Integration Suite] Fixed an issue when TPM Agreement Templates and Agreements weren’t synchronized.

  9. [FIX, Common] Fixed links in email notification (BTP installation).

Notes for upgrade from 2501 to 2502

  1. It is required to process forcible synchronization for Api Management agents from Integration Objects page to initialize integration objects for Api Proxy objects.

  2. It’s required to update approuter/xs-app.json file if Figaf Tool is deployed to SAP BTP, Cloud Foundry. You can download new archive from repository.

    Deploy the application by command cf push --vars-file vars.yml.

2501.1

  1. [FIX, Testing Tool, CPI, Only for BTP deployment] Fixed an issue occurred during messages sending to IFlows deployed on Cloud Integration runtime.

2501

  1. [Testing Tool, CPI] Extended testing support for scenarios having HTTP endpoint with /* when it’s an empty value instead of /*.

  2. [Testing Tool, CPI, Integration Suite] Added support of sending test data to on-premise edge systems for SAP BTP deployment.

  3. [Testing Tool, PRO] Added an option on PI agent that enables polling of messages without scenario id if no messages were found during the polling with scenario id. Use that option only when you know that ICO logs messages without scenario id because polling without scenario id may fetch messages that don’t belong to the target scenario. Read more about the setting here.

  4. [Support Tool, CPI] Added a possibility to notify about expired retry attempts for IFlows that are not designed to escalate messages when there are no more retry attempts (read more here).