SyncApp Settings and Configuration Deep Dive
Why This Matters
Understanding exactly what gets stored when a SyncApp is created — and the sequence in which it happens — demystifies the entire provisioning process. This is the 'under the hood' view that makes you a confident SyncApp debugger.
What You'll Learn
- What the settings/locations section of WAM stores: PMS name, last connected PMS, PMS credentials
- The step-by-step SyncApp creation sequence: validate credentials → create source ID + password → create settings file → spin up SyncApp process
- How PMS credentials differ per PMS type (e.g., InfiniteVT uses Office ID; CloudNeeds uses Client ID; e-Clinic uses Client ID + URL + Office Group ID)
- How to add PMS settings manually using Darren Super Patch (settings tool)
- What the sync status view shows: entity counts, processing state, modified/added/deleted records per sync cycle
Watch Video
Lesson Summary
Creating a SyncApp follows four steps: (1) Validate PMS credentials. (2) Create a new source ID and password (the SyncApp credentials). (3) Store the PMS name and PMS credentials in the settings/locations area. (4) Use all of this configuration to spin up the SyncApp process. Every PMS requires different credential types — InfiniteVT uses Office ID, others use Client IDs, connection strings, or endpoint URLs. Darren Super Patch is the tool for manually adding or updating settings. The sync status view in WAM shows the current state of all entities being synced.