database=@<SID> After commenting this line out and restarting Dimensions the messages were gone. By default the deploy_config.dat should not include any settings.
After upgrading suite version to 4.0.1 (Development Manager, Requirement Manager or Release Manager) or installing RM 12.1 you will need to reinstate your Dimensions CM 2009 R2 - 12.2.1 web applications into the new Tomcat. If you are already using Dimensions CM 12.2.2 then no additional steps are necessary.
On some base databases that have been upgraded from a previous version of Dimensions users have reported that when trying to edit or create a selection criteria for a release or baseline template in the Adminconsole it shows "Loading..." as a value for the fields State/Stage and Additional rule.
- Developer does a check-out of the same item and Dimensions overwrites the changes with no warning. Please, bear in mind that upgrade to Dimensions 12 is not an option for customer; so Kutxa is asking for a workaround or solution based in Dimensions 2009R2. 3. What is the expected result?
1. Describe the problem & the customer's use case scenario? Customer's trigger has stopped working since they upgraded to 12.2 2. What are the steps to reproduce the problem? The following source code demonstrates the issue.
