| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
Hello,
Could someone verify this please. I have no more access to a V2.3
system.
My customer upgraded from ALL-IN-1 V2.3 to ALL-IN-1 V3.0. They were
claiming that the problem they are experiencing right now was not
in V2.3.
When a user receives a meeting invitation and if there is a conflict
and do a GOLD I (user wants to go to TM via interrupt menu to check the
conflict) it gives you an informational message.
"That option is unavailable, this menu accessed via the Interrupt menu"
I did a test for V3.0 and V2.4 and same behaviour, Customer is pretty
confident that this GOLD I worked in V2.3.
Could anyone please confirm this.....
Thanks
ricardo
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3319.1 | Intentional (I think!) | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Fri Sep 24 1993 14:26 | 4 |
I think we forbade the option during GOLD/I to stop problems with
reentering the editor.
Graham
| |||||
| 3319.2 | Yabbut,If no conflict GOLD I works ! | KAOFS::R_OBAS | Fri Sep 24 1993 16:12 | 7 | |
The user just want to view the calendar via GOLD I from EM. Do we
actually enter the editor just from reading an invitation ,then if
there is a conflict , user wants to see what the conflict GOLD I
does not work. If there is no conflict GOLD I works just fine.
| |||||
| 3319.3 | Pending the arrival of the Dead Products Consultnat... | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Thu Sep 30 1993 23:28 | 10 |
I think the problem is that we don't know when the meeting request
arrives what you are going to do with it. You might choose to answer it
and then want to enter the editor to add some text to your reply.
Because we can't (at that point) unwind the meeting request back into
the INBOX to get it processed again later, we have to take the worst
case and forbid it all the time.
I think :-)
Graham
| |||||