Thin Client Method Broadcasting

When running in thin client mode, the Automated Test Code Generator (ATCG) does not record a subset of unimplemented control and form event methods, which are defined by internal method masks. For thin clients, the event methods are optimized and are not sent to the application server for execution if unimplemented; ATCG remains unaware that they are called so cannot record them.

You can specify which event methods to omit from this optimization when running ATCG in thin client mode; that is, you can force the broadcasting of unimplemented event methods to the application server so that ATCG can record them.

The Application class methods listed in the following table enable you to force the broadcasting of unimplemented event methods when using ATCG in thin client mode.

Method Description

forceThinClientMethodBroadcast

Marks a single event method to start broadcasting to the application server, even when unimplemented.

isThinClientMethodBroadcastForced

Returns true if the broadcast has been forced for the method specified in the eventMethodName parameter.

resetThinClientMethodBroadcast

Clears the internal collection of broadcasting event methods.

You must invoke a method in the previous table prior to the creation of a form you want it to affect.

The methods have no effect on existing forms.

When calling the forceThinClientMethodBroadcast or isThinClientMethodBroadcastForced methods, Jade finds the superclass of the specified method and uses it to determine whether an event is broadcast.

Internally, Jade will maintain only one collection for each control; that is, Jade effectively ignores user classes and treats the superclass and any derived classes as one class.

If you have subclassed the Button class in your user‑defined schema as MyButton, you can pass Button or MyButton as the first parameter to the forceThinClientMethodBroadcast method.

Similarly for forms, if you have created a Form subclass in your user‑defined schema as MyForm, you pass Form or MyForm as the first parameter to the forceThinClientMethodBroadcast method.

The end result is the same: Button and all subclasses of Button or Form and all user forms will broadcast the event method defined as the second parameter, even when unimplemented.

2020.0.02 and higher