Skip to end of metadata
Go to start of metadata

How are Netigma Form Events Encoded?


Thanks to the INetigmaFormEventServiceProvider interface that comes with Netigma 3.7+;

  • Before the information form is uploaded; be able to intervene before and after the registration process,
  • To be able to pass the validated function values on the server side of the entered form values,
  • Prevent form registration when necessary,
  • Able to add web controls to the top and bottom of the form

they are provided.

Document Content


The classes that implement the INetigmaFormEventServiceProvider interface are included in the Netigma TypeManager. (See Operations That Must Be Considered). The two lines between the written INetigmaFormEventServiceProvider class can be provided from the netigma meta-management pages. (See Form Event Listener property set to MMS Case Events. This name comes from the DisplayName property in the interface implementation)


Operations To Be Considered


During ITask implementation, the document "Rules to be observed in classes that use TypeManager (Factory) " must be observed.



INetigmaFormEventServiceProvider Members

onPreLoadData(FormEventArgs e)

This method works before the editor values in the form are filled in from the DataRow. Editor values can be changed. In the example below, the method changed the value of freight to 2, as the sum of Freight values for the previous year exceeded 20000.

onPreSave(FormEventArgs e)

After you press the save form button, it runs before the values are saved in the database. If "e.Cancel = true" the form is not saved. The message text sent by "e.Message" is displayed on the data sheet. In the example below, the freight value is checked and the registration is blocked.

OnSaveCompleted(FormEventArgs e)

 Form information works after being saved to the database. In the example below, the method records the value of the freight entered from the form in the test table with the date information.

GetHeaderControl(FormEventArgs e)

Allows custom web control or controls to be added to the form. In the example below, the method has added a label check on the form that shows the order totals for the years above the form. If desired, the script can be register in LiteralControl.For example, in the register script, freightClientInstance.SetValue (1); If an expression is used, the value of the editor to which the freight information is shown is set to 1 on the client side. Thus, this method of the interface can be used to change the values of the editor or to give the initial values. Unlike "preLoadData", the change is made on the client side. The following figure shows the label attached to the form.

GetFooterControl(FormEventArgs e)

Used like GetHeaderControl. Unlike this method, add the control under the form. In the example, the value is returned as null. In this case no control is added to the form. The control can be registered to the page. In these scripts, client process support of forms can be used. categoryname.setenabled (false);

FormEventArgs Class


Sample Application


Sample Also