Product integration

Verify specific objects and outcomes across products. See the governance journey and business scenarios.

Relationship	Boundary
Metadata and SQLink	Object-based basic lineage versus advanced lineage capabilities
Catalog and marketplace	Asset administration versus discovery, requests, and approval records
Security and gateway	Governance rules versus JDBC masking and audit
DAM and DIG	Optional AI assistance subject to license and permissions

Configuration guides

• REST API guide and scenarios: module selection, calls, and acceptance.
• Field standards mappings: establish links and verify reverse references.
• Classification design: reuse catalog spaces and check levels and attributes.
• BI integration tasks: configure and test target results.
• Access policies and JDBC: validate runtime protection.
• SQLink interfaces: confirm contracts and authentication.
• DIG approvals: verify actual results in each target module.

Source data, governance metadata, and application records serve different purposes. A working interface does not establish synchronized business state.

Integration acceptance

Check	Evidence
Identity	Verified system, schema, object, asset, or metric mappings beyond names
State	Distinguish draft, review, publication, closure, and verification
Permissions	Test maintainer, reviewer, and consumer functions and data scopes
Traceability	Tasks, approvals, logs, calls, time, and owners
Recovery	Defined return point for harvesting, definitions, mappings, rules, policies, or publishing