inflowDocsLearning path

Inflow Home

الدليل العربي للصفحة الرئيسية covers first-day use, Arabic/RTL, current feature availability and uncertain-change recovery. This program guide distinguishes the current Home routes from features that remain candidates; integrated qualification is still pending for the marked work.

Home is the standard landing surface for an admitted account that has no eligible configured group landing page. It is separate from Studio. An operator enables it explicitly; existing environments retain their previous landing behavior by default.

Sign in and find work

After signing in, a valid explicit destination or configured group landing still takes precedence. Home does not grant access to applications or tasks. When no business context is available, Home offers your account information, Get help and Sign out. Contact your administrator through your organization's usual support channel if you need access.

When the operator enables Home together with application-user access, a signed-in account with no usable configured App Shell landing opens Home even if another application is available. The /home route checks the current account again. Turning Home off preserves the previous landing behavior. A task opened from Home returns to its same-workspace Home Tasks URL and supported inbox filters; this does not bypass the task's current authorization. Home Tasks now reuses the existing task inbox only for a selected context that currently advertises the Tasks area. This source integration still needs the consolidated validation and runtime qualification.

Choose a workspace from the contexts currently admitted for your account. Tasks opens the existing My work inbox, with its assigned/available/completed views, filters, task forms and actions. Open a task normally; Back and Save and close return to that same Home inbox and its URL filters. Task actions still enforce current assignment and business permissions.

Applications lists currently admitted published application pages. Opening one uses its normal published route and rechecks access there. Current Studio source also includes All, Favorites and Recent filters plus favorite controls when the server admits personal preferences for the signed-in session. Other readable sessions can still open applications without personal controls. A favorite or recent entry never grants access, and this source slice has not passed consolidated release qualification. My requests is a section within Home Tasks. Social, Data Navigator, Business Starts, Home-wide search and the notification center do not have current Home user pages; their sections below describe candidate behavior only. Backend Social API/service source now exists, but it is default-off and unqualified and does not provide a Social screen. Ask [App] inside a published App Shell is separate from the built-in Home Chat candidate.

An intended published application may show its own Ask [App] chat when its publisher has enabled and configured the existing App Chat feature and you have current access to an approved source or action. Ask [App] is scoped to that application and is separate from Ask Inflow; opening Home or an application does not enable AI. Use citations to check the current source. Unsaved form values stay private; unless the app explicitly offers a sharing control, use the ordinary form instead of sending its draft. Review any proposed action and confirm it yourself; a draft alone does not change business data. The feature may be disabled or unavailable while the ordinary application remains usable. See the Ask [App] guide for end-user and publisher instructions.

Built-in Home Chat is a candidate, not a current Home feature. Current source contains no Home Chat setting, Home Chat endpoint or panel/launcher; the home-app-chat provider-purpose name alone does not enable Home Chat. Do not expect to chat from /home. This does not affect independently configured chat inside a published App Shell. See the Ask [App] guide for the published-app feature and the Home candidate status.

Social and notifications — candidate behavior

Availability: Social and the Home notification center are not current Home user pages. The Social backend route is present in source behind default-off gates; it has not been release-qualified, and there is no Studio Social page. The following is design guidance, not a live workflow or an instruction to change a runtime. Read the detailed Social guide with that boundary in mind.

The planned Social experience would show updates available to your current account. It would let you choose a workspace or group audience before posting and select eligible mentions privately. These controls are not available in Home today: the backend rejects non-empty mention lists and has no recipient selector or notification delivery. The source outbox records only a pending event intent, not a notice. The planned experience also covers supported images, comments, reactions, follows, saves, reports and moderation where authorized. Following would subscribe you to later edits and comments without granting access; followed-post notifications are not delivered by current Home source. Planned Share in Social actions from records, tasks, document previews, My Requests and published App Shells add private typed references to a post draft. Opening a reference would recheck access through its current canonical owner; a request link would open only the Home request summary for a current initiator or completed-task participant who also has current case visibility. A reference would not reveal protected business data or grant access. These are design descriptions, not current Home controls.

