Skip to main content

Overview

A Journey Manager App is a custom, dashboard-style internal application you assemble — without writing code — to navigate and operate any kind of CXF object: contacts, content instances, documents, orders, and more. You build an App from reusable Sections, and each section presents its data through configurable layout pages — a data table, a kanban board, a calendar, a map, cards, a record detail view, a creation form, and so on. The result is a focused workspace your team uses to do its day-to-day work. For how this fits the platform, see Core concepts.

Where to find it

Journey Manager Apps are built under Orchestration → Journey Managers, where you design the app shell, its sections, and their layout pages. The apps your team actually uses at runtime appear in their own area of CXF.

How an App is built

A Journey Manager App is composed of a few building blocks that nest into each other:
BlockWhat it does
AppThe shell — navigation, a home/overview page, taxonomies, and attached inboxes and funnel reports. Built in the App Designer.
SectionA reusable unit of data bound to a View, exposing one or more layout pages. See Sections.
ViewThe data source behind a section — it defines the object type, the filters, and the available fields.
Layout pageA way to present a section’s data: table, kanban, calendar, timeline, map, cards, front page, funnel report. See Layout pages.
Single Record pageThe detail view for one record, and the form used to create new records. See Single Record pages.
At runtime the flow is: the app’s navigation opens a section, the section’s bound View filters the data, and the chosen layout page renders it.

Reusable sections

Sections are composable — one section can appear in many apps, and an app draws on many sections. You define a section once (its View, fields, and layout pages) and reuse it wherever it’s useful, rather than rebuilding the same data view per app.

Live reference synchronization

Apps reference sections and layout pages by identity, not by copy. When you rename a section or a layout page (its title, slug, or icon), every app that references it — in its navigation and its featured pages — is updated automatically, so links never go stale.

Date filters & aggregation

Layout pages support date filtering for time-based analysis, including comparing a current period against a previous one. The same mechanism powers dashboard aggregations — shortcut totals and widget boxes that summarize a section’s records for the selected period.

Exports

A section can be enabled for exports. When a user exports, CXF generates CSV and JSON files in the background and notifies them when the download is ready — so large exports don’t block the interface. Applying filters before exporting keeps the output focused.

Seeds

Seeds support for Journey Manager Apps is coming soon.

Governance & permissions

Only a super admin or Master can create, edit, and delete Journey Manager Apps, Sections, and Single Record pages.

API access

The User API manages Journey Manager Apps, Sections, and Single Record pages, and powers the date-filter aggregations and export generation. See the API reference.

In depth

App Designer

The app shell — navigation, home/overview, taxonomies, inboxes, and funnel reports.

Sections

Data units bound to a View, with field linking, creation rules, and exports.

Layout pages

Every way to present a section’s data, and the configuration each type needs.

Single Record pages

The record detail view and the New Record creation form.

Views

The data source bound to every section.

Conversations

The inboxes you can attach to an app.

Engagement Funnels

The funnels behind an app’s funnel reports.