Camera, GPS, and Push Notifications in OutSystems Mobile

Go to **forge.outsystems.com** in your browser. Search for **Camera Plugin** (by OutSystems). Check the compatibility badge shows your MABS version is supported. Click **Install** → select your environment → confirm. Once installed, back in Service Studio: press **Ctrl+Q** (Manage Dependencies). In the Producer search, type **Camera Plugin** → expand it → check **CameraPlugin** under the Client Actions section → expand Logic → check: `TakePicture`, `ChooseFromGallery`, `GetCameraSettings`. Click **Apply**. TrueChange confirms the dependencies are resolved. The Camera Plugin actions appear under Logic tab → Client Actions → CameraPlugin.

In Service Studio, open the screen where you want camera functionality. Create a **Client Action** named `CapturePhoto` (right-click screen → Add Client Action). Create Local Variables: - `CapturedImageB64` (Text) — stores the base64-encoded image string - `ImageBinary` (Binary Data) — for converting and storing - `CameraError` (Text) Action flow: ``` Start → TakePicture Quality = 80 (integer, 0-100) Width = 1024 (max pixel width) Height = 1024 (max pixel height) CorrectOrientation = True EncodingType = JPEG (JPEG or PNG) → If TakePicture.Success [True] → Assign CapturedImageB64 = TakePicture.ImageCaptured → ConvertB64ToBinary (use TextToBinaryData built-in) → Assign ImageBinary = ConvertB64ToBinary.BinaryData → Call Server Action to save ImageBinary to entity [False] → Assign CameraError = TakePicture.Error.Message → End ``` To display the image immediately: add an Image widget → set Source to `"data:image/jpeg;base64," + CapturedImageB64`

1/* TakePicture Client Action call — in CapturePhoto Client Action */
2
3/* Plugin action parameters */
4TakePicture(
5  Quality:            80,
6  Width:              1024,
7  Height:             1024,
8  CorrectOrientation: True,
9  EncodingType:       Entities.CameraEncodingType.JPEG,
10  MediaType:          Entities.CameraMediaType.PICTURE,
11  AllowEdit:          False,
12  SaveToPhotoAlbum:   False
13)
14
15/* Output parameters */
16TakePicture.Success        /* Boolean */
17TakePicture.ImageCaptured  /* Text — base64-encoded image data */
18TakePicture.Error.Message  /* Text — error description */
19
20/* Display captured image inline */
21/* Image widget Source property expression: */
22"data:image/jpeg;base64," + CapturedImageB64
23
24/* Convert base64 to Binary Data for storage */
25/* Use TextToBinaryData() built-in function: */
26TextToBinaryData(CapturedImageB64)

Install the **Location Plugin** from Forge (search 'Location Plugin', by OutSystems). Add dependency via Ctrl+Q → Location Plugin → check `GetLocation` Client Action. Create a Client Action `GetCurrentLocation` on your screen: Local Variables: `Latitude` (Decimal), `Longitude` (Decimal), `Accuracy` (Decimal), `LocationError` (Text) Action flow: ``` Start → GetLocation EnableHighAccuracy = True (uses GPS, not just cell towers) Timeout = 10000 (10 seconds in milliseconds) MaximumAge = 0 (always get fresh reading) → If GetLocation.Success [True] → Assign Latitude = GetLocation.Latitude → Assign Longitude = GetLocation.Longitude → Assign Accuracy = GetLocation.Accuracy [False] → Assign LocationError = GetLocation.Error.Message → End ``` After getting coordinates, display them in expression widgets or pass to a Server Action to save them with a record or calculate distance using your own formula.

1/* GetLocation Client Action call */
2GetLocation(
3  EnableHighAccuracy: True,   /* True = GPS, False = network/wifi */
4  Timeout:            10000,  /* milliseconds before timeout error */
5  MaximumAge:         0       /* 0 = always fresh; N = use cached if < N ms old */
6)
7
8/* Output parameters */
9GetLocation.Success     /* Boolean */
10GetLocation.Latitude    /* Decimal — e.g., 40.712776 */
11GetLocation.Longitude   /* Decimal — e.g., -74.005974 */
12GetLocation.Accuracy    /* Decimal — meters radius of accuracy */
13GetLocation.Altitude    /* Decimal — meters above sea level */
14GetLocation.Error.Code     /* Integer */
15GetLocation.Error.Message  /* Text */
16
17/* Display coordinates with 6 decimal places */
18DecimalToText(Round(Latitude, 6)) + ", " + DecimalToText(Round(Longitude, 6))
19
20/* Calculate approximate distance between two points (Haversine — simplified) */
21/* For production use, call a mapping API from a Server Action */
22/* Google Maps static link: */
23"https://maps.google.com/?q=" + DecimalToText(Latitude) + "," + DecimalToText(Longitude)

