Skip to main content
Feedback

Database V2 changelog

Changelog

2205-11 (Version 47, Current)

  • Enhanced the Database V2 connector to handle long profile names by truncating names exceeding the 255-character limit and appending an ellipsis (…) as a suffix.
  • Enhanced the Database V2 connector to return the Ref Cursor Response instead of an object reference when the table in the Oracle database has column(s) with CLOB datatype.

2025-09 (Version 44)

  • Database V2 connector now successfully supports the use of both the Link Element and the IN_CLAUSE checkbox together. Grouping is performed when the SQL includes an ORDER BY clause with a column that matches the Link Element; otherwise, the process runs with standard batching. (CONC-13016)

  • Standard Get operations now support document grouping via the Link Element which requires one of the column in the ORDER BY would be same as the Link Element field. If the ORDER BY clause is absent then operations will automatically default to standard batch processing (without grouping) to ensure continued backward compatibility. (CONC-12996)

2025-09 (Version 43, - Reverted back to Version 38)

Attention

Subsequent to the September Runtime release, a fix was applied to roll back a feature that caused executions to fail when SQL queries included an IN clause with a linked element. If you applied version 43, you will be reverted back to version 38, then upgraded to version 44 Saturday, Sep 13th.

  • Added support for the CLOB datatype in the Database V2 connector GET, INSERT, UPDATE, DELETE, UPSERT, and STORED PROCEDURE operations for Oracle database.

  • Added support for returning REFCURSOR from stored procedures in the Database V2 connector for Oracle Database and PostgreSQL, enabling the process of complex queries that return multiple rows of data via cursors.

  • The Database V2 connector is updated to support the LINK element in Standard Get and Dynamic Get operations.

  • Enhanced the performance of GET and DELETE operations across Oracle, MySQL, PostgreSQL, and MSSQL. (CONC-10602)

  • The Database V2 connector's STOREDPROCEDURE operation now processes decimal values with precision and scale for insert, update, and delete statements.

  • The Database V2 connector's Upsert feature has been enhanced to support JSON data that includes special escape characters like double quotes. This ensures accurate column insert/update across Oracle, MySQL, PostgreSQL, and MSSQL without truncating characters like double quotes.

2025-07 (Version 41)

  • Enhanced the performance of GET and DELETE operations across Oracle, MySQL, PostgreSQL, and MSSQL.
  • Added support for returning REFCURSOR from stored procedures in the Database V2 connector for Oracle Database and PostgreSQL, enabling the process of complex queries that return multiple rows of data via cursors for Oracle Database.
  • The Database V2 connector's Upsert feature now supports JSON data containing double quotes, ensuring correct column updates without escape characters across Oracle, MySQL, PostgreSQL, and MSSQL.
  • The STOREDPROCEDURE operation of the Database V2 connector now accurately handles decimal values in insert, update, delete, and select (with decimal values in WHERE clause).
  • Updated Standard GET operation to skip object and column name validation, enabling parameterized dynamic SQL execution on varying objects.

2025-05 (Version 38)

  • An Info icon was introduced next to the SQL query field in the [INSERT / UPDATE / GET / DELETE] operations. Selecting this icon provides helpful guidance, making it easier to configure these operations, especially after importing an object.

2025-03 (Version 33)

  • The Database v2 operations, GET, INSERT, UPDATE, UPSERT, DELETE and STOREDPROCEDURE now allow you to change the tracking direction, controlling whether Input Documents or Output Documents are shown in Process Reporting.

  • Container logs are no longer flooded with DB connector messages for the Get operation if the Max Rows field was not set.

  • The Database v2 connector now ensures that the operation executes successfully without the Atom crash when performing a Dynamic Insert operation.

  • Resolved an issue so the Dynamic INSERT operation of the Database v2 connector stores JSON data in MSSQL without truncation.

  • The Database v2 connector has been updated to improve the performance of the UPDATE, UPSERT and STOREDPROCEDURE operations across all four supported databases: Oracle, MySQL, PostgreSQL and MSSQL.

  • Column validation now retrieves schema-specific metadata, reducing unnecessary database calls, improving validation efficiency and providing clearer error messages.

