Expo Harvester - Activity Write-back to iMIS

Overview

For a specific eventID, an activity record is sent to iMIS based on a trigger.

Triggers

The writeback will be triggered based on the following actions:

• if PaymentMechanism=“Online Credit Card” and PaymentStatus=“Charged”
  • automatic when credit card payment is made
• if PaymentMechanism=“Online Credit Card” and PaymentStatus=“Refund”
  • processed administratively on the backend
• if PaymentMechanism=“E-Check” and PaymentStatus=“Charged”
  • automatic when an e-check (aka ACH) payment is made
  • only available for authorize.net payment processor and if this feature is enabled
• if PaymentMechanism=“E-Check” and PaymentStatus=“Refund”
  • processed administratively on the backend
  • only available for authorize.net payment processor and if this feature is enabled
• if PaymentMechanism=“Check” and PaymentStatus=“Cashed”
  • processed administratively on the backend
• if PaymentMechanism=“Check” and PaymentStatus=“Refund”
  • processed administratively on the backend
• if PaymentMechanism=“Wire Transfer” and PaymentStatus=“Cashed”
  • processed administratively on the backend
• if PaymentMechanism=“Wire Transfer” and PaymentStatus=“Refund”
  • processed administratively 0n the backend
• if PaymentMechanism=“Purchase Order” and PaymentStatus=“Cashed”
  • processed administratively on the backend
• if PaymentMechanism=“Purchase Order” and PaymentStatus=“Refund”
  • processed administratively on the backend

Field Mapping

Client to provide spreadsheet with the following columns:

1. Cadmium Field: Select from the list of available fields below
2. Third-Party Field: Corresponding field name to map to (examples in the chart below are from an integration we do with a specific iMIS reseller)
3. Required (Yes/No): Indicate all fields that are required by the third-party

Requirements

Customer to provide the following:

• Technical documentation from third-party vendor 
• Endpoint
• Field mapping spreadsheet noted above
• Values for any hardcoded fields

Acceptance Testing

Note, Cadmium cannot test this type of integration. Testing is the sole responsibility of the client.

• Log in as an exhibitor
• Make a test booth purchase to trigger the activity to be sent
• Confirm the activity is created in iMIS and includes all the information you expect to see
• If you find any issues, please let your integration project manager know