Using the Meeting Conflict Checker

Aptify provides a conflict-checking mechanism that can be used to determine whether a person registering for a meeting is already registered or attempting to register for another meeting or session that occurs at the same time. This feature is particularly useful to prevent registration conflicts for organizations that have a large number of meetings or a large number of sessions at their meetings.

To implement this functionality, Aptify includes a Meeting Conflict field for meetings (on the Products record's Meetings > General tab). This allows an organization to specify conflict checking behavior on a meeting-by-meeting basis.

The Meeting Conflict field supports three values:

• No Conflict Validation: When set to this value, the system does not perform a conflict check when a person registers for this meeting. This is the default value for new and existing Meetings records.
  
  
• Conflict Warning: When set to this value, the system performs a conflict check when a user saves an order that includes a registration for this meeting. The system reviews the registrant's current meeting registrations to determine whether he or she is already registered for another meeting at the same date and time. If so, Aptify displays a warning message. A user can override this setting to ignore the conflict and create the meeting registration by clicking the Yes button.

• Conflict Prohibited: When set to this value, the system performs a conflict check when a user saves an order that includes a registration for this meeting. The system reviews the registrant's current meeting registrations to determine whether he or she is already registered for another meeting at the same date and time. If so, Aptify displays a warning message. However, in this case, the user cannot override this setting to ignore the conflict. The order cannot be saved with the conflicting meeting registration.

Keep in mind the following points when setting the Meeting Conflict parameter for meetings:

• Sessions use the Meeting Conflict setting of the parent meeting. The Meeting Conflict setting at the session level is ignored. A sessions is a Meetings record that has the top-level meeting specified in its Parent field.
  
  
• For sessions, conflict checking only occurs between sessions of the same meeting.
  
  
• The system checks for conflicts against all existing Meeting Registrations for the registrant (including any existing registration for the same meeting to prevent duplicate registrations). Also, if an order has more than one Meeting Registration order line, then the system will check for conflicts between those registrations as well when saving the order.
  
  
• On an e-Business site, if a meeting registration generates a Conflict Warning, then the on-line registration saves without error (the Web User will not be notified of the conflict). However, if a meeting registration generates a Conflict Prohibited warning, then the on-line meeting registration order will not save and the Web User is notified of the conflict while attempting to complete the on-line checkout process.