IBM Support

PI42625: SECTIONAL PAGE NAVIGATION NOT BEHAVING AS EXPECTED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When sectional page navigation is implemented in the lifecycle,
    it is not behaving as expected.
    
    Example 1:
    
    1. In a given state, there are three main sections, with page
    navigation intended for each of these main sections.
    For example:
    A
    B
    C
    
    2. Each section itself would contain two subsections, but it is
    not intended to have page navigation to these sub sections.
    A.1
    A.2
    B.1
    B.2
    C.1
    C.2
    
    
    When the user clicks on page navigation for A, it goes to A as
    expected.
    When the user clicks on page navigation for B, it should go to
    B. However it does to A.1.
    
    
    Example 2:
    
    You have three expanded sections followed by a large section
    which is not expanded. Sectional Navigation is implemented for
    all three.
    A.
    B.
    C.
    
    The user clicks on page navigation for C, whereby C is expanded
    but the start of C appears in the middle of the screen rather
    the top.
    
    
    Example 3.
    
    It is not possible to navigate to an inner section which is
    inside an outer section if the outer section is not first
    expanded.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Users for all platforms                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When sectional page navigation is implemented in the         *
    * lifecycle,                                                   *
    * it is not behaving as expected.                              *
    *                                                              *
    * Example 1:                                                   *
    *                                                              *
    * 1. In a given state, there are three main sections, with     *
    * page                                                         *
    * navigation intended for each of these main sections.         *
    * For example:                                                 *
    * A                                                            *
    * B                                                            *
    * C                                                            *
    *                                                              *
    * 2. Each section itself would contain two subsections, but it *
    * is                                                           *
    * not intended to have page navigation to these sub sections.  *
    * A.1                                                          *
    * A.2                                                          *
    * B.1                                                          *
    * B.2                                                          *
    * C.1                                                          *
    * C.2                                                          *
    *                                                              *
    *                                                              *
    * When the user clicks on page navigation for A, it goes to A  *
    * as                                                           *
    * expected.                                                    *
    * When the user clicks on page navigation for B, it should go  *
    * to                                                           *
    * B. However it does to A.1.                                   *
    *                                                              *
    *                                                              *
    * Example 2:                                                   *
    *                                                              *
    * You have three expanded sections followed by a large section *
    * which is not expanded. Sectional Navigation is implemented   *
    * for                                                          *
    * all three.                                                   *
    * A.                                                           *
    * B.                                                           *
    * C.                                                           *
    *                                                              *
    * The user clicks on page navigation for C, whereby C is       *
    * expanded                                                     *
    * but the start of C appears in the middle of the screen       *
    * rather                                                       *
    * the top.                                                     *
    *                                                              *
    *                                                              *
    * Example 3.                                                   *
    *                                                              *
    * It is not possible to navigate to an inner section which is  *
    * inside an outer section if the outer section is not first    *
    * expanded.                                                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Fix is available in next planned interim fix release for
    Rational Change 5.3.1.1
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI42625

  • Reported component name

    TLOGIC CHANGE

  • Reported component ID

    5724V87CG

  • Reported release

    531

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-06-09

  • Closed date

    2015-12-22

  • Last modified date

    2015-12-22

  • 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

    TLOGIC CHANGE

  • Fixed component ID

    5724V87CG

Applicable component levels

  • R531 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYQQ2","label":"Rational Change"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"531","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 October 2021