T
TimmyC1010
Hello!
Firstly I would like to apologise for what is most likely about to be a long
message.
Secondly I would like to thank everyone for taking the time to read this and
offer and advice. It is very much appreciated!
I work for a company that arranges conferences for various people. A person
may attend this conference and have access to our systems. I am tasked with
building an expansion to our systems so that those that have booked a spot at
a conference can arrange an appointment with another person at the same
conference. Doesn't sound too difficult until you get the catches:
People should not be able to see each other's email address (unless they
volunteer it of course).
No installation of Exchange on the server, ideally no Outlook installation
whatsoever.
This has to integrate with everyone's Outlook, so that they can make any
changes they need to locally without having to visit the web site.
My design idea is... hard to explain without a diagram. A user can only
request a new meeting through the website, as they will not have the other
attendees' email addresses. This way I know the userID. I can collect the
various details (though I haven't explored the web rendering stuff for
Outlook yet) and create a new AppointmentItem. A new EntryID is made for it.
That can be saved to the database, the email addresses can be thrown in and
my system would be "requesting" the appointment when I hit send on the
appItem.
Sounds reasonable so far! (I think)
A user makes a change by Outlook: I take that meetingItem and turn it into
an AppItem. The EntryIDs seem to always match (through testing) so I guess I
can use that EntryID to find the right App and then make the relevant
changes. The MeetingItem is modified so it looks like it was my company
requesting the change instead of the user (as it would appear my company
would be requesting the meeting in the first place) and then send it to the
recipients. They can Accept or Deny.
A user makes a change by website: Here is where I have a big problem in
design. I can take all the parameters, I can even get the EntryID and the
appointment in question. But I cannot create a new appointment item and
change its EntryID. So I cannot actually update that specific appointment.
EntryID is read only.
I understand this is probably hard to understand. Please feel free to email
me for any more information if you can help. I am getting truly stuck here.
If you are anywhere in London then there's beer in it for you!
Thanks again!
TimmyC
(e-mail address removed)
(e-mail address removed)
(.net 1.1; Office 2003)
Firstly I would like to apologise for what is most likely about to be a long
message.
Secondly I would like to thank everyone for taking the time to read this and
offer and advice. It is very much appreciated!
I work for a company that arranges conferences for various people. A person
may attend this conference and have access to our systems. I am tasked with
building an expansion to our systems so that those that have booked a spot at
a conference can arrange an appointment with another person at the same
conference. Doesn't sound too difficult until you get the catches:
People should not be able to see each other's email address (unless they
volunteer it of course).
No installation of Exchange on the server, ideally no Outlook installation
whatsoever.
This has to integrate with everyone's Outlook, so that they can make any
changes they need to locally without having to visit the web site.
My design idea is... hard to explain without a diagram. A user can only
request a new meeting through the website, as they will not have the other
attendees' email addresses. This way I know the userID. I can collect the
various details (though I haven't explored the web rendering stuff for
Outlook yet) and create a new AppointmentItem. A new EntryID is made for it.
That can be saved to the database, the email addresses can be thrown in and
my system would be "requesting" the appointment when I hit send on the
appItem.
Sounds reasonable so far! (I think)
A user makes a change by Outlook: I take that meetingItem and turn it into
an AppItem. The EntryIDs seem to always match (through testing) so I guess I
can use that EntryID to find the right App and then make the relevant
changes. The MeetingItem is modified so it looks like it was my company
requesting the change instead of the user (as it would appear my company
would be requesting the meeting in the first place) and then send it to the
recipients. They can Accept or Deny.
A user makes a change by website: Here is where I have a big problem in
design. I can take all the parameters, I can even get the EntryID and the
appointment in question. But I cannot create a new appointment item and
change its EntryID. So I cannot actually update that specific appointment.
EntryID is read only.
I understand this is probably hard to understand. Please feel free to email
me for any more information if you can help. I am getting truly stuck here.
If you are anywhere in London then there's beer in it for you!
Thanks again!
TimmyC
(e-mail address removed)
(e-mail address removed)
(.net 1.1; Office 2003)