Dialog box or pop Up in Interface without using record action / process model

The only workaround past using a Record Action for this use case (itself a workaround) is to use an in-interface approach that hides the main interface and creates a "mock" pop-up with a card in the middle of the screen - Stefan Helzle  has a recipe published for this on his blog IIRC.

I still have an outstanding feature request for them to just (finally) allow Start Process Link to choose a target of "pop up", but i'm not holding my breath.

Hello Mike, is this feature ready yet? We miss this a lot.

No. The ones who want this feature are still waiting for it.

I also miss it a lot, but as I said a long time ago, I'm not holding my breath - Appian realllllly wants to force us to use Record Actions for all possible use cases (even when they're vastly inappropriate use cases) and therefore will probably not give us this functionality in other places, for fear of diluting the necessity of the features they are pushing on us.  Sadly that's true for a bunch of the QoL feature requests I've been asking for, even ones that I'm pretty sure would be dead simple to implement.

Thank you, Mike I agree with Appian's direction in this to push for using record actions, but where it hits the wall is the single parameter that it takes which is the record identifier. Do you have any recommendations how we can pass multiple parameters to open another Screen/Form in a new tab or dialog?

my prior suggested workaround is probably the only current (supported) solution.  as far as a "stretch case" solution, you don't strictly *have* to call a record action in relation to an actual item in a record type - for instance you could call a record action and pass in arbitrary data that does something completely unrelated.  I wouldn't be surprised if someone had staged a whole "fake" record type (like with a single "dummy" entry with id "1") merely to be a container for record actions that could be called in a dialog.  I haven't gone that far myself yet (so can't make any promises as to the feasibility), but i've been sorely tempted here and there.

my prior suggested workaround is probably the only current (supported) solution.  as far as a "stretch case" solution, you don't strictly *have* to call a record action in relation to an actual item in a record type - for instance you could call a record action and pass in arbitrary data that does something completely unrelated.  I wouldn't be surprised if someone had staged a whole "fake" record type (like with a single "dummy" entry with id "1") merely to be a container for record actions that could be called in a dialog.  I haven't gone that far myself yet (so can't make any promises as to the feasibility), but i've been sorely tempted here and there.