Workflow Soluiton

I'm trying to make a web form for my HR group to use to deactivate/terminate users.  Ideally, I want to have a dropdown populated with an ADUserInfoSummary array where they can select a user.  Ideally, I'd like to then execute a Get Users with Details on the selected user from within that same form so they can quickly see the user's manager and office location.

I figure I can accomplish this by wrapping the dropdown and ascii merge label components within a DynamicUpdatePanel, but I can't figure out how to trigger additional workflow components to run when the value of that dropdown changes.  My only other way around this would be to have the user select an item from the list on one page and click a Next output to exit that form builder, process additional workflow components, then bring up a new form builder window with the settings.

If possible, I'd like to keep everything on a single form.

Any ideas?

I have attached a demo project that may give you an idea of how to do this. It contains a panel that is conditionally visible to display the User Manager and User Location. The panel is hidden on first entry into the form. The drop-down selection in the form has a Custom Event setup to click a button (button is hidden beneath the 'Submit' button) once a selection is made in the drop-down component. The button's purpose is just to have a path to pass out of the form and do a GetUser with Details component search based on the selection in the drop-down. It then passes back into the form to then change the panel to visible to show the User Manager and Location.

Its pretty basic and there might be better ways to do this but to the end-user the process always appears to never leave the form so it should solve how to do what you want to accomplish on the one form.

Attachment(s)

DEMO_ADUserSelection.zip   1.05 MB 1 version

When the value of the dropdown placed on DynamicUpdatePanel changes the postback is happening. So the controls on page are rendered again and theoretically you can use embedded models inside controls (for selecting items, initializing data etc.) even add special hidden control only for such action. But it's not a good solution because this models are executed more then once in reaction for one event.

It's not clear for me why you think that you have to go to another form. You can go from current form to Embedded Model component outside this form and return to the same form.
If you don't want to leave current form at all maybe using Embedded Action Button would be suitable. But you must be careful because it seems that Embedded Action Button could have a bug.

Bruce,

This seems to work pretty good in IE.  I noticed that the "update" button can't be Visible = False so I hid it behind the continue button like you did in your example.  Neither Firefox 8 nor Chrome seem to want to show the ajax panel, though.  Have you seen that issue?