Home notification behavior remains planned, not available. The source does not contain a Home notification projection or delivery worker for mentions, followed-post updates, task assignments or request returns. A Social outbox row is a pending event intent, not evidence that a user received a notice. If these features are delivered later, task notices should open the ordinary task page and request notices the existing My Requests detail page, each with current access checks; personal read/dismiss must never complete business work. The home_social and task preference categories do not prove delivery. The proposed Notify the request initiator USER_TASK option and default-off inflow.home.notifications.request-returned.enabled producer remain unqualified; do not rely on them.

My requests opens a Home summary that checks your current relationship and case visibility again. It shows only the authorized request reference, title, status and timestamps. When a current open task is assigned to you, the detail may show Continue assigned task; that opens the existing task page, which rechecks task access and returns to the same request and relationship filter. The link does not complete or change the request. It does not open operational failure diagnostics or disclose process variables. Current source implementation is unverified; see the SCRUM-4924 verification status below.

A published DataGrid may include calculated display columns. Each formula uses only scalar fields that the publisher also displays and that you can currently read. A column is omitted when any dependency is no longer readable; if the browser cannot evaluate an otherwise admitted formula, its cell shows a neutral dash. Calculated values do not participate in search, filtering, sorting, record identity, relations, or actions. This source addition has not yet passed consolidated validation or runtime qualification.

The source implementation and English/Arabic controls are still awaiting integrated qualification. A feature may not appear in your environment until its supported release and configuration are complete.

Search — candidate behavior

Availability: Home has no end-user search page. Current master contains a private, caller-self POST /api/home/search API behind inflow.home.search.enabled (default off; the controller is absent unless explicitly enabled), plus the existing Home and application-user-access gates. Source adapters exist for Tasks and personal Requests. A Social search adapter is also present, but it is separately default-off behind inflow.home.social.enabled. These are backend source paths, not a Home search screen, and are not release-qualified.

The Requests source searches only cases the current caller may see through the existing CaseVisibility policy and personal relationship checks as an initiator or a participant who completed a task. It matches the request reference, request ID or a title only when the current policy allows that title. It does not search form answers, process variables or arbitrary workspace cases. Results carry the current request status and Home destination; opening one rereads the request and checks the exact reference again. The source reads a 500-request candidate page plus one sentinel row to detect continuation, then uses a cursor for the next page. This is not a total count or a physical database scan guarantee. When a title is not disclosable, the result uses the permitted reference or ID label.

The Social source searches matching post text and active comment text only within the current caller's Home Social audience. The effective audience intersects the workspace-wide audience setting and configured audience groups with the caller's current group memberships; candidate rows are then projected through the original Social reader and checked again before references are opened. A Social result is not a permission grant, notification, or indication that every Social post was searched. Its source currently limits logical feed/comment rows processed per page to 1,000, but physical database work for sparse audiences or retained tombstones is not fully bounded. Do not use these unqualified APIs as operational search tools.

These sources do not add a Home search page, general record search or a workspace-wide knowledge index. If a Home search page is delivered in a future release, it must limit results to currently admitted sources and reopen each result through its ordinary authorization path; partial results must be identified as incomplete. Home-wide Knowledge search is not available; published App Chat retrieval remains limited to its publisher-approved App Shell sources.

A missing or refused area shows the neutral unavailable state. An access-service outage shows a retryable loading error instead of claiming you have no work. Signing out or changing account/context retires the previous context's displayed data. Help and account dialogs do not reload the task inbox.

Search operations record low-cardinality request and per-source outcomes in Micrometer. The labels are closed status values and fixed source kinds; search phrases, identities, workspace/object IDs, permissions and result content are not metric labels. These counters support operators and are not user-visible match counts or access grants. The internal reader is composed for the proposed Home Chat, but Home currently has no Chat API, controller or panel host. Published App Chat is separate and remains limited to publisher-approved App Shell sources and the signed-in person's access. The Home Search API and its Task, Requests and Social source paths remain unqualified; see the App Chat and Home AI guide for the current boundary.

