IBM Support

IV91760: RETIRED HIERARCHY CODES ARE NOT BEING HIDDEN WHEN SELECTING HIDE STATE IN HIERARCHY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • You want to hide records in a hierarchy of a certain state.
    For example, you want to hide locations that are in a Retired
    State.  When you go to the Data Modeler and for triLocation, go
    to State Transitions and for triRetired, select Hide state  in
    hierarchy.   Then Publish the BO.
    
    If you have the following hierarchy
    Bldg1
    bldg1-Flr1
    bldg1-Flr1-space1
    bldg1-Flr1-space2
    
    and you retire space1, it is still visible in the hierarchy and
    it should not be visible.
    
    When that checkbox for Hide State in Hierarchy in the Data
    Modeler is used, that should hide those states from being seen
    in the hierarchy.
    

Local fix

Problem summary

  • Issue only happens on MSSQL and DB2 because they have different
    sql (Union All) vs oracle sql to get all the children in
    hierarchy.
    

Problem conclusion

  • Records with hidden states are no longer  displayed in
    hierarchy if they are more than 1 level deep.
    This is targeted to the 1h2017 release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV91760

  • Reported component name

    TRI APPLCATION

  • Reported component ID

    5725F26AB

  • Reported release

    351

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-01-03

  • Closed date

    2017-01-04

  • Last modified date

    2017-01-04

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

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

Modules/Macros

  • 999
    

Fix information

Applicable component levels

  • R352 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSHEB3","label":"IBM TRIRIGA Application Platform"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"351","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
30 March 2022