Workspace Settings
Workspace-level configuration: identity, SAP RFC connection, retry, buffer TTL, stalled-document threshold, and notifications.
Workspace Settings
Open via the Workspace menu in the sidebar (or the workspace switcher) and pick Edit settings. Changes apply to newly received documents — documents already in the retry queue keep the parameters they were dispatched with.
General
| Field | Notes |
|---|---|
| Workspace name | Display name in the switcher + dashboard. Editable any time, no functional impact. |
| Endpoint URL | Read-only. Built from your deployment hostname + the workspace slug. Use the hostname as HTTP Server in OAC0 and the path as HTTP Script. |
https://filerelay.acme.internal/ws/your-workspace-slug/ContentServer
The hostname is set when the FileRelay deployment is provisioned — your admin or the FileRelay team controls it.
SAP RFC connection
Optional. Used by Data Enrichment as a fallback connection when an individual enricher has no credentials of its own. Each enricher in the RFC Console library can override these per-function.
| Field | Example |
|---|---|
| Host | sap-prod.corp.com |
| SysNr | 00 |
| Client | 100 |
| User | FILERELAY_RFC (dialog or communication user) |
| Password | •••••••• (encrypted at rest; blank on edit = preserve existing) |
| Lang | EN |
Without RFC configured, ingest still works — only enrichment is unavailable. See Data Enrichment Overview.
Retry
Applies to all delivery jobs in the workspace. Enrichment jobs have their own independent retry budget and are not governed by these knobs.
| Setting | Default | What it does |
|---|---|---|
| Max retries | 3 |
Maximum re-delivery attempts after the first failure. 0 disables retries. |
| Retry backoff | linear |
linear = fixed 30 s gap between retries. exponential = 30 s, 60 s, 90 s, … |
Pending threshold
How long a document may sit in pending before it is flagged as stalled on the dashboard and (when notifications are on) raises an alert.
| Setting | Default | What it does |
|---|---|---|
| Pending threshold | None |
None disables the threshold. Otherwise a duration in minutes — 30 is a sensible starting point. |
Buffer TTL
How long the encrypted document body is retained on the buffer disk after the delivery is terminal (success or final failure). The bytes are removed by the PurgeDocumentBuffer job once this window elapses.
| Setting | Default | What it does |
|---|---|---|
| Buffer TTL | Instant |
Instant deletes the bytes as soon as the delivery row goes terminal. Otherwise a duration in minutes — useful when you may want to manually re-deliver a failed document. |
The metadata row in documents is unaffected by the TTL — only the bytes are purged.
Notifications
Where to send alerts (currently: stalled-document and final-delivery-failure notices).
| Mode | Behaviour |
|---|---|
| None (default) | Silent. The dashboard still shows the failures. |
| Workspace owner receives a digest mail when the thresholds above trigger. |
Danger zone
At the bottom of the settings panel:
- Delete workspace — permanently removes the workspace and everything inside it (repositories, destinations, connections, documents, memberships, enrichers). Irreversible; requires confirmation.