Older releases

2.15.8

2.15.8
  1. [Testing Tool, PRO] Added an option irt.testing.pro.disable-correlation-id-lookup (possible values: false - default, true) to skip lookup by correlation id in the message monitoring client.

2.15.7

2.15.7
  1. [FIX, DevOps] Fixed a bug when selection of transport configuration by group id and revision limit failed on MSSQL Server.

2.15.6

2.15.6
  1. [DevOps, CPI] Added a possibility to configure transport configuration for particular released version of CPI IFlow.

  2. [DevOps, CPI] Added a possibility to configure not approved/imported landscape items, transport configuration now becomes immutable only for the landscape item which has been approved.

  3. [FIX, DevOps, CPI] Fixed a bug when the latest state of CPI object was taken as a source during transport instead of specified version in transport. For example: let’s have a landscape dev → qa → prod and Iflow_x (v1) has been transported to qa. Then if user update object on qa manually, further transport to prod can use that updated version instead of the state Iflow_x (v1). Now Figaf Tool always take persisted specified version of the object. Also, we decided to block transport of the state X from system A to system B when the state X doesn’t exist anymore on system A. Use additional virtual landscape items to persist intermediate state if you want to update the state of object on system A quite often, for example A → A' → B.

  4. [FIX, CPI] Fixed a bug when object name of CPI object was shown as hash on License page and it wasn’t possible to modify (request additional license options) that object license item. It affected CPI objects which have different displayed and technical names. Process synchronization with the license server from License tab to migrate affected entries.

Notes for upgrade to 2.15.6

Notes for upgrade to 2.15.6
  1. Previous configuration in Figaf Tool hasn’t been affected.

  2. It’s required to process synchronization of license to migrate affected entries (see bug description in release notes).

2.15.5

2.15.5
  1. [Testing Tool] Added a possibility to configure test parameters per test case on Shared configuration page.

  2. [Testing Tool, CPI] Added two options Run steps selection strategy and Run steps filter to select steps which should be recorded/tested.

  3. [Testing Tool, CPI] Added an option Use only finishing run steps to fetch the first and last message in a test case.

  4. [Common] Added new user role IRTLicenseRequester to request new licenses for the objects.

  5. [FIX] Fixed a bug when users with roles IRTDevOpsOperator and IRTDevOpsConfigurator couldn’t update their own passwords.

Notes for upgrade to 2.15.5

Notes for upgrade to 2.15.5
  1. Previous configuration in Figaf Tool hasn’t been affected.

  2. It’s required to process forcible synchronization (option Synchronize objects forcibly) for CPI agents from Change Tracking Tool → Tracked Objects page.

2.15.4

2.15.4
  1. [FIX, DevOps, CPI, API Mgmt] Fixed a bug with landscape items validation when virtual items were defined manually.

2.15.3

2.15.3
  1. [Change Management, API Hub] Added API_HUB agent platform. This agent synchronizes and tracks changes in APIs added to the favourites list of connected account. See configuration here.

  2. [Support Tool, CPI] Added Cancelled status support to CPI Message Monitor.

  3. [Testing Tool, CPI] Added support for all HTTP methods in HTTPS Adapter during testing.

  4. [DevOps, CPI, API Mgmt] Added a possibility to define virtual landscape items manually.

  5. [Testing Tool, CPI] Added recording of non-successful messages.

  6. [Testing Tool, CPI] Added a possibility to record MPL attachments.

  7. [FIX] Fixed a bug where Figaf Tool didn’t use proxy settings for CPI and API Mgmt.

2.15.2

