APAR status
Closed as Permanent restriction.
Error description
A New Task created using DAMO creates a Notes To Do document with incorrect "Required" or assignee field. User creates many To Do documents and assigns them to people to complete. The name of the user that creates the Task/To Do should go in the Owner field - chair, principal. The name of the user that it is assigned to should go in the AssignedTo field - AltRequired. ENVIRONMENT : Running 8.5 Notes Client with Outlook 2007 DAMO 8.0.2 IF4. - The customer provided screenshots of recreate scenario: Uploaded to SPR attachment db. Also uploaded to FTP Server and stored in ECuRep: /ecurep/pmr/3/6/36614,227,000/36614.227.000damoerror.doc - When I create the task and assign it to someone, the recipient of the task does not get notified. If I look at the task in Notes it shows as the creator ( Owner ) as me, and the person it is assigned to ( Required ) as me also. The Required field should be the user I assign the To Do / Task to. 1. Create a new task using DAMO 2. Select / Assign Task 3. Enter Assignee data 4. Press send. 5. When you go to Notes to view the task, you see the following Tasks created using DAMO has the wrong name in the Required field ( note using fake user names here ) Owner : Tom Smith( sent by Rebecca ) Required : Tom Smith/Acme@Acme Tasks created with Notes client shows correct name in the Required field Owner : Tom SMith Required : Amanda Public/Acme@Acme THEORIES : incorrect field mapping by DAMO Could not recreate on Notes, or at IBM with DAMO and Outlook 2003 Business Case : Admin/customer very interested in using DAMO Management are heavy Outlook users - they want to switch to Exchange servers
Local fix
use Notes client to create To Do document.
Problem summary
This problem was resolved as: No Plans to Fix Ever
Problem conclusion
This problem was resolved as: No Plans to Fix Ever
Temporary fix
Comments
APAR Information
APAR number
LO40151
Reported component name
NOTES/DOMINO 7X
Reported component ID
5724E6200
Reported release
801
Status
CLOSED PRS
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-05-01
Closed date
2009-05-29
Last modified date
2009-05-29
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
NA
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Product":{"code":"SSKTMJ","label":"Lotus Domino"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
29 May 2009