RapidValueDocs RapidValue.eu
Docs/More

Documentation status

This portal was checked against RapidValue product main at commit 269e577 on 12 October 2026. The glossary keeps an older date because only its new entries were checked. JML flows and lifecycle coupling were checked later, against commit 10cd2dd on 15 October 2026, and describe the main employment and the pre-hire hold. Eight pages were checked against commit b772025 on 16 October 2026 for the changes merged since 13 October; the changelog names them. Fourteen pages were checked against commit fe8d042 on 19 October 2026 for the changes merged since 16 October. Four pages were checked against commit bae3f6f on 20 October 2026 for the changes merged on 19 October. Five pages on AI agents were checked against commit 7a73b1b on 21 October 2026. Ten pages were checked against commits e5bdb69 (21 October) and 6764c4e (22 October 2026) for the other changes merged on 20 and 21 October. Seven pages were checked against commit 9291ed6 on 23 October 2026 for the changes merged on 22 October; the changelog names them. Thirty-one pages were checked against commit 43bd4359 on 26 October 2026 for the changes merged from 23 to 26 October; the changelog names them. Fourteen pages and the new workflows page were checked against commit 5a6c97e on 27 October 2026 for the changes merged on 26 October. Thirteen pages were checked against commit 3681281 on 28 October 2026 for the changes merged on 27 October, and eight pages against commit 954be1b on 29 October 2026 for the changes merged on 28 October, and four pages against commit 69f0272 on 30 October 2026 for the changes merged on 29 October. Fifteen pages were checked against commit 929542f on 2 November 2026 for the changes merged from 30 October to 1 November; the changelog names them. Two pages were checked against commit c0d8a38 on 3 November 2026 for the changes merged on 2 November. Five pages were checked against commit 67b3417 on 4 November 2026 for the changes merged on 3 November. Four pages were checked against commit 896b5a0 on 5 November 2026 for the changes merged on 4 November. Seven pages were checked against commit ff9b062 on 6 November 2026 for the changes merged on 5 November. Partner access and the partner console are on main but off until the partner sign-in is configured in production, so they are not described yet. The runtime gateway in front of other systems is accepted on staging only and closed in production; deciding every agent call describes it as such. The agents-first onboarding path and the Entra "at the customer" setup option are on main but not yet complete end to end, so they are not described yet. The durable recon queue is on main but off by default, so it is not described. The BI export feed is on main as an API without a console screen, and its Power BI acceptance is still open, so it is not described yet. Before that, the baseline was commit 5440d975 on 11 September 2026. A page's Last verified date records the most recent claim-level review; its owner names the team responsible for the next one.

The hosting direction is a separate architecture decision verified on 12 September 2026. It changes the intended provider order, not the product-code baseline above, and the Scaleway production gate remains open.

What verification means

A verification pass checks public product claims against shipped code, tests, current operational rules and named limitations. It does not mean that every customer configuration enables every capability.

The build refuses pages without an ISO verification date and owner. The documentation changelog records portal changes; product release notes record selected customer-visible changes.

Freshness boundary

The product and public documentation live in separate repositories. A new product commit is not automatically a new public claim. Material changes to behaviour, permissions, limits, supported connectors or deployment guarantees require a documentation review and baseline update.

Older dates remain visible intentionally. They are a signal to review the page, not a reason for the generator to invent a newer date.

Feedback and search gaps

Page responses and searches with zero results are sent to a first-party /api/docs-events endpoint. Events contain the event type, page, selected response or search text, and timestamp. They do not add a user identifier, tenant identifier, cookie or secret.

Free-text queries can still contain information a reader types. Do not enter credentials, personal data or customer secrets into documentation search.

Current known boundaries

  • The API reference covers the governed machine gateway, not every signed-in UI endpoint.
  • Product release notes are selected material changes, not a raw commit log.
  • Connector write support remains capability- and configuration-dependent.
  • Production runs on Scaleway Amsterdam (since 24 September 2026), but no customer is live and it is not yet a generally available, service-level-backed platform. Track what is and is not yet in place in Hosting, regions and deployment status.
  • Customer-managed cloud and on-premises control planes remain future enterprise delivery models, not generally available standard features.
  • Deferred functionality stays named in the relevant page and in What we don't claim.
Did this answer your question?One click records the page; add detail by email if something is missing.

Try “tenant isolation”, “role mining” or “Entra”.