LstrecordaccessDetailHistory
The lstrecordaccessDetailHistory API supports the recorded training
access detail report.
Request
The following schema diagram shows the structure of the elements in the
lstrecordaccessDetailHistory request message.
Figure 9-9 • Schema diagram for lstrecordaccessDetailHistory
The following XML example shows a typical lstrecordaccessDetailHistory
request.
<?xml version="1.0" encoding="UTF-8"?>
<serv:message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:serv="http://www.webex.com/schemas/2002/06/service">
<header>
<securityContext>
<siteID>20070951</siteID>
<webExID>jasonc4</webExID>
<password>pass</password>
<partnerID>webexpartner</partnerID>
</securityContext>
</header>
<body>
<bodyContent xsi:type=
"java:com.webex.service.binding.history.lstrecordaccessDetailHistory">
<recondID>5862</recondID>
<timeZoneID>4</timeZoneID>
</bodyContent>
</body>
</serv:message>
For descriptions of the global elements in the security context of the
header, please see Global Request Elements in Security Context.
For descriptions of the non-global elements, please refer to “Elements
in WebEx XML Schema Definitions for the History Service”.
Response
The following schema diagram shows the structure of the elements in thelstrecordaccessDetailHistoryResponse message.
Figure 9-10 • Schema diagram for
lstrecordaccessDetailHistoryResponse
The following XML example shows a typicallstrecordaccessDetailHistoryResponse.
<?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:history="http://www.webex.com/schemas/2002/06/service/history">
<serv:header>
<serv:response>
<serv:result>SUCCESS</serv:result>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
</serv:response>
</serv:header>
<serv:body>
<serv:bodyContent
xsi:type="history:lstrecordaccessDetailHistoryResponse"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<history:recordDetail>
<history:viewID>1307</history:viewID>
<history:participantName>jason4 chencc</history:participantName>
<history:participantEmail>jasonc@sz.webex.com
</history:participantEmail>
<history:accessTime>01/21/2008 17:16:03</history:accessTime>
<history:registered>false</history:registered>
<history:downloaded>false</history:downloaded>
<history:viewed>true</history:viewed>
<history:timeZoneID>4</history:timeZoneID>
</history:recordDetail>
<history:recordDetail>
<history:viewID>1312</history:viewID>
<history:participantName>jason4 chencc</history:participantName>
<history:participantEmail>jasonc@sz.webex.com
</history:participantEmail>
<history:accessTime>01/22/2008 00:08:35</history:accessTime>
<history:registered>false</history:registered>
<history:downloaded>true</history:downloaded>
<history:viewed>false</history:viewed>
<history:timeZoneID>4</history:timeZoneID>
</history:recordDetail>
<history:matchingRecords>
<serv:total>2</serv:total>
<serv:returned>2</serv:returned>
<serv:startFrom>1</serv:startFrom>
</history:matchingRecords>
</serv:bodyContent>
</serv:body>
</serv:message>
The result and exceptionID global elements allow you to confirm that
an instantiation request was successful. They are described in "Global Response
Elements Showing Results and Errors”.