LO73440: INVALID BODY IN GERMAN REPLY WHEN USING OOO C API

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

  • You enable the Out of Office using the OOO C APIs for a German
    mail user. When the Out of Office replies, the body of the
    reply is incorrect. The return date is actually the leaving
    date.
    Example:
    Leaving date: 01/10/2013
    Return date: 01/26/2013
    Body: Ich werde ab  01/10/2013 nicht im Bro sein. Ich kehre
    zurck am 01/10/2013.
    

Local fix

Problem summary

  • When using OOO API's via Notes API toolkit, "daysoutdisplay"
     was never calculated, making foreign mail users to have a
     stale field, which is why it is wrong.  To resolve this we set
     "daysoutdisplay" to "", and ComputeWithForm a copy of the
     profile to have "DaysOut" calculated instead.  Then we replace
     "DaysOut" in original Profile, with the one calculated in
     copy.  OOO Service will use "DaysOut" when there is no value
     in "daysoutdisplay", in so resolving this issue.   This is 1
     of 2 fix, we also need a Template side fix to correct the
     formula behind "DaysOut".   Latest change regarding Beam
     complaint.
    

Problem conclusion

  • When using OOO API's via Notes API toolkit, "daysoutdisplay"
     was never calculated, making foreign mail users to have a
     stale field, which is why it is wrong.  To resolve this we set
     "daysoutdisplay" to "", and ComputeWithForm a copy of the
     profile to have "DaysOut" calculated instead.  Then we replace
     "DaysOut" in original Profile, with the one calculated in
     copy.  OOO Service will use "DaysOut" when there is no value
     in "daysoutdisplay", in so resolving this issue.   This is 1
     of 2 fix, we also need a Template side fix to correct the
     formula behind "DaysOut".   Latest change regarding Beam
     complaint.
    

Temporary fix

Comments

  • This APAR is associated with SPR# OIHZ93TRRY.
    When using OOO API's via Notes API toolkit, "daysoutdisplay"
     was never calculated, making foreign mail users to have a
     stale field, which is why it is wrong.  To resolve this we set
     "daysoutdisplay" to "", and ComputeWithForm a copy of the
     profile to have "DaysOut" calculated instead.  Then we replace
     "DaysOut" in original Profile, with the one calculated in
     copy.  OOO Service will use "DaysOut" when there is no value
     in "daysoutdisplay", in so resolving this issue.   This is 1
     of 2 fix, we also need a Template side fix to correct the
     formula behind "DaysOut".   Latest change regarding Beam
     complaint.
    

APAR Information

  • APAR number

    LO73440

  • Reported component name

    DOMINO SERVER

  • Reported component ID

    5724E6200

  • Reported release

    853

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-01-10

  • Closed date

    2014-05-16

  • Last modified date

    2014-05-16

  • 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

    DOMINO SERVER

  • Fixed component ID

    5724E6200

Applicable component levels

  • R853 PSN

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

IBM Domino

Software version:

8.5.3

Reference #:

LO73440

Modified date:

2014-05-16

Translate my page

Machine Translation

Content navigation