Single Record pages

The detail view for one record in a Journey Manager App — its header, featured attributes, attribute groups, and actions — plus the New Record form used to create records.

A Single Record page (SRP) is the detail view for a single record in a Journey Manager App — what opens when a user clicks a row in a layout page or follows a field link. It’s a Section dedicated to one record, with its own layout. This page also covers the New Record form used to create records.

Single Record page

The detail layout is composed of a header, a quick-look strip, grouped attributes, and actions. Every part is optional.

Header

Configuration	Required	Description
type	Yes	How the header visual is rendered: initials, icon, or image.
source_field	Conditional	Required when type is initials — the field the initials are derived from.
icon	Conditional	Required when type is icon.
title, subtitle	No	Header text.

Featured attributes

A quick-look strip of key attributes shown near the top. Each entry has a field slug and a label; the field must exist on the section’s View.

Attribute groups

The record’s attributes can be organized into groups (tabs/sections), each with a slug and a title. Group slugs must be unique within the page.

Actions

A Single Record page can expose actions on the record — the operations a user can run from the detail view.

New Record form

The New Record form is how users create a record from inside an app. Its configuration is optional; supply only the parts you need.

Configuration	Description
core_fields	The object’s built-in fields — see Core fields by object type. Each group sets an optional title, description, a column layout of 1, 2, or 3, and its list of field slugs.
view_fields	Additional fields drawn from the section’s View. Each must exist in the View’s fields.
taxonomy_config, workflow_config, profile_config	Toggle and constrain taxonomies, workflow, and profile input on the form.
authoring_fields	The taxonomies and tags exposed for authoring (each must exist as a taxonomy/tag field on the View).
submit_behavior	What happens after creation — whether to redirect and whether to show a success message.

Core fields by object type

The built-in fields available to core_fields depend on the section’s object type:

Object type	Core fields
Contacts	given_name, last_name, email, phone, type
Content instances	title, slug, type, description
Documents	contact_id, title, slug
Orders	template_id, title, slug, contact_id, location_id, destination_location_id

For orders, the required core fields depend on the order section’s type — for example a transfer requires a destination location instead of a contact. CXF enforces the right required fields per order type when the form is saved.

Related

Sections

Field linking and creation rules that feed a Single Record page.

Layout pages

The list and visualization types that link into detail views.

Attributes

The fields shown and grouped on a record.