It is all related. If you were screen sharing from your Share layout (with Share Pod 1) to the Discussion layout (without any Share pods) - the screen share stops. It has to, since the pod is no longer available. There is a solution I can suggest for this very scenario.
In the Discussion layout, add the same Share Pod (Share Pod 1, for example) that you have in the Share layout. But hide it underneath one of the other pods in that layout. Thus, when you switch from the Share layout to the Discussion layout, the same share pod is available; and you are still sharing, but no one can see it. When you switch back to the Share layout, the share will continue and be visible to the attendees.
This solution works for switching between layouts, as described above. I have confirmed that it works with BOR, though I do caution you may not want to do it this way. It tends to be better to reshare after ending BOR. That's up to you - but I have confirmed you can share your screen as long as you use the same instance of a pod in all BOR and the "main room".
Regards,
Andrew
]]>I had a lapse in memory. I figured out your issue. Your account has CSRF enabled for XML-APIs (found by being logged-in as an Administrator at: Admin > Account > More Settings > CSRF Settings > Enable CSRF Protection for XML API.
NOTE: During my tests with you, previously, I just used the browser, on an account that does not have CSRF protection enabled. I have a connect.js file I built that has the ability to call all APIs and includes the OWASP_CSRFTOKEN to work with accounts that has it enabled. So my applications are designed to work.
This means that:
1. You will need to search for/include a parameter called OWASP_CSRFTOKEN in your API
2. You'll need to use an HTTP-POST (and will not be able to use HTTP-GET such as typing API commands into a browser).
NOTE: I tend to use Postman, but there are a number of other tools you can use for sending HTTP-POST commands for testing purposes
To get/use the CSRF token, I tend to:
* Call common-info API and then parse both:
- results.OWASP_CSRFTOKEN.token
- results.common.cookie
These will be used for all future commands until logout is called
* Call login API (passing both parameters above), such that: https://{DOMAIN}/api/xml?action=login&login=ADMIN_LOGIN&password=ADMIN_PASSWORD&OWASP_CSRFTOKEN=a129df7d301a67711cfb974a28b1d6416f6c84ea03a1aecbf4ccb5a269fff7f9&session=na12breezfp6oi4t3wyewab31
* Call principal-update API to create the new user: https://{DOMAIN}/api/xml?action=principal-update&email=deleteuser@envolvemedia.com&type=user&first-name=delete&last-name=user&password=connect12&has-children=false&OWASP_CSRFTOKEN=a129df7d301a67711cfb974a28b1d6416f6c84ea03a1aecbf4ccb5a269fff7f9&session=na12breezfp6oi4t3wyewab31
Here is the result:
Feel free to respond in this forum, or you can reach out, if you still need assistance.
Regards,
Andrew
]]>Presenters are able to change breakout rooms, on their own. If a user is a Presenter before you start the breakout rooms, they can switch rooms using the dropdown, available at the top-center
NOTE: This is the Adobe/Hosted view, which is running Adobe Connect 12.5.1
Regards,
Andrew
]]>When you create the breakout room (BOR), it uses the layout that is selected at the time. You have two options to create 3 different breakout rooms:
1. Use three different layouts when you create the rooms
2. Create three rooms and then before your actual meeting starts - start BOR, enter each room as a host and change the layout/content structure
For option 1, above:
When you create BOR, three rooms are created by default, using the layout you are currently on as the template. Before creating BOR, create three dedicated layouts each with the structure/content you want for the three different BOR. Then select the layout you want to use for BOR1. In the attendee pod, switch to BOR view. Delete Breakout2 and Breakout3. Click Start Breakout. Then you can immediately end the BOR. Switch to the layout you want to use for BOR2. In the Attendees pod (still in BOR view), click the + to add a new BOR. Click Start Breakout. Immediately end BOR. Switch to the layout you want to use for BOR3. In the Attendees pod (still in BOR view), click the + to add anew BOR and Start Breakout. Immediately end the breakouts.
You have now 3 BOR, each with different content/views/layouts
For option 2:
When you create BOR by default, it creates 3 rooms using the current layout as the template. Before your actual meeting starts, you can start BOR at any time. Go into each BOR individually and change the layout and upload content you want for each separate room
Does this make sense?
]]>I am looking for ideas for a 10-minute icebreaker activity for an event with 10 to 12 participants.
We want to get everyone using their cameras and to participate in an activity that helps them get to know each other.
Any ideas will be much appreciated.
Thanks
Bob
Alessandra
]]>Since the summer (I assume the Adobe Connect 12 update), the team I work have found the new Meeting Dashboard challenging. As hosts, we can no longer view meetings created by other people in the Meeting Dashboard.
Does anyone know of a solution to this?
Many thanks in anticipation.
]]>