Journey designer header configuration fields reference
Journey designer headers can be configured for different journeys so that the different users can have a unique view for their role in the journey.
Heading Configuration
Note: The Heading Configuration must be created before heading fields can be added.
| Field | Description |
|---|---|
| Configuration name | The name of the header configuration. |
| Persona | Journeys have 3 personas. Each persona has its own header configuration.- Employee: The person for whom the journey is created. - Journey owner: The person who creates the journey. Managers create and modify journeys for their employees. - Mentor: The person identified to help the employee complete a journey. A mentor's permission may include the ability to add other mentors and edit a journey. |
Heading Configuration Fields
Heading fields have default labels for the name of each field. Labels are displayed to users in the journey. Add custom labels to make user visible labels meaningful to the user.
For example:
| Custom label | Table name | Field name |
|---|---|---|
| Journey publish date | Journey Accelerator Plan [sn_ja_plan] | start_on |
| Mentor | Journey [sn_jny_journey] | mentors |
| Field | Description |
|---|---|
| Custom label | A custom label is visible to the users who are part of the journey. |
| Display order | A label's display order is used in the user interface to identify how the label is displayed. |
| Field name | The default name of a field that is given to the label identified in a table. |
| Table name | The name of the table that contains the field names and custom labels used in the user interface. The header fields for journeys are in these tables.- Journey Accelerator Plan Header Field \[sn\_ja\_plan\] - Journey \[sn\_jny\_journey\] A journey header configuration can have labels identifies in multiple tables. |
Parent Topic:Journey designer reference