Connect by JBRH Open Connect

Features for one business

A business can ask JBRH for a feature only it needs. JBRH scopes and approves the request, and switches it on only after it has proved, on the live database, that the change reaches that business alone. It then applies to that workspace only and can be rolled back. A customer's request never becomes code or a deployment by itself.

Status
Available What this means
Audience
both
In the app
/api/v1/feedback/custom/requests
Last verified
Product version
6.3.2

The request's path#

  1. Ask (a workspace admin)
  2. Scope (JBRH)
  3. Approve (commercial and deployment)
  4. Verify isolation
  5. Active for this workspace
  6. Customer review
  7. Rollback or reject when needed

Scoping records the key, the mechanism, its values, feasibility, privacy, cost and dependencies. A workspace admin can ask, review or withdraw. JBRH scopes, approves, activates, rolls back or rejects.

What a custom feature can be#

Only two mechanisms exist: a feature flag, or a configuration value that shared code already reads. A custom feature is never new source code written for one customer, so it cannot fork the product or bypass the shared rules on security and isolation.

Shared code asks whether the feature is on for this workspace and reads its configuration. Plans and entitlements are consulted too, so a custom feature answers for its own workspace and no other (offerings, plans and trials).

Where you find it#

A workspace admin asks from the Feedback area of any Connect app. It then shows its state as it moves: scoped, approved, active, rolled back or rejected. JBRH works the request from its own desk, so it never reaches anyone outside JBRH and your workspace.

Approval has two halves, commercial and deployment, and both are recorded. It can be withdrawn by the business at any point before it is active, and an active feature can be reviewed by the business so JBRH knows whether it does what was asked.

Safety rules#

  • Activation happens only after the isolation check passes against the live database.
  • Rollback takes effect on the next read. Nothing waits for a release.
  • Every step is audited, and the customer can see its state.
  • An ask is only an ask: its words are never executed, compiled or deployed.

Questions#

Can another business see or use our custom feature?

No. It is enabled for one workspace, and activation requires proof that it reaches no other.

Is there a cost for a custom feature?

Cost is one of the things recorded when JBRH scopes the request, before anything is approved, so you know it before you decide. These pages state no price: the owner sets prices, and the scope for your feature is where yours appears.

What if the feature causes a problem?

JBRH rolls it back, and the change takes effect on the next read. Your workspace returns to the shared behaviour.