Using Haploo Register ()
This function accepts a properly formed JSON Data Object. The syntax is very specific. How you deliver this registration payload to the
HaplooRegister() function is completely up to you. For example, in a multi-tenant environment, you may wish to dynamically fetch and resolve this JSON Object to be
specific to a customer or region. This registration definition creates the highest level sync domain for your clients or apps.
Main JSON Payload Keys
| Key Name | Key Description | Data Type | Notes |
| API_Endpoint | The url subdomain for Haploo Cloud | String | Legacy Param: Moving towards multi-tenant. Use Tenant_EndPoint |
| API_Token | Assigned Token for your sync domain | String | Legacy Key: Moving toward multi-tenant, use Tenant_ID |
| Client_Secret | Assigned Password for authorizing syncs | String | Legacy Key: Moving toward multi-tenant, use Tenant_Secret |
| Provider_ID | the associated billing account / account admin | String | |
| Tenant_EndPoint | The url subdomain for Haploo Cloud | String | Assigned to you via your Haploo Cloud Login Portal |
| Tenant_ID | Assigned Token for your sync domain | String | Same as API Token, but generated for each tenant or sync domain |
| Tenant_Label | A friendly label to describe your tenant | String | |
| Tenant_Secret | Assigned Password for authorizing syncs | String | |
| Solution_Name | A friendly name for your deployed fm solution | String | Examples: Inventory System, Audit Tool, Purchasing Master. Simply, the name of your app |
| API_Version | Determines if Schema needs to be fluid / dynamic | Static Dynamic | Uses a keyword. If your solution does not need to resolve schema differences at runtime, use **Static**, otherwise use **Dynamic**. Please note dynamic is more compute intensive |
| PushOption | Enables push messaging for user / app | Enabled Disabled | We will register your iOS device's push token with Haploo Messaging Services. To trigger a push to actually send will be done within the SyncBy() Functions. |
| PushUserTags | An array of words describing the user / device | Array / List | Keep these words simple and alpha numeric, no special chars or spaces. |
| SyncTriggers | Toggles different sync modes | JSON Object | Control the behavior of specific sync related triggers. |
| ExcludePrefix | Prevents certain fields from syncing based upon field name prefix pattern matching | String | For example, using __ double underscore my indicate a private field and posting of such values should be ignored. |
| ExcludeGlobal | Prevents global fields from posting | True False | Global fields are typically reserved for user specific sessions and syncing them across multiple device may produce unwanted results. |
| PullPolicy | Provides a data pulling query to limit what records the device is allowed to access from the Haploo Cloud Servers. | JSON Object | This pull will further break apart the sync domain into smaller sections. It will allow syncing to be more efficient for your users / apps. It can control what data is pulled for each table in your solution. |
SyncTriggers JSON OBJECT Syntax