IBM Support

JR45348: UNABLE TO REMOVE DATES AFTER SAVED IN COACH

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Unable to remove dates after saved in coach
    

Local fix

  • n/a
    

Problem summary

  • Data entered in the Date selector via keyboard is not submitted
    if boundary event occurs without Date selector focus lost.
    
    USER AFFECTED:
    End users of Coaches using Date selectors with IE7 and IE8
    
    PROBLEM DETAILED DESCRIPTION:
    Root cause is a timing issue with IE7/IE8 browser's event
    handling, between when the onChange executes of the
    DateTimePicker and the form being submitted.
    
    Reproduction steps,
    1) Requires a Human Service with two consecutively chained
    Heritage Coach each containing a Date Selector control. The
    first Coach will contian a Next Button control which will cause
    the second Coach to display. The second Coach will contain a
    Back Button control which will cause the first Coach to display.
    Appropriate variables and bindings need to be defined to store
    and retrieve a date value.
    2) Run the containing Human.
    3) Select a date in Date Selector control in the first Coach,
    then click Next Button control.
    4) The same date will be observed in the Date Selector control
    in the second Coach.
    5) Remove the date using backspace or delete key in this second
    Coach.
    6) Click Back Button control.
    Result: Observe the original selected date is displayed in first
    Coach
    Expected Result: No date is displayed in first Coach.
    

Problem conclusion

  • Resolved the timing issue by changing the CoachDesigner.xsl file
    to generate different Javascript code for Buttons.
    
    ATTENTION: When buttons are clicked programmatically during
    window.onunload or window.onbeforeunload (or the dojo
    equivalent) the usage of the timers will prevent the click logic
    from being invoked. Because the page being unloaded when the
    timer is set and the page is destroyed before the timer is
    invoked. So only in these scenarios would the
    "window._BPM_skipTimer = true;" need to be set so the click
    logic is invoked directly. Following snippet demonstrates this
    logic,
    
    window._BPM_skipTimer = true;
    dojo.byId("ButtonGroup_Button_Submit").click();
    try {
     window._BPM_skipTimer = false;
     delete window._BPM_skipTimer;
    } catch (ex) {
    }
    
    FIX AVAILABILITY:
    For 7.5.1.0, this fix is available as an interim fix for 7.5.1
    Fixpack 1 (7.5.1.1), and can be obtained from Fix Central,
    http://www.ibm.com/support/fixcentral/ . Search for JR45348.
    
    For 8.0.1.0, this fix has been included with 8.0.1 Fixpack 1
    (8.0.1.1).
    
    When downloading fix packages, ensure that you also download the
    readme file for each fix. Review each readme file for additional
    installation instructions and information about the fix.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR45348

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    751

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-01-11

  • Closed date

    2013-01-30

  • Last modified date

    2014-01-29

  • 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

    BPM ADVANCED

  • Fixed component ID

    5725C9400

Applicable component levels

  • R751 PSY

       UP

  • R801 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
12 October 2021