B

Working with Rational RequisitePro

This appendix describes notes and limitations specific to synchronizing requirements between Quality Center and Rational RequisitePro.

This appendix includes:

➤Guidelines for Working with Rational RequisitePro on page 121

➤RequisitePro Connection Properties on page 122

➤Migrating to the Quality Center Synchronizer on page 123

Guidelines for Working with Rational RequisitePro

When working with the Synchronizer, make sure that you follow these guidelines:

➤Record creation will fail during synchronization if you use the following characters when naming a requirement in Quality Center, or when naming a project, package, or requirement in RequisitePro: \ ^ * “ : ‘

➤For synchronization with a RequisitePro project located on a network drive, the user configured to log on as a service for the Synchronizer must have permissions to access the network location.

➤In Quality Center, if you want to move a requirement and make it a child of another requirement, make sure that you move it under a requirement of the same type. This is required because RequisitePro does not allow you to place a requirement of one type under a requirement of another type.

➤RequisitePro Real, Time, and Userlist type fields are defined as String type in Synchronizer field mappings.

121