Both camera and location plugins request permissions at runtime (iOS and Android require explicit user consent). Handle the permission flow gracefully: **Check permission status before calling the plugin:** Use the Camera Plugin's `CheckCameraPermission` and the Location Plugin's `CheckLocationPermission` Client Actions. Action flow with permission check: ``` Start → CheckCameraPermission → If CheckCameraPermission.PermissionStatus = "granted" [True] → TakePicture [False] → RequestCameraPermission → If RequestCameraPermission.PermissionStatus = "granted" [True] → TakePicture [False] → Show message explaining permission is needed → End ``` For iOS, once a user denies permission the system does not re-prompt — you must direct them to Settings. Detect this with Error.Code from TakePicture and show a link.

1/* Permission check pattern — Camera */
2/* Available in Camera Plugin: CheckCameraPermission, RequestCameraPermission */
3
4CheckCameraPermission() output:
5  PermissionStatus: Text
6  /* Values: "granted", "denied", "prompt" (not yet asked) */
7
8/* Full permission-aware camera capture flow */
9Start
10→ CheckCameraPermission
11→ Switch on CheckCameraPermission.PermissionStatus
12     Case "granted":
13       → TakePicture → [handle result]
14     Case "prompt":
15       → RequestCameraPermission
16       → If RequestCameraPermission.PermissionStatus = "granted"
17            [True]  → TakePicture → [handle result]
18            [False] → Assign CameraError = "Camera permission denied"
19     Case "denied":
20       → Assign CameraError = "Please enable camera access in device Settings"
21→ End
22
23/* iOS — open app settings for permission re-grant */
24/* JavaScript node: */
25if (cordova && cordova.plugins && cordova.plugins.diagnostic) {
26    cordova.plugins.diagnostic.switchToSettings();
27}

Push notifications require: (1) a Firebase project with FCM configured, (2) the OutSystems Push Notifications Plugin from Forge, (3) Firebase configuration files added to your app build. **Step A — Firebase setup:** 1. Go to console.firebase.google.com → Create project 2. Add Android app → enter your app package name (from Service Studio → app properties → Package Name) → download `google-services.json` 3. Add iOS app → enter Bundle ID → download `GoogleService-Info.plist` **Step B — Install plugin:** Search Forge for **OutSystems Firebase Cloud Messaging Plugin** (or **OneSignal Plugin** as a simpler alternative) → Install. **Step C — Add config files to app:** In Service Studio → Interface tab → Resources → Add Resource: - Add `google-services.json` (Deploy Action: Copy to App Resources) - Add `GoogleService-Info.plist` (Deploy Action: Copy to App Resources) **Step D — Request push permission and get device token:**

1/* Push Notifications Plugin — register and get token */
2/* After installing FCM Plugin and adding dependency */
3
4/* Client Action: RegisterForPushNotifications */
5/* Call on app start in OnApplicationReady */
6
7Start
8→ RegisterDevice
9     /* FCM Plugin action: registers with FCM and returns token */
10→ If RegisterDevice.Success
11   [True]
12   → SaveDeviceToken (Server Action)
13        /* Save RegisterDevice.DeviceToken to PushToken entity */
14        /* Associate with current UserId: GetUserId() */
15        UserId      = GetUserId()
16        Token       = RegisterDevice.DeviceToken
17        Platform    = GetDevicePlatform()   /* "Android" or "iOS" */
18        UpdatedOn   = CurrDateTime()
19   [False]
20   → Log error (FeedbackMessage or Logger)
21→ End
22
23/* Server Action: SendPushNotification */
24/* Called from Timer or Server Action when notification needed */
25/* Uses FCM API via REST — Consume REST API in Logic tab */
26
27/* FCM v1 API call */
28/* POST https://fcm.googleapis.com/v1/projects/{projectId}/messages:send */
29/* Body: */
30{
31  "message": {
32    "token": "<DeviceToken>",
33    "notification": {
34      "title": "Order #123 Shipped",
35      "body": "Your order has been dispatched"
36    }
37  }
38}

After adding Forge plugins and configuration files, you must trigger a new MABS build to compile the native app with the new plugins included. **In Service Studio:** Click **1-Click Publish** (top center). After publishing, go to your app in the browser → click **Generate Android App** or **Generate iOS App** button → MABS builds the native package (APK/IPA). **Alternatively:** In **Service Center** → Factory → Applications → [your app] → Mobile → Generate → select platform → Submit. MABS build times: 5-15 minutes typically. Monitor progress in Service Center → Factory → Applications → your app → Mobile Versions. **Test:** Download and install the generated APK on an Android device (or use TestFlight for iOS). Open the app → test camera, GPS, and push notification flows. **Debug crashes:** If the app crashes on device, check Service Center → Monitoring → Error Logs → filter by application name for JavaScript and native errors.