Workplace is the CP4BA end-user application for tasks, launching processes and cases across all workflow engines of the platform (Workflow Servers, Case, Automation Workstreams) - it is federated by design. The classic Process Portal was a process app running inside one Process Server; on containers it is deprecated and not the entry point in the dashboard.
- Process Federation Server (PFS) indexes tasks and instances of every registered workflow system into OpenSearch / Elasticsearch and exposes the federated REST API (/rest/bpm/federated/v1). Workplace reads its task list, launch list and saved searches from PFS - without PFS Workplace shows nothing from Workflow Servers. The operator deploys PFS when workflow / workstreams patterns are selected (pfs_configuration in the CR).
- What Workplace has: task list with filters and saved searches, launch (exposed processes / services / dashboards), case work, in-app notifications, custom columns from exposed business data, the responsive task UI (coaches render inside Workplace).
- What it does not have: the classic portal's collaboration stream, portal themes, the "Dashboards" toolkit widgets (Team Performance, Process Performance) - replaced by BAI dashboards; custom portal process apps (copies of the System Process Portal) are not used.
- Custom dashboards still work: a client-side human service exposed as a dashboard appears in Workplace's launch list and runs inside it; the Dashboards toolkit's charts can be replaced by UI Toolkit charts or BAI.
# federated task list as Workplace sees it (Zen API key + CSRF)
GET https://cpd.../pfs/rest/bpm/federated/v1/tasks?size=50&offset=0 (path via the PFS route in .status.endpoints)
GET .../rest/bpm/federated/v1/systems # registered workflow systems and their index state
If the classic portal is still required on a release that deploys it, it is reachable on the Workflow Server route under /ProcessPortal, but treat it as a transition aid, not a target.
References