Compare the integration’s behaviour, not the number of connector logos. Public documentation itself shows why the word “integration” needs qualification. Hyperproof distinguishes task, messaging, cloud-storage and evidence-collection mechanisms; Archer distinguishes API, scheduled-feed and one-time-import approaches. (help.hyperproof.app)
Use this integration requirements checklist for every shortlisted configuration:
| Criterion | Question for the supplier | Acceptance evidence to request |
|---|---|---|
| Supported objects | Which records and fields are actually supported? | A field-level mapping for your source and destination |
| Direction | Read-only, write-back or bidirectional? | Demonstrated changes in every contracted direction |
| Scope | Which entities, accounts, environments and periods are included? | Reconciliation against a known source population |
| Identity and access | Whose credentials run the integration? | Permission review, ownership and credential-rotation procedure |
| Freshness | How often does it run, and what does a missed run look like? | Last-success timestamp and a visible failure state |
| Failure recovery | What happens after a partial load or outage? | Retry, alerting and duplicate-prevention demonstration |
| Evidence meaning | Is the result a live link, snapshot, report or assessment? | A documented interpretation and retention rule |
| Maintenance | Who responds to an upstream API or schema change? | Named owner, support boundary and priced responsibility |
What should the failed-integration demonstration show?
Deliberately interrupt an authorised test connection, change a sample field and remove access to one synthetic record. Require the supplier to show:
- What failed and which records were affected.
- Who was notified and when.
- Whether the dashboard distinguishes stale evidence from current evidence.
- How recovery avoids missing or duplicate records.
- How the failure and recovery remain visible to an assessor.
Also test export permissions separately from ordinary viewing permissions. IBM’s OpenPages 9.1 documentation states that its privileged Data Export permission can export data regardless of normal role-based security and other access restrictions. That is a specific documented administrative privilege—not an allegation of a vulnerability, and not a statement about every export mechanism or release. Ask for equivalent clarity from every bidder. (ibm.com)
Sources cited on this page
- help.hyperproof.app ↗help.hyperproof.app
- ibm.com ↗www.ibm.com