Sending invocation

Bound invocation

The following image show how a client application can use the bound invocation to invoke a target application of its choice. In this case, App 2 opens the document contained in the client application.

Diagram showing how a client application can use the bound invocation to invoke a target application of its choice

Here's an example that shows how to send an invocation request:

target: "com.example.image.view ",
action: "bb.action.OPEN",
type: "image/png",
uri: "file:///path/to/image.png"
}, onSuccess, onError);

Once the invocation request is sent, the invocation response is handled by the invocation framework itself. However, you must create JavaScript functions to handle the success or error events. Here's a sample that shows you how to do that:

function onSuccess() {
    console.log("<p>Invocation successful</p>");
function onError(error) {
    console.log("<p>Invocation error: " + error + "</p>");

Target discovery

After learning about how to send an invocation, you must be wondering how you can determine what targets are available on the device. This section deals with exactly that. You can hard code the target application that you want to send an invocation message to, or you can query the invocation framework to find out what targets are installed on the BlackBerry device. The invocation framework uses a target filter to allow the target applications to declare the types of invocation they support. When a client application queries the invocation framework, the framework uses the target app's filter to describe the kind of target it is looking for and the data it has to offer.

The quality of the results is generally dependent on how specific the target query request is. A target query request should consist of the URI and the MIME type. If the MIME type is left out, the framework tries to determine the type using the URI.

A client application can include the action, to be performed on the data, in its target query request. If the action is not specified in the target query request, the query result will contain a list of all the actions that can be performed on the specified data by the available targets.

The invocation framework returns a query result which includes the targets grouped by the action that these targets support. For each target, the query result provides the target ID, the target type (an application or a card), and other information about the target, such as icons and labels, that can be used to display the target in the client application's screen.

To determine what targets are suitable candidates, the invocation framework applies a set of brokering rules. For more information, see Target selection and brokering process.

The following code demonstrates a target query request in which a client application searches for targets that support the bb.action.OPEN action on image/png images, which are sent as a file:// URI.

var request = {
    "action": "bb.action.OPEN",
    "type": "image/png",
    "uri": "file://path/to/image.png",
    "target_type": ["APPLICATION", "VIEWER"],
    "action_type": "ALL"

blackberry.invoke.query(request, onSuccess, onError);

Here's how you can handle the results:

function onSuccess(response) {
    console.log("<p>Invocation query response: " + response + "</p>");
    var data = JSON.stringify(response);
    //can now parse the data variable for invocation targets
    // that matched the query criteria

function onError(error) {
    console.log("<p>Invocation query error: " + error + "</p>");

Unbound invocation

In this section, you will learn how the invocation framework can make invoking a target application easy, by removing the need to query. Instead of sending a target query request to determine the available targets, the client application can simply send an invocation request to the framework without specifying a target. This kind of invocation is called unbound invocation. If you send an unbound invocation, the framework searches for and invokes a suitable target application for you.

The following image shows how a client application (App 1) lets the invocation framework return the most suitable target app for a particular action. In this case, App 2 is the most suitable application to open the document contained in the client application.

Diagram showing how a client app lets the invocation framework return the most suitable target app for a particular action.

To find the best candidate, the framework first uses a brokering process. It applies a set of rules to determine which target applications support the client application's invocation request. If there is more than one suitable target available, the framework applies a set of selection rules to choose the most appropriate target. For more information, see Target selection and brokering.

You can also send an invocation request without specifying an action item, since only the data is sent. The framework determines the type of target and the action to be performed.

If you don't define the action parameter, the invocation framework tries to find an appropriate target application for the bb.action.VIEW action. If no suitable target application is found for bb.action.VIEW, the invocation framework falls back to determine an appropriate target application that supports bb.action.OPEN. If still no suitable target application is available for bb.action.OPEN, the invoke request is unsuccessful.

The following sample code shows how you can easily create an unbound invocation. The sample code invokes the most suitable target application to handle the image.png file, specified by the URI.

uri: "file:///path/to/image.png"
}, onSuccess, onError);

Last modified: 2014-10-09

Got questions about leaving a comment? Get answers from our Disqus FAQ.

comments powered by Disqus