BlackOakAdmin

Settings registry

Typed operational settings, resolved most-specific-scope-first. Every change carries a reason and is recorded.

Resolve in scope
Leave blank for the global answer. More specific scopes win.
Keys (9)
KeyTypeEffectiveSourceDefaultPermitted scopesOn failure
checkout.reservation_ttl_seconds
How long checkout holds stock before release.
integer900Code default900global, environmentFails safe
scheduling.booking_hold_ttl_seconds
How long a held booking survives unconfirmed.
integer900Code default900global, environmentFails safe
scheduling.booking_horizon_days
Default furthest-out bookable day.
integer60Code default60global, environmentFails safe
scheduling.booking_lead_time_minutes
Default minimum notice before a booking.
integer0Code default0global, environmentFails safe
compliance.reminder_horizon_days
Licence-expiry look-ahead for the reminder sweep.
integer30Code default30global, environmentFails safe
compliance.metadata_max_length
Cap on stored compliance metadata length.
integer200Code default200global, environmentFails safe
worker.poll_interval_ms
Worker sweep cadence.
integer2000Code default2000global, environmentFails safe
integration.outbound_max_claim_attempts
Retry ceiling for outbound claims.
integer5Code default5global, environmentFails safe
integration.webhook_tolerance_seconds
Inbound webhook replay window.
integer300Code default300global, environmentFails safe
checkout.reservation_ttl_seconds
How long checkout holds stock before release.
Type
integer
Code default
900
Permitted range
30 to 86400
Clearing removes the value at the chosen scope, so the key resolves from the next scope out — or from its code default.
Change history (0)limit must not be less than 1,limit must be an integer number

How this step works

SIPOC
Who supplies this step, what it needs, what it does, what it produces, and who uses the result. Suppliers and customers are links — follow them to walk the workflow, including into the consumer and merchant apps.
SuppliersWhere the work comes from
InputsWhat this step needs to do its job
  • The catalogue of settings the system defines
  • Their current values and scope
  • Who may change each
ProcessWhat happens here, in order
  1. Show every operational setting, its type and where it applies
  2. Change a value within its allowed range
  3. Version the change so it can be dated and reversed
OutputsWhat this step produces
  • Published configuration values
How this step works