ecm-impact-analyzer

To perform capability impact analysis, resolve the capability ID using a name lookup or validator, then run the impact workflow against your ECM Studio workspace. This scans mappings, downstream consumers, change requests, and tasks to produce a structured summary of dependencies.

An ECM capability impact report includes identified ancestors, descendants, replacement links, audit events, and generic JSON references. It scopes capability lineage data from mappings, downstream consumers, change requests, and tasks to surface risks before major changes.

Finding downstream consumers and replacement links involves scanning the ECM Studio model repository's mappings, change requests, and tasks. The impact workflow detects these references along with audit events to map capability dependencies and lineage.

Yes, you need a capability ID to run an impact analysis on an ECM Studio model. You can resolve the capability ID using a model validator or a name lookup before executing the impact workflow against your workspace.

Run an impact analysis workflow on your ECM model repository prior to retiring, merging, deleting, moving, or making major changes to a capability. It detects audit events and JSON references to surface dependency risks and guide change decisions.

Yes, impact analysis can detect generic JSON references in ECM model change requests and tasks. It scans these elements alongside mappings and downstream consumers to identify dependencies and replacement links during capability changes.