Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Events/Configuration/DefiningPageLayouts.htm

## Defining Event Layouts

Events Management uses a layout engine to determine which layout to use based on a set of inputs, providing a dynamic user interface that displays information depending on the following factors:

* The event's object type
* The country where the event takes place
* The start date of the event
* The status of the event
* The application profile of the user
* The role of the user on the event team

For example, an event layout can be defined for end users not involved with the event, and another layout can be defined for the end user hosting the event.

**Who can use this feature?**

* Business Admin Users - Browser
* [Creating Page Layouts for Events Management](#Creating)
* [Event Page Layout Matching and Ranking](#Event)
* Users require an Events Management License

### Configuring the Page Layout Engine for

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)Business Admin Users](#)

To configure this feature:

1. Ensure [Configuring Events Management](Config.htm) is complete.
2. Navigate to **Admin > Configuration > Objects > em\_event\_\_v > Layouts**.
3. Add the **Event Layout** app section to all em\_event\_\_v layouts. This step is optional and enables troubleshooting any potential mismatches with the Page Layout Engine. If this app section is added, it should only be readable by Business Admin Users.

### Creating Page Layouts for Events Management as

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)Business Admin Users](#)

To create layouts for use in Events Management, create an em\_event\_layout\_\_v record with the following fields populated:

| Field | Description |
| --- | --- |
| event\_configuration\_\_v | Select the appropriate em\_event\_configuration\_\_v record. If you created this record from the Event Layouts related list of an em\_event\_configuration\_\_v record, this field automatically populates. |
| event\_status\_\_v | Enter the appropriate value of the status\_\_v picklist on the em\_event\_\_v object to match the layout record to. This field is case sensitive. |
| application\_profile\_\_v | Enter the appropriate application profile to match the layout record to. This field is optional, if this field is left blank, the layout record could match to any application profile. |
| event\_team\_role\_\_v | Enter the appropriate value of the role\_\_v field on the em\_event\_team\_member\_\_v object to match the layout to. This field is optional, if this field is left blank, the layout record could match to any event team member. |
| event\_layout\_\_v | Enter the name of the appropriate em\_event\_\_v layout to use. |
| expense\_estimate\_layout\_\_v | Enter the name of the appropriate em\_expense\_estimate\_\_v layout to use for any Expense Estimates created for an event matching to this layout. This field is optional, if this field is left blank, em\_expense\_estimate\_\_v layouts are determined via the standard Vault behavior. |
| expense\_header\_layout\_\_v | Enter the name of the appropriate expense\_header\_\_v layout to use for any Expense Headers created for an event matching to this layout. This field is optional, if this field is left blank, expense\_header\_\_v layouts are determined via the standard Vault behavior. |
| expense\_line\_layout\_\_v | Enter the name of the appropriate expense\_line\_\_v layout to use for any Expense Lines created for an event matching to this layout. This field is optional, if this field is left blank, expense\_line\_\_v layouts are determined via the standard Vault behavior. |
| visible\_buttons\_\_v | Use the format ;button1;button2; to enter a semicolon-separated list of buttons to display to end users. The following buttons are available:   * Edit * Delete * unlock\_\_v * approve\_\_v * submit\_for\_approval\_\_v * cancel\_event\_\_v * close\_\_v * recall\_approval\_request\_\_v * reject\_\_v * reschedule\_\_v * attendee\_reconciliation\_\_v * generate\_invitations\_\_v * generate\_sign\_in\_\_v * preview\_event\_qr\_code\_\_v * record\_a\_call\_\_v * schedule\_engage\_\_v * send\_email\_\_v * start\_webinar\_\_v * view\_signature\_\_v * Custom Actions   Users still must have View and Execute actions to buttons in order to select a defined button on the layout. |
| country\_override\_\_v | Select the appropriate em\_event\_configuration\_country\_\_v record to only apply the created layout to a specific country. This field is optional, if this field is left blank, the event layout record applies to all countries associated with the em\_event\_configuration\_\_v record. |

![](../../../Resources/Images/Events/Config/Layout.png)

#### Object Support for the Page Layout Engine

Business admin users can also configure the Page Layout Engine to control layouts of the following objects:

* em\_attendee\_\_v
* em\_event\_budget\_\_v
* em\_event\_material\_\_v
* em\_event\_session\_attendee\_\_v
* em\_event\_session\_\_v
* em\_event\_speaker\_\_v
* em\_event\_team\_member\_\_v
* em\_expense\_estimate\_\_v
* expense\_header\_\_v
* expense\_line\_\_v

To create these records:

1. Create a **em\_event\_layout\_\_v** record with an object type of related\_object\_layout\_\_v.
2. Select the appropriate value in the event\_object\_name\_\_v field.
3. Enter the appropriate information for all fields.
4. Select Save.

Ensure end users have the appropriate object and field level permission to any objects with a defined em\_event\_layout\_\_v record.

Page layouts for related objects display based on the following factors:

* Object type of the selected record
* Event Status (e.g. requested, approved)
* Country override (The country where the event takes place)
* Event Team Member role
* The application profile of the user

If a layout is not found, the standard layout displays.

### Event Page Layout Matching and Ranking as

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)Business Admin Users](#)

Event layout records determine which layout is visible to a user when viewing or editing an event. Since multiple layouts can exist for a given event type, a ranking process determines which layout is displayed when an event is loaded. Each event layout record is associated with an em\_event\_configuration\_\_v record that is associated with a group of countries. Only event layouts within the context of the event type, country, and time frame from these associations are considered.

After those parameters are met, the following ranking occurs to identify which singular layout to use for the event:

1. Country override, team role, and user profile.
2. Country override and team role.
3. Country override and profile.
4. Country override (team role and user profile are blank.
5. Team role and user profile.
6. Team role.
7. User profile.
8. Team role and user profile are blank.
9. If no matches are found, the standard layout is returned based on the event's object type. It is recommended to set a fallback event layout for each event status to prevent this scenario, and a backup layout using Vault’s standard layout configuration as a lowest-level configuration.

For example, the following records were created by the business admin:

#### Event Configuration

| Event Configuration ID | Event Type | Start Date | End Date |
| --- | --- | --- | --- |
| EC1 | speaker\_program\_\_v | 1/1/2024 | 12/31/2030 |
| EC2 | speaker\_program\_\_v | 1/1/2024 | 12/31/2029 |
| EC3 | congress\_\_v | 2/1/2024 | 8/1/2024 |

#### Event Configuration Country

| Event Configuration Country ID | Country | Event Configuration ID |
| --- | --- | --- |
| ECC1 | United States | EC1 |
| ECC2 | Canada | EC1 |
| ECC3 | Brazil | EC2 |
| ECC4 | Mexico | EC3 |

#### Event Layout

| Event Page Layout ID | Event Status | Event Layout | Team Role | Application Profile | Country Override | Event Configuration ID |
| --- | --- | --- | --- | --- | --- | --- |
| EL1 | requesting\_\_v | RQ\_US\_PC |  | Primary Care | ECC1 | EC1 |
| EL2 | requesting\_\_v | RQ\_PC |  | Primary Care |  | EC1 |
| EL3 | requesting\_\_v | RQ\_SP |  | Specialty |  | EC1 |
| EL4 | requesting\_\_v | RQ\_MK |  | Marketing |  | EC1 |
| EL5 | requesting\_\_v | RQ\_Base |  |  |  | EC1 |
| EL6 | requesting\_\_v | RQ\_PC\_Org | organizer\_\_v | Primary Care |  | EC1 |
| EL7 | requesting\_\_v | RQ\_Org | organizer\_\_v |  |  | EC1 |
| EL8 | pending\_\_v | PD\_Base\_CA |  |  | ECC2 | EC1 |

In this example, EL1 is valid in the US only, EL2 - EL7 are valid in both the US and Canada, and EL8 is valid in Canada only. For any users with the Primary Care profile in the US, the RQ\_US\_PC (EL1) layout is used, regardless if the user is an event organizer or not.

EL6 is used when a Primary Care user creates an event in Canada. If an organizer of the event in any other profile views the event, EL7 is used. If any Primary Care user who is not an event organizer views the event, EL2 is used. If a specialty or marketing user views the event in US or Canada, layouts EL3 and EL4 are used. If any user without a defined configuration for role and profile views the event, EL5 is used.

### Related Topics

[Using the Next Steps Section](../Planning/NextSteps.htm)

[Using Event Configurations](EventConfigs.htm)

[Defining Custom Event Statuses and Lifecycle States](Lifecycle.htm)