/ Forums / Advansys Formativ / Creating Solutions with Formativ / Setting destination fields to addresses with initials / Reply To: Setting destination fields to addresses with initials

June 2, 2005 at 6:58 pm #7189
Support 1a
Participant

    We spent some more time on this issue, and believe we have discovered two cause of the behavior. Whether or not Novell will see these as bugs I’m not sure.

    There are two scenarios where this behavior can be seen:

    1) Two Address Book entries with the same Display Name value, different email addresses

    The problem occurs when you have two address book entries that share the same Display name in different Address Books. One entry is a GroupWise user in the System address book, the other is an external user in a personal address book. This address book may or may not be in the name completion order.

    Use ItemSetText() to type the Display Name of the recipient into the TO field. Don’t set the focus to the TO field. When you try to send the message the recipient is crossed out.

    It appears the duplicate display names in different address books causes the resolution process to fail. Manually entering the same display name would appear to invoke an internal address book resolution lookup and the send is successful.

    2) External Email Address

    Define an address book entry in a personal address that has an external (non-GroupWise system) email address. Use ItemSetText() to type the Display Name of the recipient into the TO field. Don’t set the focus to the TO field. When you try to send the message the recipient is crossed out.

    In this case it appears address book entry resolution is not occurring. The send succeeds if the text you enter includes the external email address in brackets.

    While both scenarios are slightly different, the results suggest that in both cases using the ItemSetText() token does not cause the same recipient resolution process to occur that happen when the same text is typed manually into the TO field. Using ItemSetText() doesn’t cause the individual keystroke events to fire in the same way as when you manually enter text into the recipient box. I’m not sure whether Novell are going to view this as bug.

    Regards,

    Advansys Support