RRC - Reqpro integration
I have integrated rrc project and Reqpro project.
1. I have created a requirement in reqpro and imported that requirement to RRC. I have done modifications in that requirements in req pro. The change is not getting reflected in RRC.
2. I have done modification to that requirement in RRC. And that requirement becomes read only in reqpro. But the modifications are getting reflected in Reqpro.
Is this the nature of the integration?
1. I have created a requirement in reqpro and imported that requirement to RRC. I have done modifications in that requirements in req pro. The change is not getting reflected in RRC.
2. I have done modification to that requirement in RRC. And that requirement becomes read only in reqpro. But the modifications are getting reflected in Reqpro.
Is this the nature of the integration?
2 answers
I have integrated rrc project and Reqpro project.
1. I have created a requirement in reqpro and imported that requirement to RRC. I have done modifications in that requirements in req pro. The change is not getting reflected in RRC.
2. I have done modification to that requirement in RRC. And that requirement becomes read only in reqpro. But the modifications are getting reflected in Reqpro.
Is this the nature of the integration?
In the RRC Project Adminstration page, when the connection to the RequisitePro project is made you must also choose whether changes are pulled/pushed between the two. If you want two-way updates then both must be checked.
If changes are not being reflected in RRC, then check that the Synchronization (see help) parameter value, in the RRCS fronting.properties file is NOT set to false.
com.ibm.rdm.fronting.server.synchronizing=false
Also RequisitePro needs to use either Oracle, DB2 or SQL Server, as well as Project Security.
Now RRC supports Rich Text, but RequisitePro client does not - so if Rich Text changes are pushed from RRC to RequisitePro, the text becomes read only in RequisitePro as the rich text editor is only available in RRC.
Now you can make changes to requirements attributes in both RequisitePro and RRC.
I hope this helps.