IBM Support

PM07436: ReqPro/RQM Integration - Changes made in ReqPro Client are not s ync'd with RQM until requirement is first accessed via Reqweb

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • the problem appears to be that
    requirement changes made in the Reqpro client are not captured b
    y the REST API until after the requirement is opened in ReqWeb f
    irst.
    
    This causes changes made in the ReqPro client to not be recogniz
    ed in RQM.
    

Local fix

Problem summary

  • Requirements modified via ReqPro Client are not synchronized
    with RQM until requirement is first accessed via Reqweb
    

Problem conclusion

  • A requirements refresh was forced in RequisitePro before
    passing out the requirements info to RQM
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM07436

  • Reported component name

    REQUISITEPRO WI

  • Reported component ID

    5724G3900

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-02-11

  • Closed date

    2010-06-24

  • Last modified date

    2010-06-24

  • 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

    REQUISITEPRO WI

  • Fixed component ID

    5724G3900

Applicable component levels

  • R710 PSN

       UP

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

Document Information

Modified date:
24 June 2010