Changelog

IDP now allows you to process receipts, invoices, or any other document into recipe datapills that can map any downstream actions. You can pre-configure schemas for documents, process handwritten text, and process multilingual documents.

• SAP S/4HANA Cloud, Private Edition
• SAP S/4HANA Cloud, Public Edition
• SAP S/4HANA On-Premise

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.

To make it easier to work with projects after deployment, the RecipeOps trigger now includes the package_id. With this package_id, you can confirm which recipes were deployed via API.

• SFTP: Added support for on-premise SFTP.
• SAP: Removed the metadata cache for IDoc types. All required data is now retrieved on-demand from the SAP server. This change saves agent memory and improves operational consistency.
• SAP: Added support for SAP JCo version 3.1.9 (2024-03-19), including the sapjco3.jar and corresponding native binary libraries. While Workato recommends using the latest version of SAP JCo with OPA, we still support older JCo versions with the major release 3.0.0 in partial compatibility mode.
• SAP: Added support for more precise identification of the Distribution Model for Inbound IDocs.
• Security: Updated libraries according to the OWASP scanner recommendations.
• Cloud logging: Fixed a bug that caused log spamming when debugging was enabled.

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

New endpoints have been added to expand the resources of the developer API, with connection management in mind. Read more about the new endpoints in our documentation:

• Update connection
• Connection parameters reference
• List platform connectors
• List connector metadata
• Disconnect connection
• Delete connection

The new Recipe Operations triggers for policy quota and rate limit violations are instrumental in giving administrators visibility and the ability to proactively monitor their client's API usage. With these new triggers, administrators can now receive active alerts about violations, and move quickly to address.

If you know an endpoint will take more than a few seconds to respond, you can now configure the HTTP action as a long action. The action will wait for a response for up to an hour, but does not guarantee ordering of job execution.

HTTP long action is a a beta release, available to everyone using Workato's HTTP connector.

Previously, working with the SAP OData connector required entering the internal technical name of the desired service and manually checking permissions to said service. Now, when the catalog service is enabled, creating an action or trigger will prompt a user-friendly dropdown menu, offering a selection of OData services and enhancing efficiency and reducing errors.

Wait for resume actions allow you to define actions that can suspend jobs until an event takes place in an external system, such as waiting for an invoice to be approved, or waiting for an email to be opened. With this new action, builders and partners alike can better model workflows and simplify their recipe build experience.