IBM Support

LO85798: MULTIPLE ACCEPTS FOR REPEATING EVENT THAT ONLY HAS PARENT DOCUMENT, NO CHILD DOCUMENTS.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • Repeating events normally are represented in Domino with a
    parent document and child document(s) where the child
    document(s)
    represent the actual instances on the calendar. Repeating
    events
    can get corrupted such that they may only have the parent
    document (no child documents) and the instances
    (CalendarDataTime field) is on the parent document. In this
    case Traveler does not handle sending the device (attendee)
    their status (accepted/tentative), instead it is always
    sends 'needs
    action'. So no action buttons (accept, etc) are highlighted on
    the iOS device. This may be confusing to the user, they think
    they have accepted but the device does not reflect that. So they
    may try to accept again, etc..
    The chair may get multiple accept notices.
    Traveler needs to check for this format of event documents and
    handle
    sending the correct status if the $BusyPriority field is
    available on the parent document.
    
    Fix also includes checking for this format of event to prevent
    (ignore)
    multiple replies of the same state (multiple accepts to chair).
    This can happen when user accepts event already accepted or iOS
    device gets in loop for some reason repeatedly sending accept
    notices.
    

Local fix

Problem summary

  • If a repeating event would become corrupted, the user may always
    see "Needs Action" on the event on their Traveler device.
    
    The chair may also get multiple accept notices.
    

Problem conclusion

  • The Notes Traveler Server was updated to prevent this scenario
    from happening.
    

Temporary fix

Comments

APAR Information

  • APAR number

    LO85798

  • Reported component name

    LOTUS NOTES TRA

  • Reported component ID

    5724E6204

  • Reported release

    901

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-07-24

  • Closed date

    2015-08-18

  • Last modified date

    2015-08-18

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

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

Fix information

  • Fixed component name

    LOTUS NOTES TRA

  • Fixed component ID

    5724E6204

Applicable component levels

  • R901 PSY

       UP



Document information

More support for: IBM Traveler

Software version: 9.0.1

Reference #: LO85798

Modified date: 18 August 2015