Thanks for the response and question! :-)  Sorry I wasn't clear.  We are using the OOTB pyUpdateWorkParties flow action launching in a modal dialogue from the Review Harness.  In the parties, the user can enter a key (account number for example).  There is a button on the section that calls an activity which makes various SOAP calls to retrieve the information required for that party from the SORs.  The activity is called from different places (sometimes headless during create of case object, sometimes from a connector flow action, sometimes from modal dialogue, etc.)  So, the activity sets the return harness and uses Show-Harness to exit the activity and return to the necessary page.  When we click the button and run the activity from the Modal dialogue, when the activity returns and populates the party section, the modal dialogue does not stay open so that we can hit submit and save the change.  Instead, it closes and returns to the Review harness.  As a result, the party is not persisted and if a flow action for example is not executed immediately after, the party is lost.  I imagine that the reason the modal dialogue is not staying open is our Show-Harness call.  So, I am looking for an alternative mechanism to return to the modal dialogue...  I also wondered if we would return to the modal dialogue without the Show-Harness call, but when I created a parameter and passed it in so that I could check when we were coming from the modal dialogue and just exit the activity before the Show-Harness, the behavior was the same... the modal dialogue still closed and took me back to the Review Harness.

Any ideas on how to stay in the modal dialogue would be greatly appreciated :-).

Thanks!

Scott