IBM Support

PK92530: Notification trigger in ECP process should use the concluded_id attribute, not concluder.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • In the the Change 5.2 ECP process definition concluded_id is the
    attribute dealing with the 'Person who transitioned the CR to
    the concluded state'.
    
    However, the transition notification trigger when reaching the
    concluded state contains a mistake.
    
    The concluder attribute is listed. However this attribute is not
    used in the ECP Process CR/PR lifecycle. It should be replaced
    by concluded_id.
    

Local fix

  • Manually edited the CRAssignEmail.pl to add the correct attr
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Notification trigger in ECP process should use the concluded_id
    attribute, not concluder.
    

Problem conclusion

  • Fixed in Rational Change 5.3.
    

Temporary fix

Comments

  • Updated the notification triggers in ECP process by replacing 'c
    oncluder' attribute with the valid 'concluded_id' attribute.
    Removed the 'concluder' attribute from the ECP process as it is
    a duplicate of the attribute 'concluded_id'.
    

APAR Information

  • APAR number

    PK92530

  • Reported component name

    TLOGIC CHANGE

  • Reported component ID

    5724V87CG

  • Reported release

    520

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-07-28

  • Closed date

    2010-08-31

  • Last modified date

    2011-04-28

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

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

Fix information

Applicable component levels

  • R520 PSN

       UP

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

Document Information

Modified date:
28 April 2011