OptimonCoreSync Studio
IE
CS-API-006 · API Application APIs, event streams and SaaS intake · 48 of 192

Onboard a supplier or partner event feed

Partner Integration Lead · Trigger: An external organization begins sharing operational data.

Simulated fixture data. Every record, receipt and timeline entry on this screen is demonstration material. It is never production evidence.

Acceptance

2 of 3 steps satisfied

Contract tests will preserve issuer identity and reject unauthorized content or destinations.

Run the remaining steps below. The result is read back from record state — nothing here is a toast.

Normal path

An application API or event stream is acquired with a pinned contract and a backlog inside budget.
Step 1. Test acquisition, pagination and checkpoint recovery.
satisfied
Operates onAPPS-021ERP order feed 21Application source· OPTIMON-IND / Raigarh Melt Shop
acquisitionhealthycontractcurrentbacklogwithin budget
Moves the record and writes evidence. Permission: test.
Acceptance for this step: acquisition = healthy
Step 2. Pin the contract version the acquisition depends on.
not yet satisfied
Operates onAPPS-028LIMS results 28Application source· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
acquisitionfailedcontractpendingbacklogwithin budget
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: contract = current
Step 3. Drain the backlog back inside its budget.
satisfied
Operates onAPPS-007MES batch events 7Application source· OPTIMON-IND / Halol Packaging Line
acquisitionhealthycontractcurrentbacklogwithin budget
Moves the record and writes evidence. Permission: remediate.
Acceptance for this step: backlog = within budget

Exception path

Partner identifiers colliding with tenant identifiers will remain scoped and unresolved until mapped.
Alternate path. The provider changes shape or rate-limits: raise the incident against the acquisition stage.
not yet satisfied
Operates onINCI-021Delivery lag breach — Raigarh Melt ShopIncident· OPTIMON-IND / Raigarh Melt Shop
triageresolvedimpactdegradedremediationcomplete
Moves the record and writes evidence. Permission: remediate.
Acceptance for this step: triage = in review

Workflow as specified

CoreSync will register partner identity, contract, permitted content, retention and delivery expectations, then validate a conformance sample before admitting the feed.

Evidence written in this session

Nothing run yet in this session. Record state shown above may already satisfy steps from the seeded fixture history.

Journeys that include it

Not part of a composite journey; exercised through its family views.