2025-01 (Version 30)

  • The Database v2 connector has been updated to enhance the performance of the INSERT action across all four supported databases: Oracle, MySQL, PostgreSQL and MSSQL.

2024-12 (Version 29)

  • The connector now supports Transaction Processing feature for STOREDPROCEDURE action.

2024-11 (Version 25, Cancelled)

  • This version was cancelled during the Runtime release window and reverted back to version 24.

2024-08 (Version 24)

  • The connector now supports Transaction Processing for INSERT, UPDATE, DELETE, and UPSERT actions.
warning

This advanced feature requires careful handling of transactions, as improper use can lead to unintended results. Please ensure that you follow best practices to maintain the integrity and reliability of your data.

2024-06 (Version 22)

  • Resolved an issue where the Filter field was not visible during import operations.

2024-06 (Version 21)

  • When importing stored procedures in the Database V2 connector, the user can specify a string or wildcard to limit the number of stored procedures that are searched.

  • The Database V2 connector resolves the nvarchar parameter successfully when it is used in the WHERE clause of a Standard Get action to a MSSQL database.

2024-02 (Version 20)

  • Processes invoking a Oracle Database stored procedure that has default input parameters with multiple document scenarios execute without error.

2024-01 (Version 18)

  • Users can pass all parameters except default and nullable procedure parameters, else the connector displays an exception message.
    • The Stored Procedure nullable is used when the parameter value is not provided.
  • Users can set Null on the Nullable Stored Procedure parameters.
    • The Stored Procedure default is used when the parameter value is not provided.
  • The connector successfully inserts all the records when Batch Count is entered.
  • The connector successfully returns null value instead of incorrect values when data with null values are fetched from the database.
  • The connector successfully retrieves large integer values (>2147483647) in NUMBER type columns for all Database v2 databases without any error.
  • The connector supports Oracle data type ROWID and successfully imports profile objects from all the database rows including the ones having data type as ROWID without any exceptions.
  • The connector successfully supports inserting/updating/selecting any range of decimal values supported by the Oracle database without any data truncation or loss.
  • Database NULL value is getting inserted for Json datatype when trying to insert a null node while executing the STOREDPROCEDURE action in Database V2-PostgreSQL.
  • Suitable error message is displayed for constraints instead of displaying [400] Bad request for Database V2 operations.
  • The connector supports and stores database NULL, when incoming data of type NVARCHAR is NULL.
  • Test connections successfully work with or without connection pooling enabled for DatabaseV2 connector with PostgreSQL database.

2023-10

  • The update to this connector has been removed from the platform release. If you applied version 14 during the runtime release, be aware that you will be reverted back to version 13.

2023-09 (Version 13)

  • Users can insert null on the nullable parameters using standard insert for NVARCHAR items without getting any errors.

  • Users can update null on the nullable parameters for NVARCHAR items without getting any errors.

  • The connector sends JSON parameters, including double quotes, in the right format to the database.

  • A dynamic null value update is considered valid on all the nullable parameters.

  • You can set Null type on the nullable columns through standard insert.

    This fix is not backward compatible and we recommend the use of null type for all the existing and new nullable inputs.

  • You can set Null type on the nullable columns through upsert.

    This fix is not backward compatible and we recommend the use of null type for all the existing and new nullable inputs.

  • The connector correctly formats the JSON format input parameter for the StoredProcedure action and gives correct format data output to the database.

  • For the stored procedure called from Database V2, the JSON object is successfully formatted for CLOB/VARCHAR type input parameter.

  • The connector correctly handles special characters used in the values for the input parameter of a stored procedure and outputs the correct format data to the database.

On this Page