Operator rollout and rollback

Both inflow.home.enabled=true and inflow.application-user-access.enabled=true are required. Set these through the supported canonical feature configuration, then restart the affected API. The Home switch is restart-required and defaults to false. Do not edit generated runtime files in shared environments or change a caller's grants to make a tab appear.

Before enabling Home pagination, configure inflow.home.cursor.active-key-id and one or two inflow.home.cursor.key-references.<id> entries that point to deployment-provided INFLOW_HOME_CURSOR_KEY_* environment secrets. Each secret is canonical base64 for 32 random bytes. Do not put key bytes in custom configuration, source control, logs or support captures. The deployment owner must provision identical values for every key ID on every active API node; the application can validate each node's local keyring but cannot compare remote nodes. For rotation, first publish the new key reference on every node and restart/verify every node has both keys while the old key remains active. Then switch the active ID across the fleet, restarting and verifying each node while retaining the old key for at least 15 minutes after the last node switched. Remove the old reference only after every node uses the new active key and that overlap has elapsed. Missing or malformed local key configuration prevents Home from starting; it does not fall back to a per-process key. Cursors remain bound to the authenticated account, credential, scope and route purpose, expire after 15 minutes, and can be retried from the first page when expired.

Before rollout, validate normal sign-in for an account with no business scope, an ordinary scoped task performer, an application reader, configured landing/tie/explicit-destination cases, logout/revocation and policy outage. Check the current implementation/evidence record in specs/20261109-inflow-home-socialecho/implementation-impact.md; a focused test pass is not full-platform approval. CI and deployment holds remain binding.

To roll back, set inflow.home.enabled=false through the same supported configuration and restart the affected API. This restores the prior destination resolver behavior. Current Home source includes migrations 000446 through 000450, with readiness floor 450; none may be applied under the current hold. Do not remove notification preferences, receipts or business data during rollback. Direct /home visits must still pass authentication and server admission; a URL is never an access grant.

Workspace Home settings — interface not yet shipped

The current source contains a native Home configuration API, but it does not contain the planned Home configuration page in Studio. There is no supported Home settings screen for administrators to operate yet. Do not follow a browser path or send direct configuration writes based on the planned controls below. Wait for the operator interface and its release qualification.

When that interface is delivered, administrators are expected to choose Social, Data and Starts functions from the current workspace's existing-function list, review each audience and enabled area, and save against the displayed revision. A function picker is only a choice list: it must not create functions or grant workspace access, and a previously assigned function binding is immutable. See the technical source reference for the current API contract and its not-yet-qualified status.

Integration contract

Home lives at /home and /home/tasks or /home/applications, with a validated workspace coordinate. Bootstrap and context paging are caller-self, no-store GET requests under /api/home/bootstrap and /api/home/contexts; both return the same bounded bootstrap shape. The applications endpoint is /api/home/applications. Requests accept no actor override. Context and catalog cursors are opaque, credential/context-bound, short-lived, and work across active API nodes sharing the configured keyring. Retry starts a fresh page after expiry or key retirement.

Context and application pages default to 20 with a maximum of 100. Continuation is emitted only after another admitted entry has been observed. Reads have bounded native decision/scan budgets; an unresolved budget or source failure is unavailable, not a successful empty catalog. Large-page and complex publication limits remain subject to the existing native read safety budget.

See the specification, landing contract and applications/tasks contract for the full program and remaining work.

Applications preferences — source controls with qualification pending

When the server admits personal preferences for your signed-in session, use Favorite or Unfavorite beside an application. You can keep up to 100 favorites; remove one before adding another if the limit is reached. Choose All applications, Favorites or Recent from Applications. Every view checks current access again; a saved favorite does not grant access or keep a removed application's title visible. Other readable credential types can still open applications without personal-write controls. The controls are present in current source, but the feature has not passed consolidated release qualification.

