MyOp Integration

Micro-frontend context, captured automatically.

When a page mounts MyOp components, Impact attributes them at runtime and attaches the details to your ticket - so a report about an embedded widget arrives with the exact component behind it.

How it works

1 Record or screenshot a page that mounts MyOp components, as usual.
2 Impact attributes the active MyOp components at runtime (component UUID + variant); for screenshots the runtime channel is combined with a Vision hint.
3 The ticket gets a MyOp block appended as a separate Monday reply - each mounted component with a link back to its owner.

What you get

The MyOp component UUID and variant captured automatically.
A dedicated MyOp block on the ticket (component + owner link), separate from the main body.
No manual "which widget was this" archaeology.

Use cases by role

How different people on the team get value from MyOp Integration.

PM / Product

Know exactly which embedded component a report is about, without guessing.

Developer

Get the component UUID and owner link up front - go straight to the right micro-frontend.

Designer

See which shared MyOp component a visual issue involves.

File an issue on an embedded widget with the component identity already attached.

Support

Escalate an embedded-widget problem with the owning component named.