Meeting requests can be issued to meeting attendees upon meeting creation and when new attendees are invited. The default value of the application property, curam.send.meeting.requests , is 'YES', thus ensuring that meeting requests are issued to all meeting attendees. One of the benefits of issuing meeting requests is the ability for potential meeting attendees to store the invite not only in their application calendars but also in alternative email accounts, for example, a Microsoft Outlook email account.
Email addresses should be configured for each meeting attendee. If no email address is configured, then an informational is displayed to the user issuing the meeting requests: "A meeting request was not issued to '%1s' as they do not have a valid email address". If the meeting organizer does not have a valid email address, the following informational is displayed: "A meeting request was not sent to you as you do not have a valid email address".
When this is set to 'NO', meeting requests will still appear in the invited attendees meeting calendars; however, no meeting requests will be issued via email. Also, the following informational is displayed to the meeting organizer: "A meeting request was not issued to the attendee(s) as the system administrator specified not to send meeting requests".