HCP OneLink Integration – Troubleshooting Validation & Test Guide



Purpose: Validate that the troubleshooting instructions are complete, accurate, and usableAudience: Engineering, OpsWhen to run: Quarterly, onboarding, or after infra changes


1. Prerequisites

  • Access to CadenceFrontline
  • Access to OneLink UI
  • Access to Cadence UI
  • CURL or Postman installed


2. Test Scenario A — Happy Path

    Identify known Cvent Event ID
    Verify Ensemble exists in Cadence
    Confirm correct contract status in OneLink
    Manually run integration
    Confirm status updates in Cadence
Check Mark Button Pass if Cadence matches OneLink


3. Test Scenario B — Email Mismatch

    Modify OneLink HCP email (or use known mismatch)
    Run integration
    Confirm contract does not update
    Fix email
    Re-run integration
Check Mark Button Pass if second run resolves issue


4. Test Scenario C — Webhook Only

    Trigger webhook payload manually
    Confirm no immediate change
    Run import job
    Confirm update occurs
Check Mark Button Pass if behavior matches documentation


5. Test Scenario D — Failure Handling

    Force invalid OneLink response (if safe)
    Run integration
    Confirm:
  • Error logged
  • Email notification sent
  • No partial corruption


6. Validation Checklist

  • Can operator locate correct server?
  • Can logs be found without dev help?
  • Can job be run manually?
  • Can failure be diagnosed?
  • Can escalation include useful data?
If any box is unchecked → update Docs 1 or 2


7. Sign-Off

  • Last validated by: __________
  • Date: __________
  • Gaps found: __________
  • Actions taken: __________