IBM Support

PI38761: Bulk transitions fails when one or more related CRs are not in required state

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Abstract:
    Change request bulk transition fails if one of more child-CRs
    are not in a required state
    
    Error Description:
    Attempts to bulk transition change requests fails for all CRs if
    one or more child CRs are not in a required state, without
    indication as to which child CR are not in a required state.
    
    Steps to reproduce:
    1)  Edit the process by adding two attributes 'child_CR' and
    'has_child_CR', Web-Type 'CCM_RELATION'.
    2)  Edit transition 'assigned2resolved' by adding this
    pre-transition trigger:
    'verify: bsf verify_related_change_request_states.js child_CR
    probreject canceled duplicate resolved tested concluded'
    3)  Install new process
    4)  As Change user create 6 new CRs, linking 3 pairs as
    parent-child using above new attributes.
    5)  Set the three parent CRs into state 'assigned' and only one
    of the child CRs to state 'resolved'.
    6)  Run a report that returns the three parent CRs.
    7)  Select these three CRs and select ' Transition'.
    
    Expected result:
    One CRs is successfully transitioned while the two other CRs are
    reported as not having met the pre-transition requirement.  A
    pop-up message indicates which CRs have or have not been
    transitioned.
    
    Actual result:
    None of the CRs are transitioned.
    
    Local Fix:
    Transition one CR at a time or try to use smaller sub-groups of
    CRs for bulk transition.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All platform user                                            *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Abstract:                                                    *
    * Change request bulk transition fails if one of more          *
    * child-CRs are not in a required state                        *
    *                                                              *
    * Error Description:                                           *
    * Attempts to bulk transition change requests fails for all    *
    * CRs if one or more child CRs are not in a required state,    *
    * without indication as to which child CR are not in a         *
    * required state.                                              *
    *                                                              *
    * Steps to reproduce:                                          *
    * 1)  Edit the process by adding two attributes 'child_CR' and *
    * 'has_child_CR', Web-Type 'CCM_RELATION'.                     *
    * 2)  Edit transition 'assigned2resolved' by adding this       *
    * pre-transition trigger:                                      *
    * 'verify: bsf verify_related_change_request_states.js         *
    * child_CR probreject canceled duplicate resolved tested       *
    * concluded'                                                   *
    * 3)  Install new process                                      *
    * 4)  As Change user create 6 new CRs, linking 3 pairs as      *
    * parent-child using above new attributes.                     *
    * 5)  Set the three parent CRs into state 'assigned' and only  *
    * one of the child CRs to state 'resolved'.                    *
    * 6)  Run a report that returns the three parent CRs.          *
    * 7)  Select these three CRs and select ' Transition'.         *
    *                                                              *
    * Expected result:                                             *
    * One CRs is successfully transitioned while the two other CRs *
    * are reported as not having met the pre-transition            *
    * requirement.  A pop-up message indicates which CRs have or   *
    * have not been transitioned.                                  *
    *                                                              *
    * Actual result:                                               *
    * None of the CRs are transitioned.                            *
    *                                                              *
    * Local Fix:                                                   *
    * Transition one CR at a time or try to use smaller sub-groups *
    * of CRs for bulk transition.                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • This issue is fixed. Fix will be available with the next planned
    release of Rational Change 5.3.1.1.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI38761

  • 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-04-09

  • Closed date

    2015-09-28

  • Last modified date

    2015-09-28

  • 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:
15 October 2021