| Hi
I found some failer in the LNX322MA Client
1. About LinkWorks:
==================
add also the time in the User Info, please.
Login time: Monday, 7. April 1997
Logout time:
----> Is being solved
2. LNXDUA:
=========
can't close the lnxdua it is starting again ig you close
the lnxdua. The lnxdua is startet in a distribution list.
The add function is also not correct working. In the KB
release it was ok. It is also looping if you End Task for
LNXDUA.
Im missing also a search base for the lnxdua. We have three
Customer with a worldwide x.500. That means lnxdua search on
the top from the x.500.
---> we will look into it
3. Mail Setup:
===========
The absent from has not date preconfigured
---> will not be changed (in future it will be as in WorkFlow)
4. MailInbox:
==========
Reply dosen't works in Open Envelop from Event Manager
show message. Only after it was read normaly in the MailInbox
(E196): Parent object of Open Envelope "User" must be specified.
---> more info needed, because we are not able to reproduce
Thanks Toni
|
| Hi
I found some failer in the LNX322MA Client
1. About LinkWorks:
==================
add also the time in the User Info, please.
Login time: Monday, 7. April 1997
Logout time:
----> Is being solved
2. LNXDUA:
=========
can't close the lnxdua it is starting again ig you close
the lnxdua. The lnxdua is startet in a distribution list.
The add function is also not correct working. In the KB
release it was ok. It is also looping if you End Task for
LNXDUA.
---> will be solved
Im missing also a search base for the lnxdua. We have three
Customer with a worldwide x.500. That means lnxdua search on
the top from the x.500.
---> new requirement, please forward that requirement to marketing
3. Mail Setup:
===========
The absent from has not date preconfigured
---> will not be changed (in future it will be as in WorkFlow)
4. MailInbox:
==========
Reply dosen't works in Open Envelop from Event Manager
show message. Only after it was read normaly in the MailInbox
(E196): Parent object of Open Envelope "User" must be specified.
---> reproducable here, a Problem report has been written
Thanks Toni
|