Hello,
we want to update to V9.3 and run into an issue.
"References to VI.DialogEngine and other libraries that use System.Windows.Forms cannot be used in scripts anymore."
Regarding (custom) modal forms (in the manager frontend when executing custom DialogTasks), I'm aware of MsgBox and VID_InputBox, but those don't fullfill the needs of popups having dropdowns, multiple input fields, checkbox(es) etc.
Before knowing we'll have an issue with V9.3 i tried ("out of interest" to "be more standard") desperatly to get a form working utilizing the DialogForm-xml-"Framework", but gave up after 1-2 days. Finally as I searched the community and Markus advice in one thread refered to the SDK....which was basically what I did all the time before, but always took it as "lacy workaround" (because vb coding was faster than diving into the "xml-dialog-framework". ) therefore QBM_ShowFormDialog seems not to be usefull for customforms as well.
So....here's my question:
When the "officially advertised" SDK-approach (vb.net coding utilizing system.windows.forms) is not possible anymore, how to implement or configure custom forms / modal popups in that version?
The xml-based approach via Dialog(Logical)Form definition called via QBM_ShowFormDialog (?) seems to be a relic as far as i got to know.
And MsgBox just doesn't fulfill my needs.
And a really "suboptimal" workaround saving inputs in customprops first (yeah, i've seen such stuff!)...is not an option.
Displaying messages in the user interface
Identity Manager 9.3 - Configuration Guide