Changelog
Keep up with the latest updates we’ve made in Workato.
Community Connectors: What’s new in May
We're excited to announce our latest updates in the Workato community for May 2024! This month, we've introduced 5 new connectors, including Google Gemini for AI driven content creation, Google Chat for enhanced team communication and Conga Composer for streamlined document generation. Additionally, we've upgraded 21 other connectors like Freshsales, SmartRecruiters, OneLogin and SOAP, implementing various enhancements and resolving numerous bugs. Curious about the updates? Take a peek at our full update here.
Community Connectors: What’s new in April
We've released 8 new connectors this month, including AWS Bedrock for AI innovation, Kintone for team collaboration, iChris for HR automation, and JobAdder for recruitment efficiency. Plus, we've polished up 13 other connectors like Acumatica, GraphQL and Freshsales with enhancements and bug fixes. Curious about the updates? Take a peek at our full update here.
Community Connectors: What’s new in March
We're excited to announce 23 new and updated connectors this month! Dive into apps featuring MYOB Business for streamlined accounting, Insided for enhanced team collaboration, and Akamai EAA for secure enterprise application access. Also, check out enhancements like mail-related triggers in Microsoft Graph API and Bearer Token authentication in JAMF. Read the full update here
Enhanced Call BAPI action for SAP RFC connector
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.
Addition of package id to the package deployed RecipeOps trigger
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.
On-prem Agent (OPA) 24.0 Release
- 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 thesapjco3.jarand 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 release3.0.0in 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.
Expansion of Developer APIs for connector management
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:
Addition of RecipeOps trigger for alerting when API client exceeds policy limit
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.
Wait for Response available for HTTP Connector
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.
SAP OData Connector now supports catalog service for easy recipe building
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.