Skip to main content
Use the @bijection/connectors/sugarcrm entrypoint to declare SugarCRM resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Module records

pull: date_modified windows with a deleted=true phase, unconditional PUT

The following example matches configuration standard.
The function references identify application policy queries. Implement those policies in your application; the references alone grant no authority.

Configuration: standard

Case: sugarcrm/records/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: sugarcrm. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Commands
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Configuration: readOnly

Case: sugarcrm/records/pull/readOnly. Connection and resource configuration are declared by this exact case. Credential kind: sugarcrm. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. The connection holds a sugarcrm credential; setup endpoint is the REST base including its version, such as https://acme.sugarondemand.com/rest/v11_24/. Sugar takes its access token in an OAuth-Token header. The credential is a managed oauth_refresh envelope over the user’s refresh token whose protocol names that header; Sugar’s stock client is public (sugar, no secret):
Sugar keeps one session per user and platform; the refresh request sends no platform, and whether Sugar then renews under the platform the grant was issued for is unestablished. Sugar names no instance identity, so the connection is its own account namespace. records.pull reads <module>/filter with date_modified $gte, ordered date_modified:ASC,id:ASC, 100 rows by offset until next_offset is -1, re-asking from one second before the latest date_modified read. The pass then reads the same listing with deleted=true; a row whose deleted is true withdraws the record. Each finished pass carries the latest modification and deletion; the next starts five minutes before them. date_modified is kept as Sugar spells it, the version. update is an unconditional single-attempt PUT. Nothing here has run against SugarCRM or been qualified.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.