Might anyone have any information concerning best-practice methodology when creating a customization that contains additional form/module controls. Specifically, I am interested in the proper, or approved method for setting the enable/disable properties of a control, both prior to a new record initialization and after. What I’m trying to do is [1] follow what appears to be current Epicor form/module behavior and [2] ensure that users are not allowed to enter any values in any fields, or click on any buttons until a new record request has been initiated.
I’m working with the Non-Conformance module right now where we need to add in specific Federal Aviation Administration (FAA) information on a non-conformance that currently is not included on the out-of-the-box NonConf form/module. Of course, when I add any control to an additional sheet (especially a button with code behind it), that control is now enabled by default, no matter if a new record has been initialized, or not.
Example:
From the example above, you can see that all of the controls on the added customized sheet are enabled by default when the Non-Conformance module is launched; whereas the standard controls on the module are disabled by default. I want to make sure that the customized controls follow the standard control behavior upon form/module launch.
Is there a best-practice method of doing this (enable all/disable all)?
What about when a user initiates a new record, does not save/commit the record, and decides to delete the “temporary” record that was initially requested? How might I go about disabling the customized controls at that point (returning them to their original disabled state)?
Thanks for any insight you might wish to offer.