Release notes

2602

  1. [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.

  2. [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.

  3. [DevOps, B2B] Enhanced Auto-activate B2B agreements to activate not activated agreements and update edited agreements as well.

  4. [DevOps, B2B] Added new Suppress warnings for Auxiliary B2B objects - allow imports always option on Landscape configuration page.

  5. [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 warning Can be imported - this will overwrite the existing object with potential loss of data, the user can suppress this warning and perform forcible import.

  6. [DevOps, CPI] Implemented synchronization of previous system in addition to the dev and target systems during initial synchronization of import through landscape with Locked version workflow.

  7. [B2B] Supported deletion of agreements.

  8. [B2B] Supported deletion of trading partners and communication partners.

  9. [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

  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 correct Receiver Message Version for B2B Scenarios.

Patches

2602.1

  1. [Testing Tool, CPI] Supported change of Agent Object assigned to the test case for IFlow Chains.

    If IFlow Chains don’t match fully (the same Sender IFlow and Chained 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.2

  1. [FIX, Change Tracking] Fixed an issue when synchronization results were leaked in Hazelcast cache when object type synchronization failed.