Updating Meetings (OAuth)

Updating Meetings (OAuth Providers)

Sametime functionality is different, so this page only refers to other meeting providers.

Agent

Updating meetings goes via the (DOMI_updateXXXXMeeting) agents. `domiUpdateMeeting() is called passing the relevant service type as a string constant.

Deprecated Functionality - 1.0.2 and Lower

Prior to version 1.0.3 each agent had different entries in the `nodesToCopy` StringList. This list contained a key (the field to set on the Calendar Entry) and a value (the node to extract from the REST API response). The fields set vary depending on what information is available from the REST API.

`domiUpdateMeeting()` was then called, passing the `nodesToCopy` StringList and the service type as a string constant.

This has now been moved to domiUtilsBE Script Library and getDOMInodeNamesToCopy function.

domiUpdateMeeting

The domiUpdateMeeting() function in the domiUtilsFE Script Library calls dominoOnlineMeetingIntegrator.updateMeeting().

The meetingID is extracted from the Calendar Entry. Some services don’t return content, so specific fields for DOMI content are extracted so the code does not wipe out the field values.

At this point there is a Select Case statement to perform slightly different processes for the different services.

Microsoft Teams does not have an update endpoint, so the code calls me.deleteMeeting() followed by me.createMeeting().
Different services use different HTTP methods, so the verb may need to vary.
Some services do not return content, so the pushMeeting() method will blank the items. So we need to reset them with the existing meeting values.

The code then goes through pushMeeting.

After pushMeeting, the code then comes back up to domiUpdateMeeting and calls domiNotifyResult().