Tool configuration lost after bad database login

[DaveSchloat]

Hey Gang, I created a database query, and in order to make the WF shareable, I added user inputs/actions for username and password.

I added "username" to the database connection string so that I wasn't putting MY user ID out for everyone.  When you hit the magic wand, everything works fine.  But I accidently hit the "run" button instead, which is easy to do, and naturally the database login failed because "username" is not a real user id.  

Then my unique tools and data cleansing tools (and probably others I didn't notice) lost their configurations....the windows were blank because no data came through, and the tools reconfigured to receiving no fields, and reported that they needed to be configured.

Is there a way to guard against this?  Like can I turn off the "run" button, or force the tools to remember their configs?

[mceleavey]

Hi @DaveSchloat ,

the tools should not lose their config but will error due to the data being missing.

If you were to re-run using the wand the workflow should run correctly.

Give it a try and show us the screenshots if it clears the config again.

M.

[DaveSchloat]

Thanks - I tested your idea a few times.  Turns out that if you run it with the bad username, then click on the tool (unique, cleaner, whatever), THAT is what clears the config.  I guess clicking the task forces it to re-evaluate the incoming data.  If you can avoid clicking on the tools that may be affected, then it won't happen, and you can use the magic wand to run.