Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Events/EventBusinessRules/SpeakerRulesExample.htm

## Examples of Event Speaker Rules

This topic contains detailed examples for each type of Event Speaker Rule.

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)Per Speaker Engagement Limit Rule](#)

The admin wants to warn event organizers if an invited speaker of a Speaker Program in the US has already been a confirmed speaker more than three times in a rolling 90 day period.

To implement this restriction:

1. Navigate to the **Event Business Rules** tab.
2. Create an event business rule with an object type of **em\_per\_speaker\_engagement\_limit\_rule\_\_v.**
3. Populate the following fields:

   | Field | Value |
   | --- | --- |
   | name\_\_v | Speaker Program Ninety Day Limit |
   | run\_on\_event\_action\_\_v | submit\_for\_approval\_\_v |
   | speaker\_status\_\_v | requested\_\_v:invited\_\_v,accepted\_\_v;;approved\_\_v:invited\_\_v,accepted\_\_v;;closed\_\_v:attended\_\_v,signed\_\_v;; |
   | date\_threshold\_type\_\_v | rolling\_\_v |
   | rolling\_period\_\_v | 90 |
   | warning\_type\_\_v | Hard Warning |
   | warning\_text\_\_v | EM\_RULE\_PER\_SPEAKER\_ENGAGEMENT;;EVENT\_BUSINESS\_RULE\_WARNING (Populated automatically) |

   The admin leaves the per\_event\_topic\_\_v checkbox unselected to apply the restriction regardless of event topic.
4. Select **Save**.

After creating the Event Business Rule, associate the rule to the appropriate Event Type and Country:

1. Navigate to the **Speaker Program Ninety Day Limit** record.
2. Navigate to the **Event Business Rule Configurations** related list.
3. Select **New**.
4. Create an **Event Business Rule Configuration** record with the following values:

   | Field | Value |
   | --- | --- |
   | event\_business\_rule\_\_v | Speaker Program Ninety Day Limit  (Populated automatically) |
   | event\_type\_\_v | speaker\_program\_\_v |
   | country\_\_v | United States |
   | rule\_start\_date\_\_v | January 1, 2020 |
   | rule\_end\_date\_\_v | December 31, 2050 |
   | limit\_quantity\_\_v | 3 |
5. Select **Save**.

An event organizer plans a Speaker Program in the US and adds Clinton Ackerman as a speaker. However, Clinton Ackerman has already been a speaker three times in the last 90 days, so when the event organizer selects Submit for Approval, the following hard warning displays:

Clinton Ackerman has been added as a speaker at 3 United States Speaker Program events. Speakers cannot speak at more than 3 events.

The event organizer is prevented from submitting the event for approval, so the organizer removes Dr. Ackerman as a speaker and selects another speaker before submitting the event again.

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)Cross-Event Per Speaker Engagement Limit Rule](#)

The admin wants to warn event organizers if an invited speaker in the US has already been a confirmed speaker at more than ten Speaker Programs, Congresses, or Lunch and Learns during the year.

To implement this restriction:

1. Navigate to the **Event Business Rules** tab.
2. Create an event business rule with a object type of **em\_cross\_event\_per\_speaker\_engagement\_limit\_rule\_\_v**.
3. Populate the following fields:

   | Field | Value |
   | --- | --- |
   | name\_\_v | US Speaker Annual Limit |
   | run\_on\_event\_action\_\_v | submit\_for\_approval\_\_v |
   | speaker\_status\_\_v | requested\_\_v:invited\_\_v,accepted\_\_v;;approved\_\_v:invited\_\_v,accepted\_\_v;;closed\_\_v:attended\_\_v,signed\_\_v;; |
   | date\_threshold\_type\_\_v | calendar\_year\_\_v |
   | limit\_quantity\_\_v | 10 |
   | warning\_type\_\_v | Soft Warning |
   | warning\_text\_\_v | EM\_RULE\_CROSSEVENT\_PER\_SPEAKER\_ENGAGEMENT (Populated automatically) |
   | comment\_required\_\_v | Required |

   The admin leaves the per\_event\_topic\_\_v checkbox unselected to apply the restriction regardless of event topic.
4. Select **Save**.

After creating the Event Business Rule, associate the rule to the appropriate Event Type and Country:

1. Navigate to the **US Speaker Annual Limit** record.
2. Navigate to the **Event Business Rule Configurations** related list.
3. Select **New**.
4. Create three new **Event Business Rule Configuration** records with the following values:

   | Field | Record 1 | Record 2 | Record 3 |
   | --- | --- | --- | --- |
   | event\_business\_rule\_\_v | US Speaker Annual Limit  (Populated automatically) | US Speaker Annual Limit  (Populated automatically) | US Speaker Annual Limit  (Populated automatically) |
   | event\_type\_\_v | speaker\_program\_\_v | congress\_\_v | lunch\_and\_learn\_\_v |
   | country\_\_v | United States | United States | United States |
   | rule\_start\_date\_\_v | January 1, 2020 | January 1, 2020 | January 1, 2020 |
   | rule\_end\_date\_\_v | December 31, 2050 | December 31, 2050 | December 31, 2050 |
5. Select **Save**.

An event organizer plans a Speaker Program in the US and adds Dr. Bob Adams as a speaker. However, Dr. Adams has already been a confirmed speaker at four Congresses, four Lunch and Learns, and three other Speaker Programs during the year. When the organizer selects Submit for Approval, the following warning displays:

Bob Adams has been added as a speaker at 11 events. Speakers cannot speak at more than 10 events.

The event organizer enters a reason for keeping Bob Adams as the speaker, then selects Continue and continues planning the event.

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)Speaker Attendance By Expense Cap Rule](#)

The admin wants to warn event organizers if the expenses for a speaker at a Congress in the US exceeds 10% of their associated expense cap.

To implement this restriction:

1. Navigate to the Event Business Rules tab.
2. Create an event business rule with a object type of **em\_speaker\_attendance\_expense\_cap\_rul\_\_v**.
3. Populate the following fields:

   | Field | Value |
   | --- | --- |
   | name\_\_v | US Congress Expense Threshold |
   | run\_on\_event\_action\_\_v | submit\_\_v |
   | percent\_threshold\_\_v | 10 |
   | warning\_type\_\_v | Soft Warning |
   | warning\_text\_\_v | EM\_RULE\_SPEAKER\_ATTENDANCE\_EXPENSE\_CAP;;EVENT\_BUSINESS\_RULE\_WARNING  (Populated automatically) |
   | comment\_required\_\_v | Required |
4. Select Save.

After creating the Event Business Rule, associate the rule to the appropriate Event Type and Country:

1. Navigate to the US Congress Expense Threshold record.
2. Navigate to the Event Business Rule Configurations related list.
3. Select New.
4. Create a new Event Business Rule Configuration record with the following values:

   | Field | Value |
   | --- | --- |
   | event\_business\_rule\_\_v | US Congress Expense Threshold  (Populated automatically) |
   | event\_type\_\_v | congress\_\_v |
   | country\_\_v | United States |
   | rule\_start\_date\_\_v | January 1, 2020 |
   | rule\_end\_date\_\_v | December 31, 2050 |
5. Select Save.

Dr. Ackerman has an annual Speaker Expense Cap of $1000, of which $950 has already been committed. An event organizer attempts to add Dr. Ackerman to a new Congress. Since Dr. Ackerman has less than 10% of his annual expense cap remaining, the following warning displays when the event's expenses are submitted:

Clinton Ackerman has exceeded their Speaker Expense Cap and cannot be added to this event.

The event organizer enters a reason for Dr. Ackerman’s expenses exceeding his cap, then selects Continue and continues planning the event.

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)Per Event Speaker Ratio Rule](#)

The admin wants to enforce a speaker-to-attendees ratio of 3 attendees per invited speaker for Congresses both in the US and Canada.

To implement this restriction:

1. Navigate to the Event Business Rules tab.
2. Create an event business rule with an object type of em\_per\_event\_speaker\_ratio\_rule\_\_v.
3. Populate the following fields:

   | Field | Value |
   | --- | --- |
   | name\_\_v | US-Canada Speaker Ratio Rule |
   | run\_on\_event\_action\_\_v | submit\_for\_approval\_\_v |
   | speaker\_status\_\_v | invited\_\_v |
   | attendee\_account\_type\_\_v | account\_\_v |
   | warning\_type\_\_v | Hard Warning |
   | warning\_text\_\_v | EM\_RULE\_PER\_EVENT\_SPEAKER\_RATIO;;EVENT\_BUSINESS\_RULE\_WARNING  (Populated Automatically) |

   The admin leaves the attendee\_status\_\_v field empty to apply the rule to all attendees, regardless of status.
4. Select Save.

After creating the Event Business Rule, associate the rule to the appropriate Event Type and Countries:

1. Navigate to the US-Canada Speaker Ratio Rule record.
2. Navigate to the Event Business Rule Configurations related list.
3. Select New.
4. Create two new Event Business Rule Configuration records with the following values:

   | Field | Record 1 | Record 2 |
   | --- | --- | --- |
   | event\_business\_rule\_\_v | US-Canada Speaker Ratio Rule  (Populated automatically) | US-Canada Speaker Ratio Rule  (Populated automatically) |
   | event\_type\_\_v | congress\_\_v | congress\_\_v |
   | country\_\_v | United States | Canada |
   | limit\_quantity\_\_v | 3 | 3 |
   | rule\_start\_date\_\_v | January 1, 2020 | January 1, 2020 |
   | rule\_end\_date\_\_v | December 31, 2050 | December 31, 2050 |
5. Select Save.

An event organizer plans a Congress in the US that has four speakers and nine attendees. When the event is submitted for approval, the following warning displays:

A US Congress can have 3 attendee(s) per each speaker.

The event organizer removes one speaker from her Congress before submitting the event for approval again.

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)Per Event Speaker Limit Rule](#)

The admin wants to limit the number of speakers at any Congress to between four and six.

To implement this restriction:

1. Navigate to the Event Business Rules tab.
2. Create an event business rule with an object type of em\_per\_event\_speaker\_limit\_rule\_\_v.
3. Populate the following fields:

   | Field | Value |
   | --- | --- |
   | name\_\_v | Speaker Limit Rule |
   | run\_on\_event\_action\_\_v | submit\_for\_approval\_\_v |
   | speaker\_status\_\_v | invited\_\_v |
   | global\_rule\_\_v | Selected |
   | warning\_type\_\_v | Soft Warning |
   | warning\_text\_\_v | EM\_RULE\_PER\_EVENT\_SPEAKER\_LIMIT;;EVENT\_BUSINESS\_RULE\_WARNING  (Populated automatically) |
   | comment\_required\_\_v | Optional |
4. Select Save.

After creating the Event Business Rule, associate the rule to the appropriate Event Type:

1. Navigate to the Speaker Limit Rule record.
2. Navigate to the Event Business Rule Configurations related list.
3. Select New.
4. Create a new Event Business Rule Configuration record with the following values:

   | Field | Value |
   | --- | --- |
   | event\_business\_rule\_\_v | Speaker Limit Rule  (Populated automatically) |
   | event\_type\_\_v | congress\_\_v |
   | minimum\_quantity\_\_v | 4 |
   | maximum\_quantity\_\_v | 6 |
   | rule\_start\_date\_\_v | January 1, 2020 |
   | rule\_end\_date\_\_v | December 31, 2050 |
5. Select Save.

An event organizer plans a Congress with seven speakers. When the event is submitted for approval, the following warning displays:

Congress must have between 4 and 6 speakers.

The event organizer believes that the additional speaker is necessary, despite the rule, and enters a reason before selecting Continue and continuing to plan the event.

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)Speaker Attendance Qualification](#)

The admin wants to restrict speakers who are qualified to speak at a Congress from being added as attendees to the event, regardless of country.

To implement this restriction:

1. Navigate to the Event Business Rules tab.
2. Create an event business rule with a object type of **em\_speaker\_attendance\_qualification\_r\_\_v**.
3. Populate the following fields:

   | Field | Value |
   | --- | --- |
   | name\_\_v | Congress Qualification Rule |
   | run\_on\_event\_action\_\_v | submit\_for\_approval\_\_v |
   | global\_rule\_\_v | Selected |
   | warning\_type\_\_v | Hard Warning |
   | warning\_text\_\_v | EM\_RULE\_SPEAKER\_ATTENDANCE\_QUALIFICATION;;EVENT\_BUSINESS\_RULE\_WARNING  (Populated automatically) |
   | comment\_required\_\_v | Required |
4. Select Save.

After creating the Event Business Rule, associate the rule to the appropriate Event Type:

1. Navigate to the Congress Qualification Rule record.
2. Navigate to the Event Business Rule Configurations related list.
3. Select New.
4. Create a new Event Business Rule Configuration record with the following values:

   | Field | Value |
   | --- | --- |
   | event\_business\_rule\_\_v | Congress Qualification Rule  (Populated automatically) |
   | event\_type\_\_v | congress\_\_v |
   | rule\_start\_date\_\_v | January 1, 2020 |
   | rule\_end\_date\_\_v | December 31, 2050 |
5. Select Save.

An event organizer plans a Congress about Cholecap and adds Dr. Clinton Ackerman as an attendee. However, Dr. Ackerman has a valid speaker qualification for the topic Cholecap and therefore should not be eligible to attend the event as an attendee. When the event is submitted for approval, the following warning displays:

Clinton Ackerman is trained to speak at events for Cholecap. They cannot be added as an attendee.

The event organizer must remove Dr. Ackerman as an attendee before submitting the event for approval.

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)Speaker Attendance By Expense Cap Rule](#)

The instance is using [product-specific speaker caps](../Speakers/ProductCaps.htm) and the admin wants to warn event organizers if the expenses for a speaker at a Congress in the US exceeds 15% of their associated product-specific cap.

To implement this restriction:

1. Navigate to the **Event Business Rules** tab.
2. Create an event business rule with a object type of **speaker\_attendance\_product\_cap\_rule\_\_v**.
3. Populate the following fields:

   | Field | Value |
   | --- | --- |
   | name\_\_v | US Congress Product Threshold |
   | run\_on\_event\_action\_\_v | submit\_\_v |
   | percent\_threshold\_\_v | 15 |
   | warning\_type\_\_v | Soft Warning |
   | warning\_text\_\_v | EM\_RULE\_SPEAKER\_ATTENDANCE\_PRODUCT\_CAP;;EVENT\_BUSINESS\_RULE\_WARNING  (Populated automatically) |
   | comment\_required\_\_v | Required |
4. Select **Save**.

After creating the Event Business Rule, associate the rule to the appropriate Event Type and Country:

1. Navigate to the **Event Business Rule Configurations** related list of the US Congress Product Threshold record.
2. Select **New**.
3. Create a new **Event Business Rule Configuration** record with the following values:

   | Field | Value |
   | --- | --- |
   | event\_business\_rule\_\_v | US Congress Product Threshold  (Populated automatically) |
   | event\_type\_\_v | congress\_\_v |
   | country\_\_v | United States |
   | rule\_start\_date\_\_v | January 1, 2024 |
   | rule\_end\_date\_\_v | December 31, 2050 |
4. Select **Save**.

An event organizer for a Congress attempts to add a speaker to the event. However, the speaker has a product-specific speaker cap for the subject of the event of $1000, of which, $900 has already been committed. Since the speaker has less than 15% of his annual product-specific cap remaining, a warning displays when the event organizer submits the event.

Since this is a Soft Warning-type rule with comments required, the event can still be submitted after the event organizer enters their reasoning and selects Continue.

### Related Topics

[Creating Event Speaker Rules](SpeakerRules.htm)

[Warning Text and Tokens](WarningTextTokens.htm)