Simplified Bookings And Invitations |
The internal invitation handling code is now available through the COM api:
AddParticipant( IDispatch ) RemoveParticipant (IDispatch ) GetParticipants -> Collection containing Associate or Person objects (read-only list)
The Add/remove participant functions figure out if the passed object is a person or an associate and act accordingly. If an invalid type of object is passed to AddParticipant or RemoveParticipant (e.g. a project member or a contact) then an error is signaled.
We also want to make it easier to accept or reject an invitation.
GetInvitations -> IAppointments collection
The returned list of appointments contains invitations that the user has not accepted yet. Rejected appointments may be included in the list so that the user has a chance to reconsider a rejection.
The programmer can then accept or reject the invitations using this call:
AcceptInvitation( response )
Response is a new enum: enReject = 0, enAccept = 1
The Reason field is not used.
Appointment booking conflicts can also be detected now: HasConflict -> variant_bool - returns true if there is a conflict
Up: Getting Started Prev: Role-Based Security Next: SOApplication Edit