Overview

ProBeya Pharma Connectors provide bidirectional data integration with enterprise systems commonly used in pharmaceutical manufacturing and quality management. Connectors synchronize data between ProBeya and your on-premise or cloud-hosted enterprise systems, eliminating manual data entry and ensuring consistency across platforms.

Supported Systems

ConnectorSystemDirectionTypical Data
SAP PMSAP Plant MaintenanceBidirectionalWork orders, maintenance notifications, equipment master
TrackWiseHoneywell TrackWiseInboundDeviations, CAPAs, change controls, complaints
EnnovEnnov DMS/QMSInboundDocument metadata, controlled document status, audit findings
CoswinSiveco CoswinBidirectionalMaintenance tasks, spare parts, equipment history
SAP ECC RFCSAP ECC via RFCInboundMaterial master, batch records, production orders

Connector Lifecycle

Each connector follows a defined operational lifecycle:

inactive → active → error (recoverable)
    ↑                    │
    └────────────────────┘
  • Inactive — newly created, not yet syncing. Configuration can be modified freely.
  • Active — connected and syncing on schedule. Data flows according to the sync configuration.
  • Error — a sync failure occurred. The connector pauses syncing until an admin investigates and resolves the issue.

Setting Up a Connector

1

Open Connector Settings

Navigate to Settings > Connectors in your organization admin panel.

2

Create New Connector

Click New Connector and select the target system type (SAP PM, TrackWise, Ennov, Coswin, or SAP ECC RFC).

3

Name the Connector

Enter a descriptive name that identifies both the system and location, e.g., “SAP PM - Brussels Manufacturing Site” or “TrackWise - Global Quality”.

4

Configure Connection

Enter the connection parameters for your enterprise system. These vary by connector type but typically include:

  • Host / URL — the system endpoint
  • Port — the connection port
  • Authentication — credentials or certificate references
  • System ID — for SAP systems, the SID and client number

Connection configuration must reference encrypted credentials stored in a secret manager. Never enter plaintext passwords — they will be rejected. Contact your IT team to provision credential references.

5

Configure Sync Settings

Define how data flows between systems:

  • Entity mappings — which ProBeya fields map to which enterprise system fields
  • Sync schedule — how often synchronization runs (e.g., every 15 minutes, hourly, daily)
  • Batch size — number of records per sync batch
  • Retry policy — how many times to retry a failed sync before marking the connector as errored
6

Save and Activate

Click Save to store the configuration in inactive state. When ready, click Activate to begin syncing.

Sync Operations

Sync Types

TypeDescription
FullSynchronizes all records from the source system. Use for initial data load or recovery.
IncrementalSynchronizes only records changed since the last successful sync. This is the default for scheduled syncs.
ManualAdmin-triggered one-time sync for testing or ad-hoc data refresh.

Sync Logs

Every sync operation is logged with:

FieldDescription
Sync IDUnique identifier for the sync run
TypeFull, incremental, or manual
StatusSuccess, partial, or failed
Records SyncedNumber of records processed
Started AtWhen the sync began
Finished AtWhen the sync completed
Error DetailsError message and stack trace (if failed)

View sync logs by clicking on a connector and selecting the Sync History tab.

Managing Connectors

The connector list supports filtering by:

  • Connector type — show only SAP PM connectors, for example
  • Status — filter by active, inactive, or error state

Results are paginated (20 per page by default) and sorted by creation date.

  • Edit — click on a connector to modify its name, connection configuration, or sync settings. Changes take effect on the next sync cycle.
  • Deactivate — set the status to Inactive to pause syncing without deleting the configuration.
  • Delete — permanently remove a connector and all its sync logs. Previously synced data remains in your boards.

Security

  • All connection configurations are stored as encrypted JSONB in the database.
  • Credential fields are never returned in API responses — they are redacted before transmission.
  • Only organization owners and admins can create, modify, or delete connectors.
  • All connector operations are scoped to the current organization for strict multi-tenant isolation.
  • Sync operations run server-side with no client-side exposure of enterprise system credentials.

Troubleshooting

IssueResolution
Connector stuck in “error” stateCheck the latest sync log for error details. Common causes: network timeout, expired credentials, schema change in the source system. Fix the issue and click Retry.
Partial sync with missing recordsReview the sync log for skipped records. Partial syncs occur when some records fail validation. Fix the source data and run a manual full sync.
Slow sync performanceReduce the batch size in sync settings. For large initial loads, schedule the full sync during off-hours.