Person object
The MXPERSON object structure allows for bidirectional synchronization of person information, including phone, email, and SMS data.
Purpose
This object structure supports synchronizing individual person data. It does not support updating availability information for a person record. The object structure also supports status changes.
Outbound Integration Processing
The following table shows the predefined values used in outbound integration processing.
Predefined integration components | Value and description |
---|---|
Object Structure definition class functionality | None |
Publish Channel | MXPERSONInterface |
Processing Rules | None |
Integration Controls | None |
Inbound Integration Processing
The following table shows the preconfigured values used in inbound integration processing.
Predefined integration components | Value and description |
---|---|
Object Structure processing class functionality | MaxPersonProcess - Requires that data for all child objects (PHONE, EMAIL, SMS) must be provided with every person update. Due to a lack of a unique key on these objects, the logic always deletes all of the child objects and adds them again. If a person has three email records in the system and a person message is received with two email records, the email record not included in the person message will be deleted. The object structure supports status changes. |
Enterprise Service | MXPERSONInterface |
Processing Rules | None |
Integration Controls | None |