Enterprise SaaS and ERP

The SaaS and ERP connectors speak each vendor’s REST or OData API directly. They are not equally complete, so each section below says exactly what is built.

Summary

For a type with no live probe, Test returns success: true with live_check_performed: false, which means the configuration was saved and nothing was verified. See Connections and credentials.

All HTTP-based connectors here dial through FACE’s hardened HTTP client. It uses no proxy, applies the address policy, and follows at most 5 redirects, all to the same host. A redirect to a different host is refused, so a credential never travels to a host the connection did not name.

SAP (OData / CSDL)

SAP connections describe an SAP system through SAPConnectionConfig (system_id, client, username, password, host, system_number). Those are RFC and SAP GUI destination parameters. OData discovery is driven by connection properties:

Credentials: username (setting or credential), and password (also api_key, token or secret) from the credential bundle. Internal addresses are allowed by default, because SAP systems usually live on private networks.

• Explore. One GET of the service’s $metadata, capped at 16 MiB.
  • Entity sets become datasets of kind entityset, qualified by the CSDL namespace.
  • Properties keep their document order and the service’s own type spelling (for example Edm.Decimal(13,3)).
  • Literal units come from Measures.Unit / ISOCurrency, and PII flags from PersonalData.IsPotentiallyPersonal.
  • Validation.AllowedValues becomes a vocabulary (up to 128 values). It is always reported as incomplete, because CSDL does not enforce it.
  • Nullability is reported only where the document states it.
  • No row counts are requested.
• Test. There is no live probe. Explore is the reachability check.
• Extraction. Not built yet. A fetch returns an error saying that the OData entity-set reader is not built and that the DDIC path needs the NetWeaver RFC SDK.

Salesforce

• Test posts the token request to the login host. A success means the credentials were accepted. Discovery and queries then dial the instance_url that the token response names.
• Extraction runs one SOQL statement, either the query you pass or the connection’s soql property. The connector does not choose objects for you. It follows nextRecordsUrl on the same host only.
  • Rows: default 5,000, at most 50,000.
  • Paging: at most 200 pages within a 3-minute budget.
  • A response that contradicts itself (done with a next page, or not done without one) is refused rather than returned short.
• Explore reads the org’s version list, then Describe Global, then a describe per object:
  • Up to 200 objects get column detail. The rest are listed without columns, and the reason says how many.
  • Picklists become vocabularies (up to 512 values). A vocabulary is marked complete only when the org flags the picklist as restricted.
  • Lookup targets appear in the declared type as reference(Account).
  • No row counts are requested, to protect your metered API allocation.

Guidewire

• Test calls /rest/apis and requires a non-empty API list.
• Extraction reads one resource (the query or resource) inside the base_url path. A route that escapes the base path is refused.
  • Page size: 200 by default, 500 maximum.
  • Rows: 5,000 by default, 50,000 maximum.
  • Paging: at most 200 pages within 3 minutes. links.next is followed on the same host only.
  • A 200 response without Guidewire’s data envelope is refused rather than read as empty.
• Explore enumerates /rest/apis, the per-API OpenAPI documents and the typelists. Typelist vocabularies are marked complete when the codes served match the count the index declares.
• The connector speaks HTTP Basic, which is what self-managed installations use.

ServiceNow

ServiceNow settings are read from connection properties: systemUrl (the instance URL). The credentials are username and password (HTTP Basic). Internal addresses are refused by default.

• Extraction reads the Table API tables syslog, sysevent and sys_audit, with an 8 MiB cap per response.
• Test requests the first of those tables.
• Explore returns supported=false. The ServiceNow dictionary tables are not read yet.

Dynamics 365, HubSpot, SharePoint

These types resolve and their settings are validated, but no call is made to a live API:

For each of these, Test reports live_check_performed: false and Explore returns supported=false.

Google Workspace

Google Workspace is read only during a fetch, through three connection types. These types are not in the connector registry, so Test reports Unknown connection type for them and Explore is not available.

Credentials: google_service_account_json. Without it, the instance-wide Google integration configured in Settings is used. The type is matched case-insensitively but otherwise exactly (google_sheets, not Google Sheets).