Release notes

2510

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

  2. [B2B] Supported Subsidiary creation (see Create Subsidiary).

  3. [B2B] Supported creation of new communications for Partner Profiles, Company and Subsidiaries.

  4. [B2B] Enhanced B2B Scenarios overview to include Agreement update status.

  5. [Testing Tool, B2B] Enhanced test case running to support both packages (package is configured on Agent page):

    • Cloud Integration - Trading Partner Management V2.

    • B2B Integration Factory - Cloud Integration - Trading Partner Management (with or without Enable simulation / skip endpoint delivery).

  6. [Testing Tool, PRO] Implemented split multi message document to separate payloads during polling when ICO logging approach is used.

  7. [Change Management, B2B] Added change tracking for Communication Partner (check supported objects here).

  8. [Change Management, B2B] Optimized tracked objects revisions creation for B2B objects. Now new revision is created only if object is changed, otherwise only the revision number is updated.

  9. [Change Management, CPI, PRO] Added a possibility to import tags (read more here).

  10. [Monitoring, CPI] Added a possibility to Restrict access by user role for CPI Message Monitor. Only FigafMessageMonitoringOperator is supported for now.

  11. [DevOps, B2B] Supported transport of agreements linked with Communication Partner.

  12. [DevOps] Enhanced Parameter values replacement configuration to support exact match for parameters.

  13. [PI→CPI Migration] Removed support of PI Integration Objects migration with B2B Scenario profile.

  14. [Common] Added a possibility to automatic license of objects. It is enabled on Application configuration page.

  15. [FIX, Testing Tool] Fixed an issue when recalculation of order numbers didn’t work.

  16. [FIX, Testing Tool, B2B] Fixed an issue when run steps filter config of B2B integration object was configured incorrectly during PI Test case migration.

  17. [FIX, PI→CPI Migration] Fixed migration of Operation Mappings with multi messages:

    • If not B2B migration, the IDOC root message name (e.g. ORDERS05) is used for the Splitter step. (No changes if Operation Mapping uses a Message Type).

    • For B2B migration, the Splitter Step isn’t added.

    • For all migration, /[local-name()='Messages']/[starts-with(local-name(), ‘Message')]/* XPath is used for the Remove Multistructure step.

Notes for upgrade from 2509 to 2510

  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 synchronize communication partners and link them with other TPM objects.

  2. It’s required to process forcible synchronization (option Forcibly process payload dependent initializations for not updated objects ) of PRO agents Change Tracking Tool → Tracked Objects page to reinitialize Operation Mappings metadata to fix migration of Operation Mappings with multi messages.

  3. [Only for BTP deployment] Download and use the latest Figaf-BTP-Deployment configuration to have new Monitoring role available on BTP.

    It’s enough to replace existing xs-security.json file by the new one (verify if you don’t have some custom changes there). After replacement execute the following command to update XSUAA configuration:

    cf update-service  figaf-xsuaa -c xs-security.json