2026
2609.2
-
[
FIX,Integration Suite] Fixed deployment to Integration Suite systems with an Edge Integration Cell runtime: an IFlow whose runtime profile points to the Edge runtime was deployed to Cloud Integration instead. The runtime is now taken from the IFlow’s runtime profile on the tenant everywhere Figaf Tool deploys an IFlow:Deployon the Landscape Overview page (theRuntimeselection in the dialog still applies to non-IFlow artifacts only), transports withDeploy after transport, distribution configurations withDeploy uploaded objects, restore withDeploy restored objects(the restored IFlow also gets its last stored configuration back), test IFlows of the Testing Tool (Delete test IFlowsnow undeploys on Cloud Integration and on every Edge runtime of the agent) and PI to CPI migration with an EdgeRuntime ProfileandTry to deploy after migration. Agents without an Edge Integration Cell runtime and IFlows running on Cloud Integration behave as before.
2609.1
-
[
PI→CPI Migration] Added support for ICOs with a wildcard (*) sender to PI to CPI migration. See Wildcard ICO migration. -
[
PI→CPI Migration] Added support for ICOs with a wildcard (*) receiver (receiver channels defined in Receiver Agreements) to PI to CPI migration. See Wildcard ICO migration. -
[
FIX,PI→CPI Migration] Fixed PI to CPI migration of an ICO with an interface split where several receiver interfaces use the same File receiver channel with content conversion inFigaf Convertermode. -
[
FIX,DevOps] Fixed the calculation of the next ticket and transport number when theTicket prefixorTransport prefixconfigured for a landscape starts with the standard prefix (for example,TRANSPORT-QAnext to the standardTRANSPORT). IDs created with the longer prefix (such asTRANSPORT-QA-1) were counted for the standard prefix as well, so ticket creation andStart Transportscould fail.
2609
-
[
DevOps] Improved batchResolveandCancelof 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 theLandscape Overviewactions 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’sKey Field Nameis 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,additionalLastFieldsandignoreRecordsetNameare 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.The content converter (2.2.0) is downloaded during each migration, so every newly migrated channel with content conversion gets the new behavior: fixed-length and separator values are trimmed by default, and blank or unmatched lines are dropped instead of raising an error. The XML produced by such channels can differ from earlier migrations. -
[
B2B] Added an endpoint value to theManage Communicationsdialog 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: theRecipient URLof an AS2 receiver, theAddressof a Process_Direct, IDOC, SOAP_1.x or SAP RM receiver, and theAddressandDirectoryof 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 errorAttribute name "…" associated with an element type "…" must be followed by the ' = ' characterwhen 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 parabecomesnew_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 withCannot read resource with ID … Not Found from Configurations service). This affected theAS2 Inbound Decryption Configurationsof a company or subsidiary, and theSignature Verification Configurationsof trading and communication partners whoseAliasdiffers from theAS2 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 theAdd modulesoperation on the Integration Objects page failing with an error when theUse the most appropriate messages logging approach by default per scenariooption is enabled and the selected object usesICO Logging(no modules required). Such objects are now skipped.
Notes for upgrade from 2608 to 2609
-
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 forciblyandRebuild links for the latest versions forcibly) of TPM registry for CPI agents fromChange Tracking Tool → Tracked Objectspage to update companies, subsidiaries, trading partners or communication partners. -
It’s required to update
manifest.ymlandapprouter/xs-app.jsonfiles if Figaf Tool is deployed to SAP BTP environment: the application router moves to thecflinuxfs5stack, and public API calls (/oauth/token,/api/v1/…) get their ownpublic-api-destination. You can download new archive from repository.Deploy the application by command
cf push --vars-file vars.yml.Check that
cflinuxfs5is offered in your landscape (cf stacks) before the push. If yourapprouter/package.jsonstill pinsnodeto18.xor20.x(descriptors older than 2603), take the current one with22.xas well - the Node.js buildpack doesn’t stage those versions anymore, on either stack.
2608
-
[
B2B] Enhanced Subsidiary creation with per-system (Dev/Test/Prod) security details and automatically generated, uniquely named communication user accounts and security entries. -
[
B2B] Added aUses Communication Partneroption to Trading Partner creation. When enabled, only the partner profile basics and identifiers are created — no systems and no communications. -
[
B2B] Allowed free-text Type System Versions when creating Subsidiaries and Trading Partners. For type systems that support it (SAP IDoc, SAP S/4HANA Cloud/On-Premise SOAP, Custom Messages) a version such as750can be typed in. -
[
B2B] Enhanced B2B Scenarios overview: theActivatedindicator now reflects whether any agreement version is active (not only the latest), and the B2B Scenario/Agreement links now open the active version by default (with the option to open either the active or the latest version). -
[
DevOps,B2B] Changed the B2B import for Locked Version landscapes so B2B objects (the TPM archive) are imported only after the rest of the transport is clean. If any other object of the transport has an unresolved validation exception or error, the B2B import is skipped with an explanatory message and runs on the next attempt once the problems are resolved or suppressed. This prevents the TPM archive from being imported twice and avoids a half-deployed state on the target.This changes the transport philosophy for B2B objects on Locked Version landscapes: unlike other objects (still imported independently), a single broken object now holds back the B2B import until it is fixed or removed from the ticket. -
[
DevOps,B2B] Improved the B2B transport error shown when an Agreement or Agreement Template references a MIG/MAG that no longer exists on the Integration Suite (usually deleted). The notification now lists every affected object together with the missing MIG/MAG id, so it’s clear which objects must be updated before retrying. -
[
DevOps,B2B] Made Mapping Guideline (MAG) a licensed object. A MAG now requires its own object license to be used in DevOps and can be licensed in advance fromConfig → License → Add Object Licenses. A Message Implementation Guideline (MIG) needs no license. -
[
DevOps] Added aShow only pendingoption to the DevOpsTicketsandTransportstables that hides items in a final state (transports:IMPORTED,REVERTED,CANCELED,DECLINED; tickets:COMPLETED,MIGRATED,CANCELED). The filter runs on the server and the choice is remembered per browser. -
[
Change Management,DevOps] Added a DevOps ticket filter to the Landscape Overview so tracked objects can be filtered by one or more DevOps tickets. -
[
Change Management] Added aLandscape Overviewaction to tracked objects that opens the Landscape Overview for the object’s composite landscape, filtered to that object. The action is hidden for object types not shown on the Landscape Overview. -
[
Change Management,B2B] Added aLandscape Overviewbutton to the B2B Scenarios overview. With one or more scenarios selected, you pick a composite landscape assigned to the agent and are taken to the Landscape Overview filtered for the selected scenarios. -
[
Integration Suite] Added API Management access credentials (URL, client id, client secret) to Integration Suite CPI agents, together with a newAPI Management Accesscheck in the agent Connection Test. The fields are optional and only needed when API Management features (such as B2B ProtectedAPI) are used (for example, during Subsidiary creation). -
[
FIX,DevOps,Api Management] Fixed an error when creating a composite API Management landscape with three or more landscape items (theNextstep failed with a server error). -
[
FIX,DevOps,CPI] Fixed the display of the Git pipeline validation report (Git Pipeline Validation Status). -
[
FIX,Common] Fixed the public APIPUT /api/v1/agentthat updated only a small subset of agent settings and silently reset all others to their defaults. -
[
FIX,Change Management,B2B] Fixed slow creation and deletion of B2B business entities (subsidiaries, trading partners, communication partners) that triggered a full synchronization of the whole TPM registry. Only the affected object is now synchronized, reducing the post-processing from minutes to seconds. -
[
FIX,B2B,PI→CPI Migration] Fixed the B2B Migration Overview failing to load when a migration record referenced a company/subsidiary, agreement, operation mapping or partner profile tracked object that no longer exists (for example a deleted agent, or an object re-created in SAP). -
[
FIX,B2B,PI→CPI Migration] Fixed Type System Version validation wrongly blockingEANCOMin Agreement creation and PI to CPI B2B migration. Version validation is now suppressed forEANCOM, whose Integration Advisor version groups don’t map to a single standard version. -
[
FIX,PI→CPI Migration] Fixed an issue when PI to CPI migration failed for integrations where PI defined sender agreements with*wildcards.
2606.4
-
[
Infrastructure,Security] Added support for Microsoft Entra authentication to Azure Database for PostgreSQL flexible server. Figaf Tool can now log in with a Microsoft Entra access token instead of a database password, so no database credential has to be stored in the deployment anymore - 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.
2606.3
-
[
FIX,DevOps,Integration Suite] Fixed an issue when theSet Transport Configuration as 'Default Values' for Edge runtimeoption (composite landscape configuration) broke IFlows with a scheduler. Externalized scheduler parameters (typecustom:schedule) are now excluded from the default values replacement, and the replacement validation is skipped for IFlow configuration only transports.
2606.2
-
[
FIX,Change Management,B2B] Fixed an issue when synchronization of integration objects failed for CPI agents with TPM if a B2B scenario had a party identifier (initiator/reactor sender or receiver ID) longer than 36 characters.
2606.1
-
[
DevOps,Integration Suite] Added aSet Transport Configuration as 'Default Values' for Edge runtimeoption to the composite landscape configuration. It works around the limitation that an Edge Integration Cell runtime configuration can’t be read or written programmatically: during transport the configured values of affected IFlows are written as default parameter values so the configuration can still be delivered to the target. The behavior applies per IFlow — only IFlows whose runtime profile resolves to an Edge Integration Cell runtime on the target are affected, while IFlows running on Cloud Integration keep the normal separation of default and configured values.
2606
-
[
AI,Security,CPI] Added the ability to connect Claude.ai (and other MCP clients) to Figaf as a custom connector using OAuth 2.1 Authorization Code with PKCE, so the AI client can call Figaf’s MCP tools. Login reuses your existing Figaf authentication (local users and SAP BTP); connecting requires theIRTMcpReader(or admin) role and access is read-only. See the section for more details. -
[
AI,CPI] Added aPreview Matched Objectsaction to the AI IFlow documentation scope filters, so you can review the exact packages and IFlows matched by your package/IFlow regex filters (with validation of invalid regex) before running a documentation batch. -
[
Change Management,CPI] Enhanced synchronization to recognize and persist discovery (standard) content. Design artifacts belonging to Configure-only discovery packages are now flagged as standard content on the tracked object, so they can be identified across all synchronization flows. -
[
DevOps,B2B] Added anAllow B2B transports of Draft stateoption to the composite landscape configuration (off by default). When enabled, agreements, agreement templates and B2B scenarios in Draft state can be added to and transported through DevOps. Drafts of Message Implementation Guidelines and Mapping Guidelines are always blocked. -
[
DevOps,B2B] Enhanced the landscape configuration for TPM with aCustomize TPM import settingsoption that configures agreement import selections similar to SAP’sAction Import Agreementscreen. DevOps then applies these import options when importing the TPM agreement. -
[
DevOps,CPI] Added support for transporting SAP standard content (from Discover) through DevOps tickets. New standard content is created as a copy from Discover and existing content is matched, keeping standard packages' unmodified status through the transport chain (including via Virtual agents). If the source has a pending Discover update or source and target versions differ, the transport is blocked. Works with composite landscapes and supports a single object, a package, or a package with all dependent objects. -
[
DevOps,CPI] Added a parameter mapping rule for discovery content technical names so Discovery Content packages can be mapped. The suffix is applied via SAP’s Discover copy API against the original catalog package, keeping copied packages and artifacts consistently named across the landscape. -
[
PI→CPI Migration,B2B] Added aDelete Recordsfunction to the PI to CPI migration overview. It removes the migration record from Figaf. Nothing is deleted in SAP and the action is restricted to the Admin role. -
[
B2B] Added support for SAP Integration Suite agreement versioning. Synchronization detects changes in older agreement versions, not only the latest. -
[
B2B] Enhanced B2B Scenario tracked object to store more information about MAG. -
[
B2B] Added certificate status to the Company, Subsidiaries, Trading Partner and Communication Partner tracked objects. For entities with multiple certificates the worst status wins, andN/Ais shown when there are no certificates. -
[
B2B] Enhanced the Create Agreement function to pick which MAG version to use. -
[
Common,CPI] Added new agent connection tests for B2B access (Agreement Templates, MAGs and Interchanges - for Integration Suite agents with B2B enabled) and Partner Directory access (for all CPI agents). -
[
FIX,DevOps,B2B] Fixed B2B transport so that outbound Functional Acknowledgement channels assigned to a Trading/Communication Partner communication are now remapped correctly. Previously such partner-specific acknowledgement channels were only matched against Company/Subsidiary communications, resulting in a wrong source reference. -
[
FIX,B2B] Fixed an issue when B2B agreements deleted via Figaf while still active left stale state at SAP, so an identical agreement could not be re-created afterwards. Agreement deletion now blocks if any selected agreement is still active and asks you to deactivate it first. -
[
FIX,DevOps,CPI] Fixed a false validation error in DevOps transports where credentials referenced through parametrized values (Camel Simple expressions) were incorrectly reported as missing on the target system. Such dynamic references are now skipped during the credential existence validation, while static references are still validated. -
[
FIX,API Hub] Fixed broken integration with API Hub agents.
Notes for upgrade from 2605 to 2606
-
Build has data migration for SAP Integration Suite agreement versioning that renames old agreement version revisions and removes redundant data.
-
Build has data migration that switches existing API Hub agents from the NEO platform type to Cloud Foundry so authentication works correctly.
-
It’s required to process forcible synchronization (options
Synchronize objects forciblyandRebuild links for the latest versions forcibly) of TPM registry for CPI agents fromChange Tracking Tool → Tracked Objectspage to rebuild per-version agreement data and agreement-to-scenario links, populate the newMAG UsageandMAG Mapping Typefields, populate certificate status for Company/Subsidiary/Trading Partner/Communication Partner, and flag existing discovery (standard) content.
2605.5
-
[
Common,CPI] Optimized Custom IdP authentication (Sign on to SAP CPI CF/IS using SAML2) to no longer send a request tosaml.figaf.comduring login.saml.figaf.comis still the SSO URL registered in the SAP Trust Configuration and must remain configured, even though nothing connects to it during login anymore.
2605.4
-
[
Testing Tool,Integration Suite] Improved externalized parameters upload for the test (Figaf/Mock) IFlow to avoid upload of theSAP_ProfileIdparameter when there is only one configured runtime. -
[
FIX,Testing Tool,CPI] Fixed an issue when the test (Figaf/Mock) IFlow missed configured values of externalized parameters in the source IFlow (only default values were used in the test IFlow). -
[
FIX,Testing Tool,CPI] Fixed an issue when the test (Figaf/Mock) IFlow could contain duplicated senders. Each sender now gets a unique participant name (Sender,Sender1, …) during test IFlow generation.
2605.3
-
[
FIX,PI→CPI Migration] Fixed an issue when PI to CPI migration failed for integrations where PI defined interface determinations or receiver agreements with*wildcards.
2605.2
-
[
FIX,B2B] Fixed links from Figaf Tool to the SAP TPM Agreement that stopped working due to versioning function for TPM agreements.
2605.1
-
[
PI→CPI Migration] Added a possibility to override the defaultFigafMigrationscript collection used during PI to CPI migration via theirt.config.pi-to-cpi-migration-script-collection-technical-nameapplication property (go to Application properties for more information). It allows using a custom script collection to deliver faster updates of migration scripts.Additionally, the
preserveInterchangeDataparameter (with default valuefalse) is now added to the content modifier during migration to simplify its overriding totrue. -
[
FIX,B2B] Fixed an issue when B2B Scenarios using a custom main flow weren’t displayed in the B2B Scenario overview and weren’t available for selection in the Create Agreement function, although they were shown in Tracked Objects.
Notes for upgrade to 2605.1
-
It’s required to process forcible synchronization (options
Synchronize objects forciblyandRebuild links for the latest versions forcibly) of TPM registry for CPI agents fromChange Tracking Tool → Tracked Objectspage to correctly display B2B Scenarios using a custom main flow.
2605
-
[
AI,Change Management,CPI] Added AI-generated documentation for IFlows. WhenEnable IFlow Documentationis configured for a CPI agent, the documentation is generated asynchronously during synchronization and can also be generated/regenerated on demand on the IFlow object page. -
[
AI,CPI] Added Figaf AI assistant that allows interacting with the tool using natural language to search IFlows (by name, package, last change date, sender/receiver systems), discover IFlow dependencies and compare IFlow versions. It’s available as an in-app AI Assistant chat.IFlow payloads are shared with the configured LLM for processing. -
[
B2B] Added presets (pre-defined table views) to the B2B Scenario overview that define which columns are visible. -
[
B2B] AddedSender Type System,Sender Type System Version,Receiver Type SystemandReceiver Type System Versioncolumns to the B2B Scenarios and CSV report. -
[
B2B] Enhanced Create Agreement function to copy existing custom IFlows into new partner-specific IFlows. For each custom flow slot (Main, Pre, Post) a mode can be selected:Use Template Assignment,Reuse / replace existingorCopy into new. -
[
DevOps] Enhanced error message shown when an object transport is denied to include the reason (denying rule) of denying. -
[
DevOps,CPI] Enhanced transport of IFlow configuration that has externalized scheduler parameters (typecustom:schedule). A transport validation now warns that such configuration may not be applied correctly by SAP and should be reviewed and updated manually afterwards. -
[
FIX,PI→CPI Migration,B2B] Fixed an issue when agreements created via agreement creation or PI to CPI migration couldn’t be activated becauseInitiatorandReactorroles were determined incorrectly. The B2B Scenario direction is now determined correctly for both agreement creation and PI to CPI migration. -
[
FIX,Testing Tool] Fixed an issue when thePartnerfield of a test case was initialized with empty values during test case creation from a recording request with{{OUT}}directive. -
[
FIX,Common] Fixed the confirmation dialog ofModify Object Licensesto show the correct message (The following objects will be updated in the license) and list only the changed objects and license types instead of all licensed objects.
Notes for upgrade from 2604 to 2605
-
It’s required to process forcible synchronization (options
Synchronize objects forciblyandRebuild links for the latest versions forcibly) of TPM registry for CPI agents fromChange Tracking Tool → Tracked Objectspage to initializeSender/Receiver Type SystemandType System Versionfor B2B Scenarios. -
Build has data migration that creates the default
Basic Overviewpreset for B2B Scenario overview.
2604.2
-
[
FIX,CPI] Fixed Custom IDP integration after changes on SAP side (it stopped working on some tenants from 2026-05-28). If some Agent system is not updated yet and requires old approach, it’s possible to fallback by definingLogin Urlon agent manually in the following format:<authorization-url>/saml/discovery?returnIDParam=idp&entityID=<authorization-url>&idp=<idp name from agent>&isPassive=truewhere:-
<authorization-url>- copy base url from SSO URL (for examplehttps://tenant-1.authentication.eu10.hana.ondemand.com) -
<idp name from agent>- it’sidp-<first 8 charecters from Agent entiity id>, for exampleidp-bd21e2af. Take this value from Trust Configuration page in BTP Cockpit.
-
2604.1
-
[
Integration Suite] AddedApplication idparameter on Agent page for Integration Suite agents with Custom IdP. It’s used to work around the authentication problem when Integration Suite forcibly chooses IAS authentication (authorization redirect URL is not available in the initial authentication requirement response in such case). -
[
FIX,PI→CPI Migration,B2B] Fixed several UI issues related to B2B migration profile.
2604
-
[
Change Management,Integration Suite] Enhanced deployment of non-IFlow artifacts (Value Mappings, Script Collections, Message Mappings, Function Libraries, Imported Archives) on Landscape Overview page. Non-IFlow artifacts are now deployed only to runtimes resolved from their linked parent IFlows by default. -
[
Change Management,Api Management] Enhanced changes detection for API Proxy synchronization. -
[
B2B] Enhanced Agreement Template tracked object to include version. AT versions are now properly synchronized and stored. Draft Agreement Templates are denied for transport creation. -
[
B2B] Enhanced B2B Scenario data to be stored in the database and initialized during synchronization (including IFlow runtime status/version, MIG/MAG status), enabling backend filtering and sorting for these columns. -
[
B2B] Enhanced B2B Scenario overview with renamed and additional columns for MIGs/MAGs:Sender/Receiver MIG Newest Design Status,MAG Newest Design Status,Sender/Receiver MIG Newest Design Version,MAG Newest Design Version,Sender/Receiver MIG Assigned VersionandMAG Assigned Version. -
[
B2B] Added Agreement Template version column to B2B Scenario overview (visible whenShow additional columnsis enabled). -
[
B2B] Improved version chain handling for Agreement Templates, MIGs, and MAGs. When the latest version is deleted, the previous still-active version is now used and considered as actual. -
[
B2B,PI→CPI Migration] Enhanced B2B Create/Migrate Agreement function to only list Agreement Templates that are active or latest draft, with version number displayed. -
[
B2B,PI→CPI Migration] Enhanced agreement creation to support selection of Communication Partner. If Communication Partner is selected, Agreement Template list is filtered accordingly. -
[
B2B,PI→CPI Migration] Added support forCustomer_TS_IDOCTypeSystem, treated as equivalent toSAP_IDocduring agreement creation and PI to CPI migration. -
[
PI→CPI Migration] Updated migration templates for communication channels with Cloud Connector and Runtime Profile support. AddedLocation IDconfiguration,Enable Cloud Connectoroption for channel mapping templates, andRuntime Profileselection on migration page. -
[
Support Tool] Added minimum validation forAlerts lifetime period (days)configuration to prevent defining the value less than 3 days. -
[
Common] Removed Figaf Gradle plugins declaration from generated git repositories. -
[
FIX,Testing Tool] Fixed an issue when additional outbound message withPAYLOAD_SNAPSHOTstate was polled during recording or polling test results whenTrading Partner Management V2package was used. -
[
FIX,Testing Tool] Fixed an issue when encoding of special characters (e.g.Ö) failed when sending test messages to SOAP or IDoc adapter based flows. -
[
FIX,Testing Tool,B2B] Fixed an issue when B2B testing failed ifB2B Package for test case runningwas configured toB2B Integration Factory - Cloud Integration - Trading Partner Management. Enhanced dynamic endpoint determination for bothTrading Partner Management V2andB2B Integration Factorypackages. -
[
FIX,DevOps,B2B] Fixed an issue when transport was marked as successfully imported although archive build failed with error while fetching MIG.
Notes for upgrade from 2603 to 2604
-
It’s required to process forcible synchronization (options
Synchronize objects forciblyandRebuild links for the latest versions forcibly) of TPM registry for CPI agents fromChange Tracking Tool → Tracked Objectspage to initialize B2B Scenario data (IFlow runtime status/version, MIG/MAG status/version), Agreement Template versions, Communication Partner data and MIG/MAG assigned versions. -
It’s required to process Init/Reinit Git repository operation on Agents page for CPI and Api Management agents with configured Git integration. Then, if automatic update of
build.gradle,settings.gradleis not configured, copy the content of updated templatesbuild-irt.gradleandsettings-irt.gradleto these files manually. -
Build has data migration to update default PI to CPI migration templates with Cloud Connector and Runtime Profile support.
-
Build has data migration of deletion of Agreement Templates versions.
2603
-
[
Infrastructure] Migrated the project to Java 21 (LTS). If you use Docker distribution: standard or BTP, the tool is updated automatically. If you use on-premise standalone instance, please update to Java 21 runtime before running newer version because Java 17 runtime isn’t supported anymore (steps for update are described here). -
[
B2B] Added support of agreement creation. -
[
B2B] Supported filtering during synchronization of B2B objects. This filter-based synchronization is executed:-
from Ticket page
-
synchronizations during importing transport
-
after agreement creation
-
synchronizations during agreement activation, update, deactivation and deletion
-
PI to CPI migration in B2B mode
-
-
[
B2B] Added archiving settings to B2B Scenario table and CSV report. -
[
B2B] Added version and status of MIGs/MAGs related to B2B Scenario to the table and CSV report. -
[
B2B] Added runtime status, runtime version and design version of IFlows related to B2B Scenario to the table and CSV report. -
[
PI→CPI Migration,B2B] EnhancedType SystemandType System Versiondefinition and added validations related to selectedPartner ProfileandB2B Scenario.The enhancement is
Type SystemandType System Versiondefinition and prefill depending on configurations:-
If Agreement Template has
Type SystemandType System Versiondefined for company and trading partner details, then the values will be set by Figaf tool and not changeable. -
If Agreement Template doesn’t have
Type SystemandType System Versiondefined and B2B Scenario has them defined, then the values will be set by Figaf tool and not changeable. -
If neither Agreement Template nor B2B Scenario don’t have
Type SystemandType System Version, then the configurations will not be defined by Figaf tool and will be selectable. -
If detected
Type SystemandType System Versionaren’t assigned the respective Sender/Receiver Systems, then warning will be shown.
-
-
[
Testing Tool,CPI] Supported polling of all MPLs when amount of dependent messages is more than 1000. -
[
DevOps] Changed denying rules criterias to use OR condition instead of exclusive one. -
[
DevOps,CPI] Added an option on landscape level (Use 'Default Value' of Externalized Parameters instead of 'Configured Value') to change IFlow Externalized Parameters values used in transport configuration. IFlow Externalized Parameters have 'Default Value' and 'Configured Value'. When this option is enabled and the parameter has 'Inherit from source' mode, the 'Default Value' will be used. -
[
Change Management,Integration Suite] Supported linking between B2B Scenario and IFlow if IFlow URL is configured via externalized parameters. -
[
FIX,Testing Tool] Fixed an issue when X12 message type wasn’t detected properly for documents having BIG segment with 2 elements. -
[
FIX,Testing Tool] Fixed an issue when file type and encoding weren’t recalculated in the Message and Test Run Result messages. -
[
FIX,DevOps] Fixed an issue when only one transport validation tag was added into the warning message for transport items. -
[
FIX,B2B] Fixed an issue when agreement wasn’t updated in Integration Suite if B2B Scenario name was changed. -
[
FIX,Common] Fixed http client reset to reset client related to MIGs/MAGs synchronization.
Notes for upgrade from 2602 to 2603
-
It’s required to update to Java 21 runtime (steps for update are described here).
-
It’s required to synchronize license to initialize
B2B Capabilities License End Date. -
It’s required to process forcible synchronization (options
Synchronize objects forciblyandRebuild links for the latest versions forcibly) of TPM registry for CPI agents fromChange Tracking Tool → Tracked Objectspage to initialize archiving settings for B2B Scenarios. -
It’s required to process forcible synchronization (options
Synchronize objects forciblyandRebuild links for the latest versions forcibly) of CPI registry for CPI agents fromChange Tracking Tool → Tracked Objectspage to initialize 'Default Value' for IFlow Externalized Parameters. -
It’s required to update
nodeversion to22.xand@sap/approuterversion to^21.2.0inapprouter/package.jsonfile if Figaf Tool is deployed to SAP BTP environment. You can download new archive from repository.Deploy the application by command
cf push --vars-file vars.yml. -
Build has data migration to enable
Use oauth url for testingsettings for CPI agents related to Integration Suite tenants.
2602.2
-
[
FIX,Change Management] Fixed an issue when synchronization results were leaked in Hazelcast cache when object type synchronization failed.
2602.1
-
[
Testing Tool,CPI] Supported change ofAgent Objectassigned to the test case for IFlow Chains.If IFlow Chains don’t match fully (the same
Sender IFlowandChained IFlows), then the warning will be shown. If you confirm the reassignment, it can break the test case completely as each message of the chain test case uses the related IFlow technical name as an additional identifier for correlation and matching.
2602
-
[
Change Management,CPI] Added a possibility to deploy Value mappings, Script collections, Imported Archives, Function libraries, and Message mappings and their dependent artifacts on Landscape Overview page. -
[
Change Management,CPI] Added a possibility to undeploy Value mappings, Script collections, Imported Archives, Function libraries, and Message mappings on Landscape Overview page. The objects can be undeployed only if related parent objects (e.g. IFlows) are undeployed in the same request as well. -
[
DevOps,B2B] EnhancedAuto-activate B2B agreementsto activate not activated agreements and update edited agreements as well. -
[
DevOps,B2B] Added newSuppress warnings for Auxiliary B2B objects - allow imports alwaysoption on Landscape configuration page. -
[
DevOps,B2B] Implemented forcible transport option (with overwriting versions when it’s possible) for MIGs/MAGs. It works the following way: Figaf tool performs transport and if MIG/MAG isn’t imported successfully due to warningCan be imported - this will overwrite the existing object with potential loss of data, the user can suppress this warning and perform forcible import. -
[
DevOps,CPI] Implemented synchronization of previous system in addition to the dev and target systems during initial synchronization of import through landscape withLocked versionworkflow. -
[
B2B] Supported deletion of agreements. -
[
B2B] Supported deletion of trading partners and communication partners. -
[
FIX,Change Management,CPI] Fixed an issue when script wasn’t run successfully in Groovy IDE if the script produced more than 86 headers.
Notes for upgrade from 2601 to 2602
-
It’s required to process forcible synchronization (options
Synchronize objects forciblyandRebuild links for the latest versions forcibly) of TPM registry for CPI agents fromChange Tracking Tool → Tracked Objectspage to initialize correctReceiver Message Versionfor B2B Scenarios.
2601.2
-
[
DevOps,B2B] Supported import of parameters of Trading Partners, Company, Subsidiaries and B2B Scenarios. -
[
Common] Added bootstrap parametersirt.config.agent.skip-pi-user-access-api-availability-testandirt.config.agent.skip-pi-user-access-testto make the user API test optional for BTP deployment (go to Application properties for more information). -
[
FIX,Change Management,CPI] Fixed an issue when scenario documentation was not generated for IFlow having orphan step element.
Notes for upgrade to 2601.2
-
It’s required to process forcible synchronization (options
Synchronize objects forciblyandRebuild links for the latest versions forcibly) of TPM registry for CPI agents fromChange Tracking Tool → Tracked Objectspage to initialize parameters for Trading Partners, Company, Subsidiaries and B2B Scenarios objects.
2601.1
-
[
FIX,DevOps] Fixed an issue when ticket couldn’t be moved to next or previous stage if newer version of attached object was deleted. -
[
FIX,PI→CPI Migration,B2B] Fixed an issue when agreement update didn’t work during migration.
2601
-
[
Testing Tool,CPI] Supported configuration ofRequest Methodfor HTTP adapter in Send Message Requests. -
[
Change Management,CPI,CPIHelper] Supported debugging through CPIHelper. To enable it configureExternal IDE URLto<Figaf tool instanse>/#/groovy-ide/deeplink/in the related configuration of CPIHelper. -
[
Change Management,CPI] Enhanced accuracy in groovy scripts and implemented a possibility to configureCapabilityfor Figaf Bot.Capabilityis configured differently for the objects:-
UDF Script:
-
Default (Message Mapping - best practices)
-
Partner Directory
-
Security Material
-
Value Mapping
-
-
Groovy Script Step
-
Default (best practices)
-
Partner Directory
-
Security Material
-
Value Mapping
-
-
XSLT Mapping
-
Default XSLT best practices
-
-
-
[
Change Management,B2B] Implemented restoring of TPM objects when they marked 'deleted' due to empty api responses from Integration Suite. -
[
Change Management,B2B] Enhanced MIGs synchronization to group objects if even some error occurred during synchronization (e.g. connection issue). -
[
Change Management,CPI] Enhanced IFlow BPMN Context search based on AI embeddings splitting vector values to adapters and steps related to MessageFlows. -
[
DevOps] Added support of mass resolve/cancel of multiple selected tickets on Tickets page. -
[
DevOps,B2B] Enhanced agreements transport to considerSystemTypein addition toPurpose. -
[
DevOps,B2B] Added newAuto-activate B2B agreementsoption on Landscape configuration page. -
[
DevOps,B2B] Added newAttach all dependent objects for B2B transportsoption on Landscape configuration page. -
[
DevOps,B2B] Enhanced validations for B2B TPM transport through landscape withLocked versionworkflow. -
[
B2B] Extended PI to CPI migration configuration to enable automatic deployment of IFlow (Deploy MainFlow immediately after migrationoption) and activation of agreement (Activate TPM Agreement immediately after migrationoption). -
[
FIX,Change Management,B2B] Fixed an issue when tracked Object for Agreement Template was not updated new scenarios were created under the Agreement Template on Integration Suite. -
[
FIX,DevOps,CPI] Fixed an issue when rollback couldn’t be performed when transport had not the latest version of MIGs/MAGs. -
[
FIX,DevOps,B2B] Fixed an issue when only the latest version of MIGs/MAGs were attached to copied ticket.
Notes for upgrade from 2512 to 2601
-
It’s required to process forcible synchronization (options
Synchronize objects forciblyandRebuild links for the latest versions forcibly) of TPM registry for CPI agents fromChange Tracking Tool → Tracked Objectspage to initialize activation state of agreements.