Quickstart OutSystems Developer Cloud (ODC)
This guide will help you implement the Group Link SDK in your application developed in the OutSystems Developer Cloud (ODC).
The GroupLinkSDK mobile library is designed to natively handle the complex management of Bluetooth, Background Services, Location and Notification permissions, ensuring full compatibility with iOS 12+ and Android 8+.
Requirements
- Required software:
- Required permissions:
- Access the OutSystems Forge to download dependencies.
Step 1 - Obtaining the Mobile Library
The GroupLinkSDK Mobile library is available in the OutSystems ecosystem.
- In ODC Studio, click on Install from Forge.

- Search for GroupLinkSDK and click Install.

- Open the Mobile library from the GroupLinkSDK in ODC Studio, click Try library, select your application, and click Confirm.

Step 2 - Configuring platform specifics (Required)
For the SDK to function in the background and interact with network interfaces on iOS, it is strictly necessary to inject native configurations at compile time (MABS). OutSystems ODC requires that the final application "own" these configurations.
Creating the buildAction.json file
- On your computer, create a text file called buildAction.json.
- Paste the exact JSON code below into it. This code injects the necessary
Background ModesandNetwork Entitlementsfor iOS:
1{2 "platforms": {3 "ios": {4 "plist": [5 {6 "replace": false,7 "entries": [8 {9 "UIBackgroundModes": [10 "location",11 "bluetooth-central",12 "bluetooth-peripheral",13 "fetch",14 "processing"15 ],16 "BGTaskSchedulerPermittedIdentifiers": [17 "com.grouplinknetwork.bgtask"18 ]19 }20 ]21 }22 ],23 "entitlements": {24 "replace": false,25 "entries": [26 {27 "com.apple.developer.networking.wifi-info": true28 }29 ]30 }31 }32 }33}
Importing into the App's Resources
- In ODC Studio, go to the Data tab and find the Resources folder.
- Right-click, select
Import Resource, and add yourbuildAction.jsonfile. - Select the imported file and change the Deploy Action to
Deploy to Target Directory.

Referencing App Extensibility
- Click on your App name at the top of the tree and click on Edit app properties.
- Navigate to the Extensibility tab.
- Add the following JSON to tell the compiler that it should read the file we created in the previous step:
1{2 "buildConfigurations": {3 "buildAction": {4 "config": "$resources.buildAction.json"5 }6 }7}

Step 3 - Using the SDK Client Actions
The GroupLinkSDK exposes 4 Client Actions. You can drag them into your logic flows.

StartSDK
Initializes the Group Link SDK in the application.
- How to use: Requires you to pass your authentication
Token(provided by Group Link). - It is recommended to call this action in the application's initialization event (
OnReady), on the application's first screen.
- It is recommended to call this action in the application's initialization event (

RequestPermissions
It intelligently handles all the complex logic of requesting native user permissions.
- How to use: Simply drag and drop into the app's input stream.
- It is recommended to call this action in the application's initialization event (
OnReady), on the application's first screen, right below the StartSDK action.
- It is recommended to call this action in the application's initialization event (
- Technical Note: The SDK automatically identifies the operating system version and adapts the request to avoid crashes.
- Android 11 → will only request
Location(necessary for BLE scanning on older systems). - Android 12 → will request
LocationandBluetoothpermissions. - Android 13+ → will request permissions for
Location,BluetoothandNotifications.
- Android 11 → will only request

StartSDKAndRequestPermissions
A convenience action that unifies the two previous functions (StartSDK and RequestPermissions) into a single node.
- How to use: Requires you to pass your authentication
Token(provided by Group Link). Ideal for flows where you want to initialize the SDK and immediately display the permissions pop-up to the user. - It is recommended to call this action in the application's initialization event (
OnReady), on the application's first screen.
- It is recommended to call this action in the application's initialization event (

SetNotificationName
Configures remote device identification. To identify the device from your remote database or platform, you must assign a unique identifier using this method.
- How to use: Receives the
NotificationName(String) parameter.
IMPORTANT: Calling this method is mandatory for generating certain platform reports. For more information on which reports require this configuration, please contact our support team.

Now that the Group Link SDK is implemented and the native features are configured, your ODC application is ready to interact with our ecosystem!