RegisterMeetingAttendee XML API confirmation email inconsistent

[ayegiazaryan]

We're using the XML API to hit the "RegisterMeetingAttendee" endpoint to register users for Training Sessions.  We're also setting emailInvitations to true.  The user receives an email confirmation successfully, however the formatting and text in the email generated by the XML API are not consistent with the email confirmation received when users go through the registration form.

For example;

1. the HTML tags such as <b> and <br> are not working in the XML API generated registration confirmation email
2. The Disclaimer (and other) text is different as well.

Attached are the two examples.

• 1.PNG Is the generated when the user goes through the registration.  This version is correct.  Formatted and bolded.  Notice the text in the "Important Notice".
• 2.PNG Is generated when we call "RegisterMeetingAttendee".  You'll notice the HTML tags are not working and the disclaimer notice at the bottom is different than 1.PNG

Any help would in resolving this would be much appreciated!

ryanhunt

[nmorrow]

Hello,

     API email capabilities are generally limited due to legacy code that provided old hardcoded plain text emails and an understanding that many application developers generally want to brand their own email notifications that originate from their system. Historically, RegisterMeetingAttendee was meant for only Meeting Center and has been a rarely used request, so may not be as up to date as other requests with functionality. I was actually unaware of any Training Center support for this request. I generally recommend CreateMeetingAttendee, which actually invites an attendee, but which you can add a joinStatus value of ACCEPT to also process an approved registration. Registering via CreateMeetingAttendee also gives you the ability to view those attendees by calling LstMeetingAttendee (there is no XML API method to view registered attendees, only invitees).

[ayegiazaryan]

Thanks for the info Nathan.  Unfortunately, switching over to CreateMeetingAttendee and setting <joinStatus>REGISTER</joinStatus> yields the same result in the XML API generated email.  Thanks for the quick reply and attempting to help!

[nmorrow · Accepted solution]

Hello,

     A bug report has been generated for this issue, to be addressed in a future API release. in the meantime, you will need to either develop your own email notification system or remove HTML formatting from the email templates. Also note that unless you wish for hosts to manually approve each registration, joinStatus should be set to ACCEPT so that registration is created in an approved state.

[nmorrow]

Unfortunately, engineering has determined that this is not a bug and should be considered a new feature request. This may not be addressed at all in the near future.

[ayegiazaryan]

No problem.  Thanks for the update.

[nmorrow]

Hello,

     One more update on this, product management is seeking business justification to push this change through and is requesting that you reach out to your WebEx account manager to submit a formal feature request so that visibility is increased.

[mrafidee]

Nathan, I got a Feature Request created for the same.

Search Key word - RegisterMeetingAttendee XML API confirmation email inconsistent