Person/user object

The MXPERUSER object structure allows for bidirectional synchronization of person/user information.This object structure 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 MXPERUSERInterface
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 MaxPersonUserProcess - Processing is required to save the person data prior to saving of the user data. This object structure supports status changes.
Enterprise Service MXPERSUSERnterface
Processing Rules None
Integration Controls None