Adobe Connect Support Blog

September 7, 2013 /Seminars /

Adobe Connect 9.1 Seminar Session Creation via the XML API

With the release of Adobe Connect 9.1, we are changing the way that Seminars need to be scheduled (more information here). That being said, there are obviously new integration requirements that are needed around this new functionality.  I am briefly going to talk about the steps it takes to create the new Seminar Sessions now with the XML API.

The first thing in the workflow would obviously be to create a Seminar Room (that you would associate a Seminar Session to).  You would do this as you normally would except now (with Connect 9.1) you do not specify a Start and End time in the creation process of the room itself.  You will notice even in the UI, that there is no longer a place to set a start and end time for a Seminar Room itself.  This needs to now be done in a Seminar Session moving forward.

So to create a Seminar Room, all you need to do is the following:

Call sco-update as:

 {serverURL}/api/xml?action=sco-update&type=meeting&folder-id=11029&name=MySeminar&url-path=/myseminar/

 (the ‘description’ parameter is optional).

where:

  • action=sco-update
  • type=meeting
  • folder-id={your Seminar License Folder sco-id)
  • name={whatever name you want to call the Seminar Room}
  • url-path={any custom URL you want} not required. System will just auto generate if left blank.

Results:

<results>
<status code=”ok”/>
<sco account-id=”7″ disabled=”” display-seq=”0″ folder-id=”11029″ icon=”meeting” lang=”en” max-retries=”” sco-id=”30009″ source-sco-id=”” type=”meeting” version=”0″>
<date-created>2013-08-26T17:08:30.060-04:00</date-created>
<date-modified>2013-08-26T17:08:30.060-04:00</date-modified>
<name>MySeminar</name>
<url-path>/myseminar/</url-path>
</sco>
</results>

 

Then, after your Seminar Room has been created, you need to create your Seminar Session with three (3) API calls.  

 

First:

Use the sco-update call to create the sco for the Seminar Session:

{serverURL}/api/xml?action=sco-update&type=5&name=MySeminarSession&folder-id=30009

where:

  • action=sco-update
  • type=5 (or type=seminarsession … either will work)
  • name={whatever you want it to be called}
  • folder-id={the sco-id of the Seminar Room from call 1 above}

Results:

<results>
<status code=”ok”/>
<sco account-id=”7″ disabled=”” display-seq=”0″ folder-id=”30009″ icon=”swf” lang=”en” max-retries=”” sco-id=”30010″ source-sco-id=”” type=”seminarsession” version=”0″>
<date-created>2013-08-26T17:12:54.927-04:00</date-created>
<date-modified>2013-08-26T17:12:54.927-04:00</date-modified>
<name>MySeminarSession</name>
<url-path>/p38z3wpft84/</url-path>
</sco>
</results>

 

Second:

Use the seminar-session-sco-update call to set the Session’s date/time as well as assign it to a Seminar Room (that either you created in the first part at the start of this blog entry or that exists already in Adobe Connect):

{serverURL}/api/xml?action=seminar-session-sco-update&sco-id=30010&source-sco-id=30009&parent-acl-id=30009&date-begin=2013-08-30T14:00:00.000-07:00&date-end=2013-08-30T15:00:10.000-07:00

where:

  • action=seminar-session-sco-update
  • sco-id={the sco-id of the Seminar Session from step ‘a’ above}
  • source-sco-id={the sco-id of the Seminar Room from step 1}
  • parent-acl-id={the sco-id of the Seminar Room from step 1}
  • date-begin={the starting date/time for the Session}
  • date-end={the ending date/time for the Session}

** the dates cannot conflict with another session or you will get an error response in the result, indicating there is a conflict.

*** yes source-sco-id and parent-acl-id are the same value in this call.

Results:

<results>
<status code=”ok”/>
</results>

 

Third:

Use the acl-field-update call to set the seminar-expected-load value:

{serverURL}/api/xml?action=acl-field-update&acl-id=30010&field-id=311&value=25

where :

  • action=acl-field-update
  • acl-id={the sco-id of the Seminar Session from the first step in the Seminar Sessions creation steps above}
  • field-id=311 (yes, use this field-id=311)
  • value={expected seminar load}

Results:

<results>
<status code=”ok”/>
</results>

*** If you don’t do this, it won’t show up on the Seminar Calendar.

 

 

Seminars

Join the discussion