Root > Reference > All Types > TELEvCustomWebFieldsRequestProc

Type TELEvCustomWebFieldsRequestProc

Previous pageReturn to chapter overviewNext page   

Procedural event handler for OnCustomWebFieldsRequest event.

 

Unit

EEvents

 

Syntax

 

Code (Delphi)

TELEvCustomWebFieldsRequestProc = procedure(

const ACustom: Pointer;

AExceptionInfo: TEurekaExceptionInfo;

ASender: TObject;

AWebFields: TStrings;

var ACallNextHandler: Boolean

);

 

Parameters

ACustom [in, optional]

Custom user data parameter. It's the same pointer as it was passed to RegisterEvent-function.

 

AExceptionInfo [in, optional]

Information about exception. Can be nil.

 

ASender [in]

Current sender class (child class of TELUniversalSender).

 

AWebFields [in]

Web fields to send to web-site (as name=value pairs).

 

ACallNextHandler [out]

True (default) - call next registered event handler, False - do not call next event handler.

 

Remarks

This event is invoked before sending to allow you to supply custom fields. Fields should be supplied as name=value pairs. We recommend to use the following construct: AWebFields.Values['Field-Name'] := 'Field-Value'. Field name depends on used send method.

 

For example, if you are sending to Mantis - then field name would be custom field name as it appears in Mantis configuration (e.g. like 'cf_count').

 

This event is not called if send method does not need / support custom fields.

 

Warning

Do not confuse custom fields (OnCustomDataRequest event) and web fields (OnCustomWebFieldsRequest event). Custom fields are inserted into bug report file. Web fields are not stored in bug report, web fields are POST-ed to bug tracker / web-site via API or HTTP request.

 

Note

AExceptionInfo param will be missing if sending is performed outside of exception processing. E.g. if sending is called manually.

 

Important!

EurekaLog will can the OnCustomWebField event only when sending a bug report. If you are invoking sender manually (for example, to send a feedback - there will be no bug report, so the OnCustomWebField event won't be called. This is done because the event handler might not expect to be called to send something other than a bug report (i.e. the AExceptionInfo param is nil), and it might crash or populate the fields incorrectly. However, if you've written a handler that can handle both error reports and feedback, you can tell EurekaLog about it by setting the _AlwaysCallCustomWebFieldsRequest global variable (from the ESendWeb unit) to True on startup of your application. If you need to distinguish between sending an error report and sending feedback in your event handler, you can pass a custom field in sending options.

 

Important!

Any event is called from the context of exception thread, which may be not the main thread of application. Thus, it's highly recommended to avoid using any global-like data and to avoid access VCL objects. If you still need to do any of that - please use proper thread synchronization for globals and Synchronize method for VCL access.

 

See also




Send feedback... Build date: 2026-06-30
Last edited: 2026-06-30
PRIVACY STATEMENT
The documentation team uses the feedback submitted to improve the EurekaLog documentation. We do not use your e-mail address for any other purpose. We will remove your e-mail address from our system after the issue you are reporting has been resolved. While we are working to resolve this issue, we may send you an e-mail message to request more information about your feedback. After the issues have been addressed, we may send you an email message to let you know that your feedback has been addressed.


Permanent link to this article: https://www.eurekalog.com/help/eurekalog/topic_type_EEvents_TELEvCustomWebFieldsRequestProc