IBM Support

LO70722: USING JAVA AGENT TO UPDATE XPAGES CURRENT DOCUMENT

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

  • Customer stated:
    In our XPages application we need to call a Java Agent that will
    update the
    current document.
    
    We have a button with the following code :
    
    -----------------------------------------------
     document1.save();
    
     var ag = database.getAgent("WKF");
     ag.run(document1.getNoteID());
     _dump("AFTER AGENT 1 : " +
    document1.getItemValueString("Langage"));
    context.redirectToPage("Demande.xsp?documentId="+document1.getDo
    cument().getUniv
    ersalID() + "&action=openDocument");
    --------------------------------------
    
    The agent will only set the Langage value with a time stamp
    (This is just for
    the purpose of the PMR, in our real application we use the java
    agent to call a
    workflow engine).
    The dump will display the value of Language BEFORE the document
    has been
    modified by the agent. It should display the new value. When the
    XPage
    refreshes after the redirect, it is the new value which is
    displayed. But we
    need to have the new value in the code juste after the agent
    because we need to
    send it by email.
    
    Steps to reproduce:
    1. Open the XPage Demande.xsp
    2. click on Save and then click on TEST.
    3. Go to the server console you will see that the value set
    after the launch of
    the agent has not changed.
    4. But when the page refreshes, we get the new value.
    

Local fix

Problem summary

  • A programming error was found and will be corrected in a future
     release.
    

Problem conclusion

  • A programming error was found and will be corrected in a future
     release.
    

Temporary fix

Comments

  • This APAR is associated with SPR# BANN8D2B3D.
    A programming error was found and will be corrected in a future
     release.
    

APAR Information

  • APAR number

    LO70722

  • Reported component name

    NOTES CLIENT

  • Reported component ID

    5724E6255

  • Reported release

    853

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-07-24

  • Closed date

    2012-08-03

  • Last modified date

    2012-08-03

  • 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

    NOTES CLIENT

  • Fixed component ID

    5724E6255

Applicable component levels

  • R853 PSN

       UP

[{"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Product":{"code":"SSKTWP","label":"Lotus Notes"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5.3","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 August 2012