Opening an admitted published application records a recent entry after its page loads successfully. A failed recent-save does not prevent using the application, forms or Ask [App]. Previewing an application in the Designer does not add a recent entry.

If a save's outcome is uncertain, use Check change outcome. Keep the page's retained change until the outcome is resolved. A lookup that finds no receipt does not prove the original save failed; the explicit Try the same change again action repeats that exact change safely. If another change has superseded it, Reload preferences retrieves current server state before you make a new selection. Signing out retires that session's controls; the browser retains an opaque recovery hint without automatically sending it again.

Operators: this source uses the existing account preferences column and identified audit path. Do not apply or edit migrations, reset a database, or use an alternate runtime to test it. Current Home source includes migrations 000446–000450 and readiness floor 450; the chain remains unapplied. Policy-route qualification, backend/framework build, ordinary-user and release qualification remain pending. See the preference contract.

My Requests source coverage (SCRUM-4924, source draft): personal relationships require the account incarnation recorded by the original authenticated native process-creation/task-completion write. They are additionally intersected with current canonical CaseVisibility before filtering/paging. Older NULL provenance, background/unqualified identity, potential assignment and general viewer access are not personal relationships. No historical backfill or current-account timestamp inference occurs; the user interface explains this limitation. Provenance is immutable on process updates and preserved only for unchanged terminal task completers. The related source is migration 000446 within the current Home chain 000446–000450, readiness floor 450; it is unapplied. Its nullable last-persisted-update timestamp leaves historical values unknown. Final consolidated validation and native UI evidence are pending.

T011 bounded review correction: account-ID equality alone cannot attribute an inherited child initiator. The actual WorkflowRuntimeServiceImpl initial-insert call now owns a package-private scoped direct-start marker; startedFrom, an active parent ProcessContext or an inherited start credential disables current-user stamping. Repository-only saves and inherited starts remain unrecorded. No new task insert can stamp an existing/historical completed-by relationship; only native transition to completed may capture it. Capture verifies the same synchronized writable physical connection/known Spring target before and after its locked account observation. Added final consolidated regressions: replaced ID resuming old parent then nested/child start, inherited-service Start, raw historical completed-task insertion, connection swap/autocommit/read-only change and scoped-marker restoration on exception. These source corrections do not constitute test/verification evidence.

Arabic/RTL source continuation: Home dialogs now explicitly carry their copy language/direction and localized close name, including command-opened dialogs. Shared tab arrows follow the actual strip direction (RTL Left advances, Right returns; Home/End select the first/last available tab). Social/request timestamps and character counts retain browser regional/calendar/numbering settings. These source corrections still require consolidated tests and actual Arabic keyboard/narrow/zoom/video qualification; they are not a completed verification claim.

Home's existing task inbox now accepts an explicit runtime copy locale, including Arabic tabs, filters, current task labels, claim/load recovery, empty states, counts and paging/accessibility names. Studio retains the English default. The existing runtime task-detail, confirmation, comment, draft, receipt and people/document-picker source now accepts the Arabic copy path. Actual runtime qualification and final native UI evidence remain required.

Task-result guidance distinguishes a recorded response from process progression: the process may wait for other responses or stop at a failed step after the answer was recorded. An already-completed task explicitly says the new answer on this page was not saved. An uncertain completion keeps the current work and asks you to check the task before resubmitting. Arabic runtime copy preserves these distinctions, the current draft-conflict/leave confirmations and current people/document-picker permissions. Task forms retain the language chosen by their authors. Comments/attachments now use the shared keyboard-aware tab strip. This is source implementation, pending consolidated tests and actual Arabic UI/video qualification.

Planned candidate: Business Starts (not available in the current Home UI)

The following describes intended behavior; do not look for these controls in Home Applications or send requests to a candidate route. The current Home application page lists admitted published App Shell pages. It does not expose Start an action.

The candidate Business Starts journey would list actions only when both publication audience and the user's current canonical start access permit them. Its form would use the published input contract and retain an operation identity for safe outcome recovery. It is not a released end-user path.

