Release notes

[DevOps] Improved batch Resolve and Cancel of tickets on the Tickets page. All selected tickets that can be resolved are resolved right away. For the others you can choose per ticket what to do (move to development, cancel or skip). Tickets whose transports were imported in one batch are still resolved all together or none. Resolving from a single ticket page is unchanged.

[Change Management, DevOps] Archived landscapes are no longer offered wherever a landscape is picked: Landscape Overview (including the Landscape Overview actions on Tickets, Object Info and B2B Scenarios), Migration to IS, the Home page landscape block and the landscape selection of the Change Log (Show versions across landscape). See Archive a landscape.

[Infrastructure, Security] Added support for Microsoft Entra authentication to Azure Database for PostgreSQL flexible server (first delivered in patch 2606.4; not included in 2608). Figaf Tool can log in with a Microsoft Entra access token instead of a database password, so no database credential has to be stored in the deployment - access is granted to an Azure identity (user-assigned or system-assigned managed identity, AKS workload identity or service principal) and revoked centrally in Entra ID. The mode is optional and off by default, so existing password-based deployments and other database systems aren’t affected. See the section for the configuration steps.

[PI→CPI Migration] Improved the migration of File sender channels with content conversion (Figaf Converter mode, see File Content Conversion migration) to follow SAP PI behavior more closely. The channel’s Key Field Name is now respected, so files whose key field is not the first field of the line are converted correctly. Enclosure signs (quoted CSV values), fieldContentFormatting, missingLastFields, additionalLastFields and ignoreRecordsetName are now read from the channel and reach the generated script. Lines that match no record type and blank lines are skipped with a warning instead of failing the conversion, and the generated script is always valid Groovy even when channel values contain quotes. The migration log now warns about File Content Conversion options that the Figaf converter doesn’t support, so a mismatch is visible before the IFlow runs.

[B2B] Added an endpoint value to the Manage Communications dialog of trading and communication partners, companies and subsidiaries, so it’s visible where each communication points without opening it in TPM. Values are shown exactly as configured: the Recipient URL of an AS2 receiver, the Address of a Process_Direct, IDOC, SOAP_1.x or SAP RM receiver, and the Address and Directory of an SFTP sender or receiver. All other senders and the system rows stay empty.

[FIX, PI→CPI Migration] Fixed the content conversion script generated for File sender channels producing broken XML (every field cut to its first character) when the field separator is a regular expression character such as |. Separators are now always treated as literal text.

[FIX, Change Management, B2B] Fixed agreement synchronization of Integration Suite agents failing with error Attribute name "…​" associated with an element type "…​" must be followed by the ' = ' character when a B2B scenario has a parameter name that isn’t a valid XML name (for example, a name with a space, a slash, a colon or a leading digit). Such names are stored in an encoded form in the B2B Scenario payload (new para becomes new_x0020_para); nothing changes in SAP, transports and agreement creation still send the original names. Agreements already stuck with this error are repaired by the first synchronization after the update, which reports the affected B2B scenario as changed once.

[FIX, DevOps, B2B] Fixed transported AS2 security configurations that couldn’t be activated in the target tenant (activation failed with Cannot read resource with ID …​ Not Found from Configurations service). This affected the AS2 Inbound Decryption Configurations of a company or subsidiary, and the Signature Verification Configurations of trading and communication partners whose Alias differs from the AS2 Partner ID. Such entries are now transported under the identifier SAP uses to find them, so the entry of the target’s purpose can be activated in TPM. Entries already transported by an earlier version must be deleted in the target tenant - see Transported security configuration can’t be activated.

[FIX, Testing Tool] Fixed handling of deleted integration objects in the Testing Tool. Deleted objects are no longer resolved as test objects automatically during test case creation (including B2B test cases created from an archive), can’t be linked to or assigned to test cases manually or through the public API, and test cases aren’t run on them anymore - such objects are skipped with a warning listing them, while the remaining test objects and test cases still run.

[FIX, Testing Tool, PRO] Fixed the Add modules operation on the Integration Objects page failing with an error when the Use the most appropriate messages logging approach by default per scenario option is enabled and the selected object uses ICO Logging (no modules required). Such objects are now skipped.

If you worked around the | field separator problem in a content conversion script generated by the PI to CPI migration by escaping the separator (fieldSeparator: "\\|" instead of "|"), revert it to "|" as soon as the IFlow uses the updated content converter (2.2.0). Separators are now treated literally, so the escaped value would be looked up as the two characters \| and break the conversion again. Re-running the migration regenerates the script with the new converter and discards the manual edit; if you replace the converter jar inside the IFlow by hand instead, revert the separator at the same time.

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 update companies, subsidiaries, trading partners or communication partners.

It’s required to update manifest.yml and approuter/xs-app.json files if Figaf Tool is deployed to SAP BTP environment: the application router moves to the cflinuxfs5 stack, and public API calls (/oauth/token, /api/v1/…​) get their own public-api-destination. You can download new archive from repository.