Using Open API Adapter
Volt MX Go doesn't support the use of the Open API Adapter in the Foundry Integration Services to connect to Domino via Domino REST API.
Using helm charts on supported Kubernetes platform
When using helm charts on a supported Kubernetes platform, you must run the
kubectl config set-context --current --namespace=mxgo command in your Ubuntu terminal session to set the current namespace context after restarting Windows or Rancher Desktop. If you don't run the command after restarting Windows or Rancher Desktop, your kubectl commands might fail.
- Foundry only allows "letters" (A-Z and a-z) as the first characters in names. For example,
$files, included in Domino field names, aren't supported. As a workaround, Domino Adapter encodes the problematic characters, for example
- Foundry restricts the length of names, such as field names, to be shorter than the name length supported in Domino.
As Domino REST API and Foundry administrators can redefine field data types, it can cause data conversion issues as they can redefine a field in Domino differently. For example, a Domino REST API administrator can indicate a date field in Domino as a boolean, while a Foundry administrator can indicate the same date field as a string. This causes conversion issues. As not all possible conversion points have been tested, data conversion isn't yet supported.
Verb mapping isn't supported for binary verbs in the Foundry Console.
Deleting offline documents
If a document is hard deleted in the Domino DB by another app, the devices using the offline sync DB won't know about this deletion, and any subsequent sync calls won't remove the document from the sync DB. This results in a stranded document on the device, but not in the back end.
To resolve stranded documents in an offline app, use the
clearOfflineData function provided by the Volt MX SDK in Iris. The function clears out the device's sync DB at the level you choose (app level, object service level, object level) so that syncing the app with the back end fully syncs all data without sending any hard deleted documents and allows the device's sync DB to match up with what's in the back end.
Offline-enabled apps use soft delete to remove deleted documents from a device's sync DB. Add the
IsDeleted property to the Domino REST API schema to enable soft delete. The property will contain the value deleted when the document has been soft deleted and removed entirely from the device’s sync DB upon a sync with the DB.
Disabling document deletion on the Domino DB if using it with an offline-enabled app combined with an agent script on the Domino REST API, which periodically clears soft-deleted documents, enforces soft delete on the Domino DB. These keep the soft-deleted documents long enough for the user devices to sync before pruning the deleted documents and ensure that the Domino DB doesn't have too many soft-deleted documents.
- Supports only Foundry Object services.
- Domino object services in Foundry are only usable by authenticated app users. You must have a valid Domino REST API token for all Domino REST API calls. Customers requiring access to Domino object services as unauthenticated users may be able to implement a Foundry pre-processor to obtain valid Domino REST API tokens and inject Authorization headers in each request.