Glad to provide an example....
As I said earlier my existing, in production, generic configurations use Action variables which have to set in the calling configuration. The more variables the more chance for mistakes.
Using my new approach I now set 1 action variable with a json string and my generic configuration consumes that string via a query action.
The attached configuration will eventually include all of my generic DNN User procedures but this one only has 1 region so far for the Login process, called "Login" .....Note I haven't had a chance to test this but you get the idea of where I am going
I call this procedure via the Goto Action but before I do I assign an action variable called Parameters with a json string with the values I want consumed. In this case it would look like
I think I need to make a few changes such as encoding/decoding the values in the json but again you get the idea.
If anyone has any other comments about things I should look out for please let me know.
My full version of this configuration has functions such as Login, DNN Account creation, Password Change, Username Change, Assign To Role, Delete from Role and Delete from User. I will gladly share once I have rebuilt it using this new approach