The following describes intended behavior; it is not an instruction to configure a Home view. A future Data Navigator would display only published, explicitly admitted views and actions. Any related-record handoff would need to recheck the request relationship and current process/record access, and would not expose process variables or list records.

Planned candidate: saved views (not available in the current Home UI)

The candidate contract makes saved views private by default. Any future sharing would require publisher permission for that exact view and reauthorization of each recipient's audience, source and fields; it would not grant data access. These controls are not currently offered in Home.

Planned candidate: operator save recovery and Studio publication

Availability: The following Data Navigator recovery and Home business-view publisher pages are not present in the current Studio Home source. Their route names and controls are design notes, not supported paths. Do not open or call the example routes below in a live environment.

The candidate design includes a privileged way to inspect an exact save receipt and a separate publication editor for deliberate field, audience, relation and action choices. It would preserve exact operation identity and require explicit confirmation for changes. No current Home user or operator page provides these controls.

The current route inventory, published screens and source contracts remain the authority for released behavior. See the Home publication availability guide for the current App Shell path and feature status.

Images and references in Social — future design only

Availability: Home has no current Social page or admitted Social write path for images, references, or mentions. The API refuses non-empty attachment, reference, and mention content. Everything in this section describes a possible future flow; these controls, drafts, and operations are not available in Home today.

In a future qualified release that supports images, a user could open Preview image or Download normalized image for an image they can currently access. Closing the preview would return focus to its opener, and the original post would not grant access to its files. A future interface could show pending, rejected, or unavailable states without exposing file details. Processing would not promise background completion or certify a malware scan.

A proposed composer could let a user choose one JPEG/PNG image at a time, up to four, and recheck the same selected version before posting. A future draft might retain typed references while hiding filenames until access is checked; removing a reference would not delete the library file. If a future write outcome were uncertain, its exact operation identity would need to be checked before any retry. Do not look for Choose an existing image, Check selected images, or Remove from draft in the current Home experience.

Mention editing is not available in Home. There is no eligible-person selector, and the current Social API rejects a non-empty mention list. Typing an @name in post text does not notify anyone. The following replacement flow is a future design only: after a supported selector and authorized backend path exist, an editor could choose an audience, select the complete replacement list, and save while keeping recipients private. Do not expect Replace mentioned people or Save replacement mentions today.

A future qualified edit flow could recheck an author's image access before changing image pins. Current Home cannot load or save images, references, or private mention recipients through Social; do not expect an image-edit dialog or post-save operation to preserve them.

لا تتوفر حاليًا في Home واجهة لاختيار الصور أو المراجع أو نشرها عبر Social؛ وترفض واجهة API الحالية هذه الحمولات غير الفارغة. في تصميم مستقبلي مؤهل، قد يتيح محرر المنشور اختيار صورة JPEG أو PNG واحدة في كل مرة، حتى أربع صور، ثم يعيد التحقق من الإصدار نفسه قبل النشر. وقد تخفي المسودة أسماء الملفات حتى التحقق من الصلاحية، مع إزالة المرجع دون حذف الملف. هذه أوصاف للتصميم فقط وليست خطوات قابلة للتنفيذ اليوم.

لا يتوفر تعديل الإشارات إلى الأشخاص في الصفحة الرئيسية. لا يوجد محدد للأشخاص المؤهلين، وترفض واجهة Social الحالية قائمة إشارات غير فارغة. كتابة @اسم في نص المنشور لا ترسل إشعارًا. تدفق الاستبدال التالي تصور مستقبلي فقط: بعد توفير محدد معتمد ومسار خلفي مخوّل، يمكن للمحرر اختيار الجمهور ثم القائمة الكاملة الجديدة مع إبقاء المستلمين خاصين. لا تتوقع ظهور استبدال الأشخاص المشار إليهم أو حفظ الإشارات البديلة حاليًا.

Inflow documentation · Published 19 November 2026

Screenshot captions retain their recorded build and capture context.

Type to search articles and their contents.