2.15.2
  1. [Common] Added automatic determination of timezone for PRO agents.

  2. [CPI, Git integration] Added support of value mapping upload, download, and deploy to cpi-plugin.

  3. [CTT, CPI] Added a flag Synchronize objects forcibly to CPI synchronization request.

  4. [Testing Tool, PRO] Added a possibility to define list of channels where modules should be added.

  5. [Testing Tool] Added possibility to view polling statistics when there is polling in progress.

  6. [Change Management, Git integration, CPI, API Mgmt] Added option Update .gitignore automatically.

  7. [FIX, CTT] Fixed a bug where options Synchronize objects forcibly and Rebuild links for the latest versions forcibly didn’t delete incorrect links (only added missed ones).

  8. [FIX, DevOps, 'CPI`] Fixed a bug where transport configuration wasn’t cached after transport approval.

  9. [FIX, Change Management, Git integration, CPI, API Mgmt] Fixed a bug where build.gradle and settings.gradle were not committed with the enabled corresponding checkboxes.

Notes for upgrade to 2.15.2

Notes for upgrade to 2.15.2
  1. Previous configuration in Figaf Tool hasn’t been affected.

  2. It’s required to process reinitialization operation on Agents page for CPI agents with configured Git integration. Then, if automatic update of build.gradle, settings.gradle is not configured, copy the content of updated templates build-irt.gradle and settings-irt.gradle to these files manually.

    Figaf Tool 2.15.2 uses cpi-plugin 2.0.RELEASE with support of value mapping upload, download, and deploy. IFlow tasks were renamed to uploadArtifact, downloadArtifact, deployArtifact. The same tasks are used for Value Mappings. Folders VM_<valueMappingName>, created by Figaf Tool previously, aren’t used anymore and should be deleted.

2.15.1

2.15.1
  1. [FIX, CPI, Git integration] Fixed a bug where dependencies from the common module were not visible from IFlow module.

  2. [Common] Increased the range of exceptions where manual license request is available.

2.15

2.15
  1. [Change Management,DevOps, Testing Tool, CPI, Api Management] Added support of Cloud Foundry environment.

  2. [Testing Tool, CPI] Added automated polling of CPI IFlow after message sending.

  3. [Testing Tool] Added support and comparison of TRADACOMS messages.

  4. [DevOps] Added new public API to fetch information about the ticket and process transport.

  5. [Change Management, UI] Added visual viewer of Iflow BPMN model differences.

Notes for upgrade from 2.14 to 2.15

Notes for upgrade from 2.14 to 2.15
  1. Previous configuration in Figaf Tool hasn’t been affected.

  2. It’s required to process reinitialization operation on Agents page for CPI and API Management agents with configured Git integration. Then, if automatic update of build.gradle, settings.gradle is not configured, copy the content of updated templates build-irt.gradle and settings-irt.gradle to these files manually. Also, copy new parameters from gradle-irt.properties to your gradle.properties.

2.14.1

2.14.1
  1. [Testing Tool, CPI] Added a possibility to keep integration flow in trace mode.

  2. [DevOps, PRO] Added support of import transports with objects which don’t exist in Figaf Tool.

  3. [Change Management] Added a possibility to view object payload without download.

  4. [Testing Tool] Added an option to avoid recalculation of order number for 1→1 relation.

  5. [Testing Tool] Added an option to configure identification of collection items for XML messages.

  6. [DevOps, PRO] Extended CTS+ transports support:

    • CTS+ transport with all its children is saved into one group.

    • CTS+ transport with all its children can be sent to approval, approved, and declined in batch mode.

  7. [Support Tool] Added skipping of alerts if it’s not possible to determine active rule.

  8. [FIX, Testing Tool] Fixed test case extraction for test runs with aggregation.

  9. [FIX, Testing Tool] Fixed a bug when rerun test cases ran test case only on one test system.

  10. [FIX, Change Management, CPI] Fixed parsing of IFlow BPMN model with the wrong position of documentation element.

2.14

2.14
  1. [DevOps,Change Management, PRO] Extended support of File and CTS+ transports in the Figaf Tool DevOps functionality:

    • Added change tracking for File and CTS+ transports.

    • Integrated usage of PRO transport objects in the ticket

  2. [Change Management, CPI] Added possibility to use iflow as a configurable template to create many iflows. See new functionality for distribution configuration to learn more.

  3. [Change Management, CPI] Added possibility to restore last iflow version of deleted iflow.

  4. [Testing Tool] Added possibility to externalize comparison configuration and share it between different scenarios using message+partner+integration object identification. See overview of shared configuration page to learn more.

  5. [Testing Tool] Optimization of test run/test suite run report generation:

    • New optional report generation strategy replaces Excel report by bundled CSV report which contain 3 files: processed messages report, diff report and test runs metadata report. Enable an option Use bundled CSV report generation strategy on the Application config page. That option will have effect only for new test suite runs or separate test runs.

    • Test run report generation won’t be triggered if at least one of the testing result is scheduled or currently in progress with comparison.

    • Test suite run report generation won’t be triggered if at least one related test run currently is not completed in the active polling or if at least one related test run scheduled or currently in progress with the report generation.

  6. [Testing Tool] Added an option for test runs/test suite runs for re-comparison of testing results in the context of the same test run. It’s possible to skip comparison of all SUCCESS entries or all compared entries.

  7. [Testing Tool] Added a possibility to extract message groups related to chosen results/test runs as new test case(s) from the test run/test suite run pages. Optionally it’s possible to link new test case(s) with the new/existent test suite. It provides a possibility to isolate problematic messages and test them separately without processing of the whole original test case/test suite all time.

  8. [Testing Tool] Added statistics of scheduled/active messages sending/comparisons/report generations for test runs.

  9. [Testing Tool] Added CSV export of Testing tool data with the applied filter for Test Cases, Test Runs, Test Run Results, Test Suites, Test Suite runs.

  10. [Testing Tool] Added support of ignoring options for XML comparison.

  11. [Testing Tool] Added pagination for Test Cases and Test Runs on UI.

  12. [Testing Tool] Updated rerun function in the test suite run. Now it’s possible to select and rerun many test runs at once.

  13. [Testing Tool] Added possibility to resend NOT_SENT messages from test run/test suite run pages.

  14. [FIX, DevOps, Git Integration] Deleted package/object now are also deleted from settings-irt.gradle or settings.gradle.

Notes for upgrade from 2.13 to 2.14

Notes for upgrade from 2.13 to 2.14
  1. Previous configuration hasn’t been affected.

  2. To use restoring of last iflow versions already registered in CTT before upgrade, enable forcible synchronization for related CPI Agent using a function Reset synchronization query on Agent dialog and then process full synchronization (or select required packages). It will download and save iflow bundles in Figaf Tool (that data wasn’t persisted in CTT before 2.14).

  3. Build has data migrations for big Figaf Tool tables. Depending on amount of test run results and test runs in the system, the first bootstrap will take some time. For example, we had a case with 15 min bootstrap time on the instance with 1.5 million testing results.

  4. Critical changes were made in the DevOps and Testing Tool related tables in the database schema. Data migrations are configured to be automatically executed during the first bootstrap.

2.13.8

2.13.8
  1. [Change Management, Git integration, CPI] Added 2 options on Agent to update build.gradle and/or settings.gradle automatically during synchronization.

  2. [FIX, Testing Tool, PRO] Fixed cancellation of EOIO messages. Also added support for cases when sender channel has quality of service EO but outbound message is EOIO.

  3. [FIX, Testing Tool, Change Management,DevOps, Monitoring] Refactored usage of detached transactions in the whole app. They could cause a deadlock in concurrently processed operations when Figaf Tool uses SQL server database.

2.13.7

2.13.7
  1. [FIX, Testing Tool, CPI] Fixed testing (both standard and with mock data) of integration flow with the local subprocess.

2.13.6

2.13.6
  1. [Testing Tool, CPI] Added initial support of iflows with the multiple sender endpoints.

  2. [Testing Tool] Check Testing Results option on Test Run and Test Suite Run now triggers comparison of received results. That also leads to regeneration of test run/test suite run report.

  3. [Testing Tool] Added an option for calculation of alphanumeric order number (by default it extracts digits from the source string).

  4. [Testing Tool] Added an option for recalculation of the order number during manual test case upload.

  5. [DevOps] Test Cases lookup from the Ticket now also works for non-integration object entries attached to the ticket.

  6. [FIX, Monitoring] Fixed a bug when one alert could be handled multiple times due to overlapped scheduled polling.

  7. [FIX, Testing Tool, CPI] Fixed CPI test object determination in the Run On operation (affected in 2.13.5).

  8. [FIX, Testing Tool, Monitoring, CPI] Fixed a bug when it wasn’t possible to register CPI IFlow integration object with the version label greater than 10 characters (also affected alerts handling for such iflows).

2.13.5

2.13.5
  1. [Testing Tool] Consolidated report generation from selected Test Suite Runs. The function is available on the Test Suite Runs page.

  2. [Testing Tool] Test cases migration from PI scenario to CPI iflow. See more details here.

  3. [Testing Tool, UI] Separate page for Test Suite Run. Navigation is available from Test Suite Runs page, Test Suite page (Results History tab), Test Run Details page

  4. [Testing Tool, PRO] Added an option on Test Run Result item to browse related messages from PI Message Monitoring. Available on Test Run Details page.

  5. [Testing Tool, PRO] Added an internal job for checking JMS connection (if JMS integration is enabled and Agent is not virtual) and refreshing JMS context when connection is broken. That job is executed each 5 min by default.

  6. [FIX, Testing Tool, PRO] Fixed a bug when messages received through JMS due to PI redelivery were not filtered.

  7. [FIX, Testing Tool] Fixed X12 message determination for some combinations of segment and element separators.

  8. [FIX, Testing Tool] Fixed EDIFACT/X12 segment comparison for cases when one document has empty segment like PCI' and another document has segment with empty data element like PCI+'.

2.13.4

2.13.4
  1. [Common, UI] Added possibility to configure mapping between SAP username to Figaf Tool username on User Details dialog to show Figaf Tool username in the Created By, Changed By and Deployed By columns of CTT and Integration object tables.

  2. [FIX, CPI, UI] Fixed IFlow deployment status on Integration objects page.

2.13.3

2.13.3
  1. [Change Management, CPI] Added an option to synchronize only objects from selected packages.

  2. [FIX, Operations, Monitoring, CPI] Fixed the max length of condition parameter.

  3. [FIX, Operations, Monitoring] Fixed usage of emailTo parameter from application settings instead of email integration entry during alert notification.

2.13.2

2.13.2

If you have CPI landscapes created in 2.13 and older versions, since 2.13.2 it’s possible to use them again. Just open landscape and reconfigure approval and deployment settings. Notice that unfinished transports must be deleted or cancelled.

  1. [DevOps] Added possibility to update approval and deployment settings in the existent landscape.

  2. [DevOps] Added and configured new user roles for DevOps operations.

  3. [UI] Landscapes configuration is moved to Configuration section.

  4. [Change Management, Git integration, CPI] Added configuration of additional Gradle modules layer for packages. As a result, now it’s possible to perform CPI/IRT plugin tasks at the package level.

Remove the file settings-irt.gradle in the branch, configured in Figaf Tool, or remove all iflow module definitions from it. It must be done because new modules have different naming. Folder structure is not changed.

  1. [FIX,DevOps, Change Management, CPI] Fixed a bug when unprocessed tracked objects were marked as deleted unexpectedly after transport.

  2. [FIX,DevOps, CPI] Fixed deployment of value mapping after transport.

  3. [FIX,Testing Tool, PRO] Fixed recording request creation for dualstack systems (affected in 2.13.1).

2.13.1

2.13.1
  1. [DevOps, CPI] Changed the behavior of transport flow for CPI objects. Previously, during each import it always took the state of an object from the first system in the landscape. Now it takes the state of the previously transported object. So, having the landscape DEV → QA → PROD, import from QA to PROD will take an object state from QA instead of the DEV. Transport configuration will be applied as usual.

  2. [DevOps, CPI] Review is configurable now for each landscape item separately instead of the global config.

  3. [DevOps, CPI] Only transport reviewers are able to process import on the target system. It has an effect only when the review is configured.

  4. [DevOps, CPI] Added an option on landscape item to deploy artifacts after transport. By default deployment is disabled.

  5. [FIX, DevOps, CPI] Fixed a bug when it wasn’t possible to process import if transport contains object versions which already exist on target system. Now transport of these objects is skipped, after that transport items are linked with already existent versions in CTT.

2.13

2.13
  1. [Common, UI] Now it’s easier to get started with tool. Both login with the default user, guides to get started with adding license and agents. Updated tours to see the tool in action.

  2. [Testing Tool] Improved EDIFACT comparison and ignoring of specific segments/fields.

  3. [Testing Tool, PRO] Added a possibility to test aggregation scenarios. For now only integration through SAP Log Module is available. Test cases must be loaded manually.

  4. [Testing Tool] Added an option on Agent to control a max amount of test messages to be sent to Agent system per defined interval (configured as cron expression).

  5. [Testing Tool, PRO] Added an option to test on decentral adapter engine.

  6. [Testing Tool, PRO] Added a possibility to test BE scenarios with mock data on PRO systems.

  7. [Testing Tool, PRO] Support of sender agreements with EDI separator and fix of testing with sender modules in case of EDI separator flow.

  8. [Change Management, CPI] Added change tracking for packages, value mappings and documents.

  9. [DevOps, CPI] Added transport of packages and value mappings.

  10. [Monitoring, CPI] Added monitoring of persisted messages in the Message Monitor

  11. [Change Management, Git integration, CPI, API Mgmt] Added an option on Agent to prevent commits of iflow/api proxy changes during synchronization in Figaf Tool to avoid duplication of changes committed by user and Figaf Tool.

Notes for upgrade from 2.12 to 2.13

Notes for upgrade from 2.12 to 2.13
  1. Previous configuration hasn’t been affected.

  2. Critical changes were made in the CPI related tables in the database schema. Old table for integration packages are no longer used and will be deleted automatically once data migration is finished.

2.12.2

2.12.2
  1. [Testing Tool, CPI] Implemented recording and testing of integration flows on CPI system with confidential data.

  2. [Common] Default timezone is switched to GMT in the license validation.

  3. [FIX, Testing Tool, PRO] Fixed a bug with encoding of special characters in recorded payloads when SAP Log Module integration is used.

  4. [FIX, Testing Tool, PRO] Fixed a bug when it wasn’t possible to parse XI message during recording using SAP Log Module integration if that XI message didn’t have a default payload attachment name equal to MainDocument.

2.12.1

2.12.1
  1. [FIX, Testing Tool, PRO] Fixed a bug when it wasn’t possible to find messages on dualstack system for plain scenarios with only one message entry.

2.12

2.12
  1. [Testing Tool,PRO] Implemented recording of Receiver Determination objects (dualstack). See that section to learn more.

  2. [Testing Tool, PRO] Implemented recording and testing of asynchronous scenarios (plain EO/EOIO) on PRO system with confidential data. See that section to learn more.

  3. [DevOps,PRO] Implemented transport of Sender/Receiver agreement.

  4. [Change Management, Agent Synchronization, PRO] Added change tracking of receiver determination and interface determination objects (dualstack).

  5. [Change Management, Agent Synchronization, PRO] Improved synchronization algorithm to handle large data set from SimpleQuery.

  6. [Change Management, Agent Synchronization, PRO] Synchronization of external messages and operations is processed during the synchronization of external definitions and service interfaces. It speeds up the process, because external messages and operations are inner objects.

  7. [Common] Added configuration to support Java 11 runtime. See that section to learn more.

  8. [UI] UI5 libraries now are embedded within the Web application (as dependencies), now there is no requirement for having access to cloud distribution of OpenUI5.

Notes for upgrade from 2.11 to 2.12

Notes for upgrade from 2.11 to 2.12
  1. Previous configuration hasn’t been affected.

  2. No critical changes were made in the database schema.

2.11.6

2.11.6
2.11.6 has a data migration for external message/operation CTT objects, it can take some time depending on count of PRO agents and total count of external message/operation objects which were previously synchronized . [CTT, PRO] Optimization for synchronization and data storage: payloads of external messages and operation objects now are not loaded from PI system during synchronization, because they are identical to payloads of related external definition/service interface objects. . [CTT, CPI] Added runtime generation of simplified IFlow model, also added possibility to compare simplified models instead of standard BPMN models. It gives better way to see, what has been changed in the IFlow structure. . [FIX, Testing] Fixed a bug when test suites were not run by scheduler if at least one object in any test suite is not licensed for testing. . Many minor fixes and improvements

2.11.5

2.11.5
  1. [CTT] Added a new option on PRO Agent for synchronizing SAP ESR objects on demand. Use it if SimpleQuery can’t load metadata for all objects of any ESR type (in most cases Data Type) or if you don’t want to synchronize such objects at all.

  2. [DevOps] Information about last ticket run is added on the ticket page (see Last Testing Result tab)

  3. Some minor fixes and improvements

2.11.4

2.11.4
  1. [Common] Added alternative way for requesting object licenses when Java doesn’t have access to network. It’s enough to have access to https://app.figaf.com/irt-lic/#/ in the browser. You just need to copy provided request in Figaf Tool and use it on license server UI.

  2. Some minor fixes and improvements on UI.

2.11.3

2.11.3
  1. [Common] Improved UI for requesting object licenses.

  2. [FIX, DevOps] Fixed a bug when some ESR objects on target system were not linked with the ticket after transport (transport finished successfully).

  3. [FIX, Security] Email check during authorization now is case insensitive.

2.11.2

2.11.2
  1. [FIX, UI] Fixed a bug when landscapes were not loaded on the Create ticket dialog on the tickets page.

2.11.1

2.11.1
  1. [Common] Added possibility to request missing object licenses from license error dialog.

  2. [FIX, DevOps] Fixed a bug when transports created for several tickets at the same time were not linked with each other

  3. [FIX,DevOps, PRO] Fixed a bug when all business component’s channels were attached to the ticket during dependent objects attachment. As a result, ticket has too many attached channels instead of used by chosen scenario. Now it doesn’t take channels for components/systems or components/systems for parties during dependent object lookup.

  4. Some minor fixes and improvements on UI.

2.11

2.11
  1. [DevOps] New development and transport workflow. See that section to learn more.

  2. [DevOps] New migration workflow which simplifies e2e migration between 2 landscapes. Write to [email protected] to get a demo or support with configuration.

  3. [Common] Licensing model has been changed to fit requirements of the new functionality. If you already have an Figaf Tool with old license, see notes for upgrade to 2.11 below.

Notes for upgrade from 2.10 to 2.11

Notes for upgrade from 2.10 to 2.11
  1. Transport configuration has completely new model in 2.11 and it’s not possible to migrate old data, so, existing entries will be deleted.

  2. Critical changes were made in the tables related to DevOps functionality, the Testing Tool and Monitoring hasn’t been affected, small changes were made in CTT tables.

  3. Old installed license will no longer be used by the app, contact [email protected] to migrate your existent license to the new format.

2.10.6

2.10.6
  1. [Testing Tool, UI] New generic Test Suite Runs page under Testing Tool section.

  2. [FIX] Fixed alerts cleaner task.

  3. [FIX,PRO] Fixed a bug where communication channel update failed due to wrongly decoded characters.

2.10.5

2.10.5
  1. [FIX, CPI] Fixed propagation of original vendor and description during transport of integration flow.

  2. [FIX, CPI] Fixed determination of start event during test object creation. If integration flow had a local subprocess or exception subprocess, test object wasn’t not created properly. Current limitation - integration flows with several sender endpoints won’t be tested correctly, support of current case is scheduled for future releases.

  3. [FIX, CPI] Fixed a bug related to generated common testing classes for groovy scripts unit testing, where common tests failed when script doesn’t use messageLogFactory (added lenient = true to the mock).

2.10.4

2.10.4
  1. [FIX, PRO] Fixed a behavior of option Don’t send message after testing for BE scenarios. Now Agent Component throws an exception after 2nd stage (After Mapping) and Testing Result for 4th stage (After Result Mapping) is not registered in the test run at all, so, it won’t be compared.

2.10.3

2.10.3
  1. [FIX] Fixed missing default value for run_with_mock_data field for existent Test Suites (reproduced on MS SQL Server). Affected in 2.9.

2.10.2

2.10.2
  1. [DevOps, Testing Tool, CPI] Added messageLogFactory and messageLog mock objects to common module for unit testing of groovy scripts.

  2. [Testing Tool, PRO] Added support for Sender and Receiver agreements (Java stack) in the manual test case creation.

  3. [Testing Tool, UI] New generic Test Cases page under Testing Tool section.

  4. [FIX,Testing Tool, PRO] Fixed selectors for manual test case creation through archive upload. Now it’s possible to assign all needed interfaces and components.

  5. [FIX,Change Management, Agent Synchronization, PRO] Fixed wrong link to business component when channel has a * in the name.

  6. [FIX,Change Management, Agent Synchronization, PRO] Fixed missing link to business systems for communication channels.

2.10.1

2.10.1
  1. [DevOps, Testing Tool, CPI] Added a function for generating test data and unit tests for groovy scripts, defined in the integration flow. You can learn more here.

  2. [Operations, Monitoring] Added a Test function for rule external integrations (email and https).

  3. [Operations, Monitoring, UI] Improved Rules and Alerts UI.

  4. [Testing Tool, PRO] Added possibility to create test case manually using only UI form (it’s an alternative approach).

  5. [Testing Tool, CPI] Added possibility to run test cases and test suites on virtual landscape systems.

  6. [FIX] Fixed a bug when only default support rule was linked with new alerts (affected in 2.10).

  7. [FIX, Testing Tool] Fixed a bug where Test Suite excel reports were not sent to specified email correctly.

2.10

2.10
  1. [Change Management] Git integration for CPI and Api Management Agents. See that section to learn more.

  2. [Operations, Monitoring] Possibility to send alert attachments through email or webhooks integration.

  3. [Testing Tool] Possibility to mark Agent system as a Production system. It prevents testing on chosen Agent system.

Notes for upgrade from 2.9 to 2.10

Notes for upgrade from 2.9 to 2.10
  1. Previous configuration hasn’t been affected.

  2. No critical changes were made in the database schema.

2.9.1

2.9.1
  1. [FIX, Operations, Transport] Fixed a bug when post synchronization failed if only ESR objects are transported.

  2. [FIX, Testing] Fixed a bug when test suites couldn’t be run by a scheduled job.

2.9

2.9
  1. [Change Management] Added implementation of CPI shared resources (scripts, mappings, schemas, archives). There are many places where it makes sense to have scripts that are being used in multiple iflows. But if you want to make a change to the script you will end up with separate versions. It can be a pain to maintain it and also test it. We have added an option to take a script and turn it into a shared resource. You can then add this shared script to your iflows. If you make a modification to it the new version can easily be applied to all iflows where it is used. It will also allow you to test the change in all your iflows. You can learn more about new feature here.

  2. [Testing] Added possibility to test CPI iflows with mock data. Over the last year, we have improved the way we make it possible to test your CPI iflows. Now we have added a new option to test with a mock service hosted by the Figaf Tool application. Figaf Tool will then make a copy of the iflow you want to test. All Request Reply connections will be replaced with a call to the Figaf Tool mock data service that will respond with what needed changes in headers and payload. It means that it will be a lot easier to run a test for scripts or configurations that have been changed. If you own to use Figaf Tool hosted on your own environment you will need to specify cloud connector information to access Figaf Tool. Learn more here.

  3. [Operations, Transport] Added a warning if a secure resource like password or certificate is are not available on the target instance. In Figaf Tool you can configure which password/certificate properties you want across the landscape. So when you transport across the landscape you will see if the values are there.

  4. [Operations, Transport, Testing] Added improvement to the virtual SAP CPI landscape, so you can run Dev and QA on the same system. That way you can save a CPI system. Figaf now supports the Process Direct adapter in virtual environment, so you also will be able to test that functionality.

  5. [UI] Testing Templates have been renamed to Testing Suites, because it is a more standard name for grouping a set of test cases.

Notes for upgrade to 2.9

Notes for upgrade to 2.9
  1. Previous configuration hasn’t been affected.

  2. No critical changes were made in the database schema.

2.8.2

2.8.2
  1. [FIX, Testing] Fixed a bug when test case report generation was processing infinitely if any test run result doesn’t have a link to inbound message. Current state in general is unexpected.

2.8.1

2.8.1
  1. [FIX, Common] Fixed a bug when it wasn’t possible to delete CPI Agent if at least one metric has been registered by SAP System Monitoring.

  2. [FIX, Transport] Fixed a bug when it wasn’t possible to define P4 host for PRO Agent if Agent Component integration type is not used.

2.8

2.8
  1. [Operations, Transport] Added support for PRO transports (file and CTS), added possibility to configure channels during transport. You can learn more about new feature here.

  2. [Change Management] Added documentation of Figaf Tool tickets. This is an excel report which contains common ticket metadata, attached object versions, related integration objects, result of the latest ticket run and information about processed transports.

  3. [Change Management] Added documentation of CPI Integration Flows.

  4. [Operations, Monitoring] Added alerting for CPI Tenants status monitoring events.

  5. [Operations, Monitoring] Added possibility to mute identical alerts for defined period of time.

  6. [Operations, Monitoring] Added a scheduled task for alerts deletion. User can configure it on Application Configuration page. By default, alerts are stored for 90 days.

  7. [UI] Home page has been changed. Now in addition to the menu tiles it contains a list of configured landscapes with most used links per each Agent system in the landscape. You can find more information here.

Notes for upgrade from 2.7 to 2.8

Notes for upgrade from 2.7 to 2.8
  1. Timezone parameter has been added to PRO agents. New transport functionality requires this parameter for correct object version identification. SimpleQuery API doesn’t have information about timezone in the response, all dates are sent in local datetime format. It’s strongly recommended to configure that new parameter properly even if transport functionality in the Figaf Tool won’t be used for a while or when your Agent system is hosted in the same timezone as Figaf Tool. The new parameter has default settings: GMT timezone. Configuration of timezone parameter should also be done in GMT format: GMT+2, GMT-5, etc. Agent timezone can be found on NetWeaver Administrator page (/nwa).

  2. Critical changes were made in the previously released features:

    • Metrics (affected database schema and model in CPI Tenants status monitoring, irt-2.7).

    • Transport configuration (affected database schema and model in CPI IFlow transports, irt-2.6).

2.7.2

2.7.2
  1. [FIX, Testing] Fixed null pointer exception during checking of MigrationHelper scenario (PRO, affected in 2.7.1)

  2. [FIX, Change Management] Fixed missing updates during PRO synchronization due to wrong time zones used in SimpleQuery. Correct Agent system timezone must be configured manually on Agent dialog. Default value is GMT.

2.7.1

2.7.1
  1. [FIX, Testing] Link to folder now is not lost after channel update

2.7

2.7
  1. [Change Management,Operations, Transport, Monitoring] Added support of API Management agents, added change management, monitoring and transport for API Proxies with their related resources (policies, endpoints, etc.). You can learn more about API Proxy change management and transport here, about monitoring of API Proxies - here.

  2. [Operations, Monitoring] CPI Tenants status monitoring. It includes several metrics such as CPU/Memory usage, iflow latency, processed messages. You can learn more about that new feature here.

  3. [Operations, Monitoring] Runtime Message Monitor for CPI Agents, in addition to the possibility to define flexible filters, it allows you to configure role-based access to these filters and decide which Figaf Tool user can access to exact filter and what kind of access: browsing messages metadata only or with attachments as well. You can learn more about it here.

  4. [Operations, Monitoring] New alerting engine in Figaf Tool. We improved its performance and throughput, made alert metadata structured, improved determination of Tracked Objects and Integration Objects (depending on alert type and system type). Since an alert is a temporary entity and doesn’t require long storage, we decided to clear them all during automated database migration because it’s not possible to correctly migrate old alerts (and actually, it doesn’t make sense). In the future releases we are going to improve post processing actions for alerts and provide a flexible strategies for notification and reprocessing (when it’s actual).

  5. [Change Management] Test Cases coverage for PRO Agents. We improved operation mapping usage report and added additional information about actual test cases coverage and usage statistics for communication channels. You can learn more about new feature here.

  6. [Testing] Integration with new Process Integration Testing tool, provided by SAP in SP14. For now it’s possible to create PIT test case from testing template run in Figaf Tool. You can learn more about it here.

  7. [Testing] Added native support for regression testing of IFlows with Process Direct sender for CPI Agents. It uses special infrastructure IFlow with HTTPS sender and Process Direct receiver instead of copying full source IFlow and replacing its sender side by HTTPS sender (old approach). For now that infrastructure IFlow should be configured manually.

2.6.2, 2.6.3, 2.6.4

2.6.2, 2.6.3, 2.6.4
  1. [Migration from Figaf Tool 1.4.*/1.5.*] Improved migration functionality, fixed some bugs

2.6.1

2.6.1
  1. [FIX, Security] Custom roles check during authorization

2.6

2.6
  1. [Security] Custom API-key authentication approach has been replaced by OAuth 2.0.

  2. [Operations, Transport] Transport functionality for Integration Flows on CPI Agents. Possibility to define custom IFlow configuration which is applied during transport.

  3. [Operations, Monitoring] Reprocessing of CPI alerts. You need to add our script to the IFlow at the specific places, that script saves needed header properties and the payload of the message. Then it is possible to reprocess an alert and resend failed message again to the origin endpoint.

  4. [Operations, Monitoring] Improved performance of alerts handling.

  5. [Operations, Monitoring] Possibility to trigger alerts lookup for chosen consumer manually.

  6. [Change Management] Possibility to build and download documentation of Integrated Configurations (PRO systems).

  7. [FIX, Change Management] Restoring of previously deleted tracked objects. When some object is deleted on SAP system, it’s marked as deleted in Figaf Tool. Then if you create a new object with the same name again, it will be added as a new version in Figaf Tool after synchronization with a link to the previous version, so, the history of your changes won’t be lost.