Webex Meetings

Release Notes 10.0.0 SP4

Important: The XML API 10.0.0 SP4 release changes some schema definitions. For the latest schema definitions, see the release notes announcements page. The features in this release are backward compatible with previous releases.

Overview

This release note describes the changes made in the release of Webex XML API 10.0.0 SP4. These changes apply to your integration with WBS 31. All features are backward compatible with existing integrations. The changes to the latest schema definitions are explained below.

What is New in this Release

This section describes the new features in XML API 10.0.0 SP4.

User preferences for default Global Call-in numbers will be supported through APIs

A site admin can enable users to set their preferred global call-in numbers from a subset of numbers available at the site level. In this release, setUser API is enhanced to allow a user or a site admin on behalf of another user to set two preferred global call-in numbers. The GetSite API can be used to get a site level list of supported call-in numbers (country aliases). This is an already supported feature. A successful request to this API returns information about Personal Meeting Room and avatar image details for a given user identity. A user identity can be one of these three:

webexId
email address
personal room url

For the avatar images, size can also be specified. As a user can have multiple avatar images, the URL to an avatar image which is most closely matches the requested size will be returned. There is no authentication required to make a request to this API.

Affected APIs

setUser

The following diagram shows the defaultGlobalCallInNum element that can be used in a SetUser request message:

Note: The phoneNumber and tollFree elements of the defaultGlobalCallInNum element are made optional. The <countryAlias> element in the SetUser request and the rest of the information is not useful in this context. As the defaultGlobalCallInNumType element is not currently used in any of the APIs as part of the request input XML body, there should not be any backward compatibility issue in making these two items optional.

New Guest API to obtain Personal Meeting Room details for other users

This release introduces the getUserCard API operation. The purpose of this API call is to obtain public information about the personal meeting room of other users. This API does not require authentication. The getUserCard API requires one of the following inputs in the request message:

Webex site and personal room ID
email address
Webex ID

The API returns basic information about the Personal Meeting Room including avatar image and personal room URL. Personal Meeting Room elements are same as the ones returned by the GetUser API for PMR related items. If the site has disabled PMR or user has no PMR enabled, PMR items will be null. For the avatar images, multiple image size can be specified. In that case, the URL to an avatar image that closely matches with the requested size will be returned. On the sites that are non-CI based (not based on the Common Identity architecture), if the image does not exist, an image based on the initials (first letter of First name and Last name) will be returned. If at any point, a valid URL image cannot be returned, the default avatar URL image will be returned. When the image URL returned is system generated or a default URL, isUploaded is set to false. For non-CI sites, if the user image file is available on the server file system and for initials-based avatar images, lastModifiedTime returned is the last modified time of that file.

Affected APIs

getUserCard

Request

The following diagram shows the getUserCard element to use in a request message:

Example Request Message

The following XML snippet shows an example of a request message sent to the getUserCard API to get basic information about the Personal Meeting Room for the specified .

Code Snippet

Copy<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <header>
    <securityContext>
      <webExID></webExID>
      <password></password>
      <siteName>sitename</siteName>
    </securityContext>
  </header>
  <body>
    <bodyContent xsi:type="java:com.webex.service.binding.user.GetUserCard">
     <webExId>webexid</webExId>
    </bodyContent>
  </body>
</serv:message>

Response

The following diagram shows the getUserCardResponse object that the User service returns:

The following diagram shows the structure of the avatar element which provides the URL to the user's avatar image, as well as other information about the image:

The following diagram shows the structure of the personalMeetingRoom element which is defined as a userCardPMRInfoType type. This element provides information about the PMR URL, as well as other information about the specified user's Personal Meeting Room.

** Example Response Message**

The following XML snippet shows an example of a successful getUserCardResponse message sent by the server in response to the above example request.

Code Snippet

Copy<?xml version="1.0" encoding="UTF-8"?>
<serv:message 
  xmlns:serv="http://www.webex.com/schemas/2002/06/service" 
  xmlns:com="http://www.webex.com/schemas/2002/06/common" 
  xmlns:use="http://www.webex.com/schemas/2002/06/service/user">
  <serv:header>
    <serv:response>
      <serv:result>SUCCESS</serv:result>
      <serv:gsbStatus>PRIMARY</serv:gsbStatus>
    </serv:response>
  </serv:header>
  <serv:body>
    <serv:bodyContent xsi:type="use:getUserCardResponse" 
                      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <use:avatar>
        <use:url>https://sitename.webex.com/mw3100/downloadFileServlet?siteurl=sitename
               &fileURI=QUhTSwAAAAWtqciY7HXkkjVkDNt8WxKgf4kZXZsr...VuZbbYI913KLO9Ctkp-jn0kS
               &isAbsolute=true</use:url>
        <use:lastModifiedTime>1454003176000</use:lastModifiedTime>
        <use:initials>UN</use:initials>
        <use:isUploaded>false</use:isUploaded>
      </use:avatar>
      <use:personalMeetingRoom>
        <use:title>User Name's Personal Room</use:title>
        <use:personalMeetingRoomURL>https://sitename.webex.com/meet/user.name</use:personalMeetingRoomURL>
        <use:accessCode>123456789</use:accessCode>
      </use:personalMeetingRoom>
    </serv:bodyContent>
  </serv:body>
</serv:message>

Support Link added to welcome emails sent from `CreateUser` API

This release changes the welcome email template by adding a new support link. The email template is used when a user is provisioned through the createUser API. The new support link points to training and help information on how to schedule and manage meetings.

Affected APIs

createUser (emails)

When a request to the createUser API (with sendWelcome flag set to TRUE) provisions a new user, the Webex service uses the default email template to send a welcome email message to the new user. This release adds a new variable to that template %SupportLink%. The XML API replaces the variable with the value: "https://help.webex.com/docs/DOC-7923". The following screenshot shows an example of the site admin panel that defines the Email template "Welcome Emails from Webex Service":