Editing a node in a flow

Edit online

Edit existing nodes in a flow to modify their configuration. When you update a node, IBM® Optim automatically validates compatibility with the rest of the nodes in the flow.

When you edit nodes that contain table mappings, subset conditions, masking policies, or insert definitions, IBM Optim automatically validates the node configuration against any access definition nodes in the flow. If the system detects incompatibilities, it filters out incompatible elements and displays inline warning notifications.

You can edit access definition, subset, masking, and target connection nodes.

Restriction: You cannot edit source or extract nodes.

Nodes must be compatible with the other nodes in the flow. For example, an access definition node must contain all tables and columns that are referenced by downstream nodes such as subset and masking nodes. If IBM Optim detects that a node is incompatible with other nodes in the flow, it is marked with a warning icon that identifies it as incompatible. Edit an incompatible node to make it compatible or remove it from the flow. For more information, see Node validation.

To edit a node in an IBM Optim Data Privacy flow:
  1. From the navigation menu, click Workflow icon Workflow > Flow builder.
  2. Define a new flow or load an existing flow.

    If the flow contains incompatible nodes, a warning notification appears. Incompatible nodes are marked with warning icons. The notification reads: Incompatible nodes detected - This flow contains number nodes that are incompatible with the access definition. Edit or replace the following nodes: node names

  3. From the IBM Optim flow canvas, right-click the node that you want edit, then click Edit.
  4. Update the node configuration to make the changes you require.
  5. Click Save.

    The node is updated with your changes. If the node was previously incompatible, the warning icon is removed after you resolve the incompatibility.

To verify that the flow is ready to run, ensure that no nodes display warning decorations and that the Run flow button in the toolbar is enabled.

Important: The Run flow button is automatically disabled when the flow contains incompatible nodes. The button re-enables only after all incompatible nodes are resolved or removed. You can save a flow with incompatible nodes at any time.

Smart filtering

When IBM Optim detects incompatibilities during node editing, it automatically filters out incompatible elements rather than rejecting the entire edit. The system filters the following elements:

Subset conditions
Removes conditions that reference columns not present in the access definition.
Masking policies
Filters out policies targeting columns unavailable in the access definition.
Insert definitions
Excludes table mappings for tables not included in the access definition.
When items are filtered, IBM Optim displays an inline warning notification. The following notifications can appear:
  • For subset conditions: Incompatible subset conditions removed - number subset conditions were filtered out because they were incompatible with the access definition. This change affects the following tables: table names
  • For masking policies: Incompatible policies removed - number policies were filtered out because they were incompatible with the access definition. This change affects the following tables: table names