Changelog

A new endpoint has been released in the Developer API to assist with regular audit reports and compliance. GET /api/activity_logs uses the same data as the Activity audit UI in-product, and supports pagination and filters. API clients get access to this endpoint per environment.

Within the Connector SDK, you can now utilize Copilot to build a custom connector with any application. New Copilot capabilities around searching for API documentation and an easy-going chat experience allow you to build connectors quickly and intuitively. You can still supply any relevant information (API docs, OpenAPI specifications) to provide context and direction to the model.

All workspaces with Copilot enabled have access to this new Copilot experience.

When exporting a manifest via Recipe Lifecycle Management, the error messaging is now more actionable to assist in fixing any missing assets. For help with troubleshooting, review our documentation.

Within Recipe Lifecycle Management, archived manifests will behave the same as deleted recipes in the Trash folder and will be permanently deleted after 30 days. With this change, we expect an improved loading time of the Export and Import manifest pages.

Within Recipe Lifecycle Management, the manifest file name format has been updated from `{folder name}_{user name}` to `{manifest name}_{folder name}`. This change was made to enable users to easily find and identify their manifests, and easily match downloaded manifests and the Export/Import UI.

Starting with OPA version 24.1, the Call BAPI action in the SAP RFC connector now includes a comprehensive catalog of BAPIs organized by Business Objects. This enhancement simplifies the process of finding and selecting the appropriate BAPI by allowing you to browse through relevant business objects.

• SAP: Improved Call BAPI action, allowing easier navigation in the catalog of available BAPI methods.
• SAP: Fixed loading of IDoc segments. Added support for segment nesting levels up to 128

See the OPA release notes for this and previous updates to OPA.

Within the Logging Service, you can now view trigger errors to assist in troubleshooting. As trigger errors do not generate a job, this visibility into the failed triggers is crucial for resolving errors and maintaining the functionality of your recipes.

When creating or updating an SAP RFC connection, you can now utilize SAP Router, SAP's standard product that acts as a reverse proxy. The SAP Router can be configured under Optional Settings on the connection setup page.

The member_invitations endpoint now supports setting roles for new collaborators in all available environments, not just Dev. We have maintained backward compatibility with the previous logic, so you can use either role_name or env_roles to set roles for collaborators.