LO48996: ATTACHMENTS NOT RETRIEVED FROM EMBEDDEDOBJECTS METHOD IN LOTUS S CRIPT

APAR status

• Closed as fixed if next.

Error description

• In a mail database while trying to get attachments from a mail
  file thru a
  lotus script agent, the method embeddedObjects returns nothing
  from an RTItem
  and also from the NotesDocument object.
  The same agent works correctly in R7 while processing the same
  document.
  
  The issue occurs only to some specific document the customer
  gets from
  internet. In attachment is possible to find a sample database
  including the
  Lotus Script agent and a document to process. To reproduce the
  case, follow the
  steps below:
  
  download the db attached;
  place the db in the data directory of the notes client;
  if your preview windows is active in the client disable it for
  the test,
  opening the document in the database will mark it like processed
  preventing the
  agent to work;
  open the mail database;
  from the menu action execute the agent called "getAttachments"
  2 message boxes will inform you about the result
  
  the code used in this case to process the document is the
  following:
  
  Dim session As New NotesSession
  
  Dim db As NotesDatabase
  Set db = session.CurrentDatabase
  Dim collection As NotesDocumentCollection
  Set collection = db.GetAllUnreadDocuments
  Dim doc As NotesDocument
  Set doc = collection.GetFirstDocument
  While Not doc Is Nothing
   If Not doc.HasEmbedded Then
    Print "no items found"
   Else
    Dim rtitem As NotesRichTextItem
    Set rtitem = doc.GetFirstItem( "Body" )
  
    Dim rtArr As Variant
    rtArr = rtitem.EmbeddedObjects
  
    Dim docArr As Variant
    docArr = doc.EmbeddedObjects
  
    If Isempty(rtArr) Then
     Print "rtArr is empty"
    End If
    If Isempty(docArr) Then
     Print "docArr is empty"
    End If
   End If
   Set doc = collection.GetNextDocument(doc)
  Wend
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• This APAR is associated with SPR# CTOO7S7GK4.
   Support should continue to log customer reports against this
   SPR.  If weight increases sufficiently, it may be re-raised
   for triage for an upcoming maintenance or feature release.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

• R801 PSN

     UP