@FnuA17547776
I’m not aware of a supported OOTB mechanism to invoke a portal-level JavaScript callback with assignment-level context on each view navigation without using an extension pattern. If you want to avoid a custom DX component, the practical fallback is to keep Pendo initialized globally and detect navigation changes indirectly (for example, SPA URL changes or rendered page metadata), then call the Pendo Location API with the derived context.
If the requirement is to reliably pass assignment-level details into JavaScript on every assignment/view load, a custom DX component or another supported extension point is the cleaner and more upgrade-safe approach.