navigator_invoke_perimeter_type_t

The possible application perimeter type values.

Synopsis:

#include <bps/navigator_invoke.h>
 
typedef enum {
      NAVIGATOR_INVOKE_PERIMETER_TYPE_UNSPECIFIED = 0   
      NAVIGATOR_INVOKE_PERIMETER_TYPE_PERSONAL = 1   
      NAVIGATOR_INVOKE_PERIMETER_TYPE_ENTERPRISE = 2   
} navigator_invoke_perimeter_type_t;

Since:

BlackBerry 10.0.0

Data:

NAVIGATOR_INVOKE_PERIMETER_TYPE_UNSPECIFIED
Indicates that the perimeter type is unspecified.
NAVIGATOR_INVOKE_PERIMETER_TYPE_PERSONAL
Indicates that the application should run in the personal perimeter.
NAVIGATOR_INVOKE_PERIMETER_TYPE_ENTERPRISE
Indicates that the application should run in the enterprise perimeter.

Library:

libbps (For the qcc command, use the -l bps option to link against this library)

Description:

This enumeration defines the possible types of perimeters in which a targeted or queried application can reside. This is used to determine where a target application should invoke, primarily in cases where the application is a "hybrid" that can run in both enterprise and personal perimeters.

Your app should not explicitly set the perimeter, as the Invocation Framework will automatically take care of this across all device configurations (e.g. Personal-only, Balance, Corporate Liable, etc.). If your app sets the perimeter, it may not be able to invoke applications in particular device configurations.