Hello All, 

Our team is running into an issue with the Pega 24.2.2 version of web-embed that does provide a reliable web listener we can use in order to reliably track whenever a new case step is in the process of being loaded, and complete.

For Context:
From what we noticed, Pega can take time to process data intensive case steps (either by running complex activities or complex pre/post processing data transforms). Due to this, we would like to listen to when the user navigates between different case steps (either using the Next/Submit buttons or Previous button) and enable/disable a parent level application event while Pega is in the process of loading each step.

• Ideally, this would be in the form of a web-embed event that would fire at the start of each case step (before any data is loaded) and fire again after all items have been processed within that same case step and navigation to the next/previous case step has occurred.
• Assuming validation (or other preventive measures) occurs within the case step that prevents the user from proceeding to the next/previous case step, this event should also fire.  
• It would be nice to have an event listener that tracks the Pega level loading spinner and fires whenever that spinner is on screen (follow it's enable/disable conditions) 

We have tried the official web-embed listeners provided by Pega and have not found that any of them fire in a reliable manner that allows us to enable/disable a parent level application event. Research on the topic led us to using "embedassignmentsubmission" however this event only fires whenever the case step finishes.  

This led us to trying and listen to the DOM events directly to try and control our parent level application event. 

• We were able to attach a click listener that would fire whenever the user clicked on a next/previous/submit button within each of the case steps which we tied to our enable function within the parent app. 
• We were able to use "embedassignmentsubmission" to fire our disable function within the parent app. 

What we noticed is that the more complexity you add to each case step, the harder it can be to fire our disable function within the parent app whenever the user is clicking on a next/previous/submit button.

•  Adding validation to a case step (and having that validation fail) would not fire "embedassignmentsubmission" again as the user is still on the same step 
• There does not seem to be a web-embed function that fires whenever case level validation fails on a step
• Using DOM level listeners to listen for specific HTML elements with attached roles when they appear/disappear on screen proved to be too unreliable for a long term solution
   

We would like some guidance on how we can achieve this functionality using both our parent application and web-embed. 
Thanks in advance,