23R1.1 Functionality Guide

Defining Lifecycle Stages for Events

Events Management administrators can map their organization’s event statuses to standardized lifecycle stages that display when viewing an event. This allows event team members to visualize the current event stage within the lifecycle of the event workflow.

For example, if you organized a new Speaker Program event, the lifecycle component displays the event as Requested. When the event is submitted for approval, the event’s status updates to Pending Compliance, a custom event status at your company mapped to the standard Pending Approval lifecycle stage. The lifecycle component updates to Pending Approval, letting you know that after approval is granted, you can execute the event.

Defining Stages for Events

Lifecycle stage mappings are determined by an EM_Event_Rule_vod record associated with the event. This record determines displayed lifecycle stages and the event statuses mapped to each stage.

Lifecycle stages display in a preset order. Stages can be relabeled, but custom values are not supported.

To define lifecycle stages:

1. Navigate to the appropriate EM_Event_Configuration_vod record.
2. Select New in the Event Rules related list.

3. Select Stage Settings for the record type.

4. Select Continue.

5. Enter the appropriate Country Override, if applicable.

   Country-specific stages are not supported on the Browser platform.

6. Select Save.
7. Select New Event Stage Configuration.

8. Populate the following fields:

   • Stage_vod – Available values are:
   • Requested
   • Pending Approval
   • Approved
   • Execute
   • Completed
   • Closed

   • Statuses_vod – A comma delimited list of the appropriate values from the Status_vod picklist on the EM_Event_vod object. For example:

     Requested_vod,Draft_vod

     

     Canceled_vod status should be configured in the Closed stage.

9. Select Save.
10. Repeat this process for all desired lifecycle stages.

If a stage is not applicable to your organization’s event workflow, it can be excluded. Stages without mapped statuses do not display on events.

Creating the Path Element

After all lifecycle stages have been defined, admins can add the Salesforce Path element to the EM_Event_vod object page layout:

1. Navigate to Setup > Path Settings.

2. Create a new Path for the appropriate EM_Event_vod record types.

   The Key Fields, Guidance for Success, and Celebrations components of Salesforce Paths are not supported.

3. Add the newly created Path component to the EM_Event_vod object Lightning record page layout.

   

4. Select the Hide Path Update Button check box.

Viewing Lifecycle Stages in an Event

Once at least two lifecycle stages are defined, the lifecycle component displays on new events. Otherwise, it does not display.

When an event is created, the Stage_Setting_vod and Stage_vod fields on EM_Event_vod are stamped based on the configured EM_Event_Rule_vod records.

Existing events may have these fields as blank. To display the lifecycle stages in these events, update existing events to populate these fields.

The current stage of the event is determined by the Event Lifecycle Stage mapped to the event’s Status_vod field. When the user updates the event status and lifecycle stage, for example, if the user submits the event for approval, the lifecycle stage updates accordingly.

Whenever an event changes lifecycle stages, a Event_Stage_History_vod type EM_Event_History_vod record is created to track when the event changed lifecycle stages.

The subdomain is a portion of the URL to an organization’s speaker portal that can be customized beyond the default My Domain. Admins can edit the subdomain to integrate company branding into URLs to the Speaker Portal communicated to speakers.

For example, the Event admin at Verteo BioPharma enables the Speaker Portal and edits the subdomain to VerteoBioPharma in order to better brand the org’s Speaker Portal.

https://verteo.speakers-am.veevacrm.com

Editing an Org’s Speaker Portal Subdomain

To edit an org’s Speaker Portal subdomain:

1. Navigate to the Events Management Integration Administration tab.
2. Select Speaker Portal.

3. Navigate to the Custom Subdomain section.

   

4. Select Edit.

5. Enter the appropriate subdomain name. Subdomain names must meet the following requirements:

   • Names must be less than 80 characters

     Names are automatically converted to lower case when saved. For example, VerteoBioPharma becomes verteobiopharma.

   • Names must contain only alpha-numeric and single dash characters

     Do not begin a sub domain name with a dash character.

6. Select Save.

After updating the sub domain, existing Speaker Portal links, including bookmarks and links within email invitations, are no longer valid.