MS Teams Workbot - New Message Trigger
Workbot remains a key way our customers can integrate humans into any workflow. The numbers show this: Workbot for Teams recipes are growing at 300% YoY.
Previously, we have only supported static commands for users to interact with Teams Workbot. This required you to build distinct triggers for each use case you wanted your bot to handle. Today, I'm excited to announce a new trigger that will introduce more use cases and flexibility to Workbot for Teams.
Now, you'll be able to listen to any message sent to Teams Workbot via a Direct Message or a mention in a channel, allowing your bot to interact with users in various ways.
What is it:
- A new trigger in the Teams Workbot connector - New Message. It operates in real-time with near-zero latency.
Why:
- Generative AI has changed how we expect to interact with bots in any medium, and our connector capabilities must keep up. Users expect that they can converse with a bot in natural language, and there can be an LLM that infers the intent and chooses what to do next. This trigger is critical for enabling these use cases.
- This trigger is the beginning of our complementary work to bring Workato Genies to life!
- Similar triggers have already been released for Slack Workbot as well
How it works:
- Simply select the New Message trigger, and no further configuration is needed.
- Optionally, use trigger conditions to filter messages from only DMs or specific channels that you want your bot to listen to.
- Use the Post message action to send a response back to the user after any recipe logic.
SAP Connector Update
- SAP RFC Connector: SAP schema refresh and Connection pooling
Keeping the schemas for RFC, BAPI, and IDoc up to date is essential for ensuring that your integration tool accurately reflects any changes made in the SAP backend. Failing to refresh the schema to account for updates like custom fields, modified data types, or field length adjustments can result in incorrect data handling, leading to processing errors. With this new enhancement, Workato now retrieves real-time data with the latest schema updates for RFC/BAPI/IDoc, eliminating the need for manual OPA restarts to reflect changes.
By clicking on the "Refresh" icon in recipe edit mode, you will now fetch the latest schema for RFC/BAPI/IDoc directly from SAP, as specified in the note in our documentation.
- SAP OData Connector: Long-running action | HTTP Offload Proxy
Currently, the SAP OData connector allows users to customise their requests effectively, but it faces limitations when dealing with requests that take longer than 120 seconds or require fetching bulk data in a single request even after applying pagination. These limitations can be challenging for users who need to work with large datasets or complex operations with SAP systems. With this change, we can eliminate such restrictions without any impact on our platform for all customers.
The HTTP Offload proxy service overcomes these challenges by handling the offloading of long-running or large requests. We have introduced a new "Extract bulk data" action to leverage this service with our SAP OData connector. This action offers extended support for longer response times, with the differences and limitations as documented here.
We intentionally introduced this as a separate action by segregating it to support the SAP ECC to S/4HANA migration scenarios.
The HTTP Offload proxy service overcomes these challenges by handling the offloading of long-running or large requests. We have introduced a new "Extract bulk data" action to leverage this service with our SAP OData connector. This action offers extended support for longer response times, with the differences and limitations as documented here.
We intentionally introduced this as a separate action by segregating it to support the SAP ECC to S/4HANA migration scenarios.
SDK Connector - Ruby Whitelist Removal
After we finished the SDK framework migration to SDK CLI Gem and then the migration into a completely secure container, the SDK team is excited to announce the long-awaited feature: removal for SDK Ruby whitelist!
SDK developers can now access the full functionality of Ruby 2.7, including built-in libraries and any available Ruby gems within the SDK container. Developers can use Ruby's require method to import built-in libraries, such as JSON, CSV, socket, etc. and many more possibilities, like using a selection of pre-installed Ruby gems without restrictions, leveraging TCP sockets for low-level TCP connections, defining classes and modules, and more!
Utilising the full power of Ruby OOTB without restrictions now opens up a whole new world of possibilities for all SDK developers!
We are launching this feature in private beta. Please let your CSM know if you want to test this feature.
SDK developers can now access the full functionality of Ruby 2.7, including built-in libraries and any available Ruby gems within the SDK container. Developers can use Ruby's require method to import built-in libraries, such as JSON, CSV, socket, etc. and many more possibilities, like using a selection of pre-installed Ruby gems without restrictions, leveraging TCP sockets for low-level TCP connections, defining classes and modules, and more!
Utilising the full power of Ruby OOTB without restrictions now opens up a whole new world of possibilities for all SDK developers!
We are launching this feature in private beta. Please let your CSM know if you want to test this feature.
