Appendix

API Descriptions

Type	Name	Argument	Description
Load Settings	setConfig	tenantURL	NF connection URL
		projectDetailURL	URL to get the configuration file from
		eumURL	eum data collection URL
		delegate	NetFunnel delegate Declarations view location
		oneTimeCallback	After setConfig has successfully loaded the configuration file, a callback function is executed once per year.
URL based NF	startManager	URL	URL registered in the NF console
URL based NF	completeManager	URL	URL registered in the NF console
Key based NF	NFStart	projectKey	The project key can be found in the NetFUNNEL console. ex) service_1
		segmentKey	The segment key can be found in the NetFUNNEL console when creating a segment. ex) segKey_1234
Key based NF	NFStop	projectKey	The project key can be found in the NetFUNNEL console. ex) service_1
		segmentKey	The segment key can be found in the NetFUNNEL console when creating a segment. ex) segKey_1234
Key based NF (Path Control)	NFStartSection	projectKey	The project key can be found in the NetFUNNEL console. ex) service_1
		segmentKey	The segment key can be found in the NetFUNNEL console when creating a segment. ex) segKey_1234
Key based NF (Path Control)	NFStopSection	projectKey	The project key can be found in the NetFUNNEL console. ex) service_1
		segmentKey	The segment key can be found in the NetFUNNEL console when creating a segment. ex) segKey_1234
delegate	SurffyActionSuccess	projectKey	The project key can be found in the NetFUNNEL console. ex) service_1
		segmentKey	The segment key can be found in the NetFUNNEL console when creating a segment. ex) segKey_1234
		retcode	The result code of the request at the time of delegate execution
delegate	SurffyActionError	projectKey	The project key used on entry ex) service_1
		segmentKey	The segment key used on entry ex) serKey_1234
		retcode	The result code of the request at the time of delegate execution
delegate	SurffyActionCancel	projectKey	The project key used on entry ex) service_1
		segmentKey	The segment key used on entry ex) serKey_1234
		retcode	The result code of the request at the time of delegate execution
delegate	SurffyActionBypass	projectKey	The project key used on entry ex) service_1
		segmentKey	The project key used on entry ex) serKey_1234
		retcode	The result code of the request at the time of delegate execution
delegate	SurffyActionBlock	projectKey	The project key used on entry ex) service_1
		segmentKey	The segment key used on entry ex) serKey_1234
		retcode	The result code of the request at the time of delegate execution
delegate	SurffyCompleteSuccess	projectKey	Return Keys Called project key  ex) service_1
		segmentKey	Return Keys Called segment key  ex) serKey_1234
delegate	SurffyCompleteError	projectKey	Return Keys Called project key  ex) service_1
		segmentKey	Return Keys Called segment key  ex) serKey_1234

FAQ

Q. What is retcode given in Delegate, and when is it needed?

A. The retcode (Return Code) is the result code that you receive from the NetFunnel server when you make a virtual wait request. You can use a combination of retcode and delegate to define your own logic. Please refer to the example of implementing a callback that is called when an entry/waiting error occurs.

ex) If you want to bypass the wait when you receive a network disconnection code (retcode : 0) when requesting to wait for a service.

func SurffyActionError(projectKey: String, segmentKey: String, retcode: Int) {

if(retcode == 0){
/*
Implement logic to enter the service
*/
}
}

ex) If you want to block a service waiting request when it receives a network disconnection code (retcode : 0)

func SurffyActionError(projectKey: String, segmentKey: String, retcode: Int) {

if(retcode == 0){
/*
Implement logic to block the service
*/
}
}

Q. I want to use Netfunnel when my application launches but it doesn't queue up, what should I do?

A. If a NetFunnel request is called before the NetFunnel settings are loaded, the request may not queue properly. This can be handled by using an initialization function (oneTimeCallback).

Q. What is basic control and what is section control and what is the difference between the two?

A. A basic control is a control that waits for some logic or the action itself. A basic control's wait key return occurs immediately after the wait (when you key return to SurffyActionSuccess), which reduces the order of the next waiter.

ex) Wait for application input, wait for button click

Interval control is a control that waits for a specific logic or action interval. By setting an entry point and an exit point, a section control throttles traffic only by the total number of entries allowed between entry and exit. The waiting key return of a section control is executed only when an explicit key return function is called.

ex) Login (Entry) - Logout (Exit), Page Enter (Entry) - Page Navigate (Exit)