XDMS
Summary
Allows you to sync entities between XDMS and HyperPortal
There are 2 directions
- HyperPortal -> XDMS
- XDMS -> HyperPortal
HyperPortal -> XDMS
CMS (custom-data), after applying changes, publishes an action message to AWS SNS (CustomDataSNSTopic) the "xdms-CustomDataEventsQueue" queue is listening to the SNS service and passes events to lambda function "xdms-CmsContactUpsertProcessorFunction"
Depending on the settings, the function checks if the event matches the conditions and sends a POST request to the URL specified in the settings
Contact module
Required fields:
- NMcontact
- CDrel - Relationship type
- K - Customer
- ...
- NRrel - Relationship id
Customer module
Required fields:
- CDcust
- NMcust
Where to get XDMS Host
XPower -> Properties -> find XDMS-SERVER property
How to enable rest connector
Contact XDMS support
XDMS -> HyperPortal
XDMS keeps exporting data to AWS S3 (xdms-imports-s3bucket) each folder corresponds to tenantId
Сron starts once a day and starts importing data
XDMS Order Module
Request 7-8 in this collection.
- One way integration ( only push to XDMS, no imports)
- Works only on creation event (no updates)
- Required fields: • NRrel - can be customer id (NRcust) or Vehicle id (NRmach) • CDpr - aways use "W" or "O1" (not 01) • CDrel - always use "K" • INln - Order line text string. Max - 60 char. If more, will be split to the next order line.
- Other fields: nrcust-inv - Relation who will pay for the order ( if left empty, customer from NRrel will be set in XDMS automatically ) (haven't tested what happens if nrcust-inv and NRrel is a Vehicle. nrcustdlv - Relation who will receive the order. Behaves the same way as nrcust-inv
- Extra fields - ???? (not tested yet) { "NRord": 10, "NMfld": "xtra", "VAfld": "", "CDfld": "character", "CDprm": "input" }
Customer that is pushed as NRrel cannot have CDcust=00 (will not pass XDMS validation). Must be at leas CDcust=10