Local Actions launched from a screen flow inherits the harness of the screen flow(TabbedScreenFlow7). 

We have a case wide local action which will open the Local actions by replacing the current assignment. In such scenarios, we are seeing the bread crumbs of the screen flows and the previous/ Next buttons of the screen flow which is not right. we would like to hide the bread crumbs and the screen flow buttons here and display the actual flow action buttons.

Is there a way to open the local action in a perform harness rather than the screen flow harness when the local action is launched from the screen flow?