K2 SmartObject backed by Oracle

What it does

This action reads from, writes to, or queries a database-style data source. The migration depends on the original provider, table or query shape, credentials, gateway requirements, and how returned values are used later in the workflow.

How Flow Migrator maps it

Flow Migrator maps this to Oracle connector or custom connector review path using Oracle Database / HTTP. Requires representative K2/SmartObject metadata before automatic mapping can be trusted. Flow Migrator recognizes this pattern, but automatic export is still planned or limited.

Common migration issues

• Automatic export is not complete yet; use the page as planning guidance and handle this action manually or with a placeholder.
• Confirm connection references, gateway setup, server/database names, table names, primary keys, credentials, and returned result shape.
• Review HTTP method, URI, headers, authentication, retry behavior, premium licensing, and response parsing.

Validation checklist

1. Review this item before export or immediately after import.
2. Open the generated flow and confirm the action card imported correctly.
3. Validate connection references and required settings before running the flow.
4. Test with representative source data from the original workflow.
5. Confirm gateway connectivity, primary key handling, query filters, and returned data shape.