What's new in IBM Optim Data Privacy

What's new in Version 2.0.0

IBM Optim Data Privacy Version 2.0.0 contains a number of new and updated capabilities.

Explore the key capabilities introduced in this release of IBM Optim Data Privacy:

• Connect to more types of data sources and targets
• Switch to your preferred language across the IBM Optim Data Privacy interface
• Restore flow configurations by importing JSON files
• Create flows faster with reusable node templates
• Edit nodes directly in your IBM Optim flows
• Consolidate multiple database sources in a single access definition node
• Export data to multiple databases in a single flow
• Test emerging database connections before production release
• Insert constant values into database columns during data transformation

Connect to more types of data sources and targets

For a full list of supported data sources, see Supported data sources and targets.

Switch to your preferred language across the IBM Optim Data Privacy interface

Set your preferred language in your browser settings, and IBM Optim Data Privacy automatically displays all menus, labels, messages, and help text in that language. Your language choice persists across sessions, so you only need to set it once.

Restore flow configurations by importing JSON files

You can now import previously exported flow definitions directly from JSON files into the IBM Optim Data Privacy flow canvas. This feature eliminates the need to manually recreate flows. Simply select a JSON file, review the flow details, and choose whether to open it in a new canvas or replace your current flow. The system automatically validates the file structure, verifies connection compatibility, and preserves all node relationships and connections during import.

For details, see Importing and exporting a flow.

Create flows faster with reusable node templates

You can now save any configured node as a reusable template and instantly create new nodes from your template library. Instead of manually reconfiguring access definitions, subset rules, or masking policies for each flow, drag a template onto your canvas and create a fully configured node in seconds. Save your newly configured nodes as templates to give yourself a head start the next time you need to create similar nodes. This eliminates repetitive configuration work, ensures consistency across your flows, and helps you to standardize data privacy policies and access controls across projects.

For details, see Creating and working with template nodes.

Edit nodes directly in your IBM Optim flows

You can now edit existing nodes in your flows without having to delete and recreate them. Simply right-click any access definition, subset, mask, or target database node and select Edit to modify table mappings, subset conditions, masking policies, or insert definitions. The system automatically validates your changes against access definition constraints and filters out any incompatible elements, displaying clear warnings so you can resolve issues before running the flow.

For details, see Editing a node in a flow.

Consolidate multiple database sources in a single access definition node

You can now connect to multiple database sources within a single access definition node, eliminating the need to create separate flows for each database. When you add multiple sources, the system automatically identifies and disables related tables to prevent circular dependencies, reducing configuration errors. If you remove an access definition node, all associated source connections are automatically cleaned up, maintaining your flow's integrity. This streamlines complex data workflows while remaining compatible with your existing single-source configurations.

For details, see Creating an access definition.

Export data to multiple databases in a single flow

You can now distribute your data to multiple database destinations in a single flow. When you create a target node and select a database as the export option, you can add multiple target databases instead of being limited to just one. The improved flow builder interface shows you all source and destination mappings on the screen and displays all target connections in a flow diagram.

For details, see Defining a target.

Reuse extract files across workflows to maintain current datasets

You can now create extract files that multiple workflows can write to, ensuring your data stays current rather than creating separate files for each workflow run. When you configure a new extract file, enable the allow overwrite option to let subsequent workflows update the same file location with fresh data. Later, when building additional workflows, you can select any file marked for overwriting and reuse both its configuration settings and its file location. This approach helps you maintain a single, up-to-date dataset instead of managing multiple snapshot files, while also streamlining workflow creation by eliminating redundant file configuration.

For details, see Defining a target.

Test emerging database connections before production release

You can now connect to new data sources in IBM Optim Data Privacy before they're fully validated for production use. When you enable tech preview connections, you gain early access to emerging database integrations with clear indicators showing their preview status. This lets you evaluate and test new connectivity options in your development environment while IBM completes end-to-end validation.

For details, see Exploring and defining connections.

Insert constant values into database columns during data transformation

You can now insert fixed values directly into target database columns without copying from source data. When transforming data in IBM Optim Data Privacy pipelines, you can set constant values like default flags, status indicators, or standard text across all rows. This simplifies data migration by eliminating the need to prepopulate source columns with repetitive values.

For details, see Literal column mapping (API).