Hi, thanks for the clarification Vinay K.. One follow-up question: If I perform an Insert, Update, or Upsert operation using the PostgreSQL connector in Workato, and the operation is successfully committed, is there any way to rollback those changes later from Workato itself? For example, in webMethods, when using Local Transaction, multiple database operations can be rolled back if a failure occurs before the transaction is committed. In Workato, if I use standard PostgreSQL connector actions (Insert/Update/Upsert), are those operations automatically committed? If yes, is the only recovery option to: Handle transactions at the database level using BEGIN, COMMIT, and ROLLBACK Use stored procedures Implement compensating actions (for example, a DELETE after a failed INSERT) Has anyone implemented similar rollback requirements with the PostgreSQL connector and, if so, what approach worked best?
Hi Team, I'm currently working on a migration/POC involving PostgreSQL iPaaS connector in Workato and evaluating transaction handling compared to webMethods JDBC Adapter. In webMethods, we have transaction options such as: No Transaction Local Transaction XA Transaction We're using the PostgreSQL connector in Workato to perform database operations (Insert, Update, Upsert, Custom SQL), and I'm trying to understand if there is any equivalent support for: Local transaction management Commit/Rollback control Transaction monitoring Distributed/XA-style transactions Specifically, has anyone implemented a scenario where multiple database operations need to be rolled back on failure, similar to webMethods Local Transaction behavior? If you've worked on a similar use case, could you please share: The approach used Whether transaction control was handled in Workato or at the database layer (stored procedures/custom SQL) Any limitations encountered with PostgreSQL connectors Thanks in advance!
