Meeting architecture
Connect documents, video sessions and meeting outcomes. Explore the roles of Megapolis.DocNet and Cisco Webex in the integration.
System roles
A proposed approach for an organisation choosing Webex as its video service.
Megapolis.DocNet
- Records, files and workflows
- Meeting and voting modules
- Signatures and audit history
DooxSwitch connector
- Account mapping
- Meeting-to-session relationships
- Event handling and deduplication
Cisco Webex
- Scheduling and invitations
- Video, audio and screen sharing
- Events, recordings and available summaries
Audio, video and screen sharing use the video service. The connector links meeting data and processes API events.
Linked records
- In DocNet
- Meeting record
- In the connector
- Mapping table
- In Webex
- Meeting identifier
Event flow
Prepare materials
Identify the DocNet meeting record, participants and access to materials. Agree the available API methods and exchange fields for the installed version.
Create meeting
The connector calls the Webex Meetings REST API with OAuth authorisation. Store the meeting identifier and join link alongside the meeting record.
Receive events
Webex sends webhook events to a cloud-reachable HTTPS endpoint. Verify the message signature, keep an event log and make processing safe to repeat.
Record outcomes
Retrieve permitted recordings or summaries where available. Returning materials to the document workflow, human review and follow-up assignments form a separately agreed integration flow.
Technical requirements
Deployment options?
DocNet and the connector follow the agreed deployment architecture. Webex Meetings is a Cisco cloud service in this design. If all video traffic must remain within your infrastructure, we select and verify a suitable video stack separately.
Access control?
Request only the Webex OAuth scopes needed. Keep secrets and tokens on the server. Agree document access, video participation and voting rights separately: joining the video session does not itself confer voting rights.
AI availability?
Webex generates summaries when AI Assistant is enabled; retention depends on settings and organisational policies. We use the summary as material for human review. Approved minutes follow the organisation’s formal procedure.
Material retention?
Before launch, agree recording location, retention periods, link access and deletion rules. Send agreed files or references to DocNet; copying recordings and summaries requires separate permissions and integration.
Pilot scope?
Check invitations, joining, roles, voting, qualified electronic signatures and documented outcomes. Test duplicate events, service outages and processing recovery for the connector. Agree licences, modules and acceptance criteria before development.
Technical references
DocNet functional reference and Webex API documentation. Verify the DocNet integration contract against the installed version’s documentation.
Describe your task
Discuss your meeting procedures, participants, existing systems and data-location requirements.