Legacy platform

Manipulate the application-provided API input or output

You can change the application behavior suitable to your business by stopping the execution of the application-provided API. You can manipulate the output of an application-provided API after any mashup call by adding subscribers to an event in extension.

Manipulate the application-provided API input

The beforeBehaviorMashupCall event gets published for mashups that are called for BehaviorController. If you want to stop any mashup call, you can add a subscriber before the beforeBehaviorMashupCall event in extension. The subscriber must return false to stop the execution of the application-provided mashups.

For example, define the subscriber for beforeBehaviorMashupCall as follows:
subscribers: {
    local: [{
	      eventId: 'beforeBehaviorMashupCall',
	      sequence: '51',
         handler: {
	           methodName: "extn_beforeBehaviorMashupCall"
	       }
    }]
}

You can determine the logic that is based on the mashup context and mashups array that is passed in the subscriber.

Note: The beforeBehaviorMashupCall event is raised only for mashups that are run by using callApi and callApis utility methods in wsc.utils.UIUtils. You cannot stop the execution of mashups that are called for InitController.

Manipulate the application-provided API output

The afterBehaviorMashupCall event gets published for mashups that are called for BehaviorController. If you want to manipulate the API output after any mashup call, add a subscriber for the afterBehaviorMashupCall event in extension.

For example, define the subscriber for afterBehaviorMashupCall event as follows:
subscribers: {
    local: [{
	      eventId: 'afterBehaviorMashupCall',
	      sequence: '51',
         handler: {
	           methodName: "extn_afterBehaviorMashupCall"
	       }
    }]
}

You can determine the logic that is based on the mashup context and mashups array that is passed in the subscriber.

Note: The afterBehaviorMashupCall event is raised only for mashups that are run by using callApi and callApis utility methods in wsc.utils.UIUtils. The afterBehaviorMashupCall event is not published for mashups that are called for InitController.