| |
Results |
|
DIM CM 2009 R1: Error when creating a base database on SQL Server 2005
|
[Microsoft][SQL Native Client][SQL Server]The specified schema name "TEST2" either does not exist or you do not have permission to use it. Error detected in E:\Program Files\Serena\Dimensions 2009 R1\CM\dbms\mssql\translated\mssql_create_base_tables.sql, line 14 Called from E:\Program Files\Serena\Dimensions 2009 R1\CM\dbms\common\setup_base_database.sql, line 279
|
|
|
|
AddObjectToCollection Web Service doesn't return an error if you specify a collection that doesn't exist
|
The scenario can be if you use a valid sessionId for a different DB than the one you intended. If the object to be added to the Collection exists but the Collection doesn't exist, the web service does nothing and returns a "Success" rather than returning an error.
|
|
|
|
DIM12: Oracle 11 runtime installation does not create instance if DB location different to binaries location
|
The Serena Oracle 11 x64 runtime installation does not created the instance if during the installation a different location is specified for the DB files to the Oracle binaries. The installer asks for the installation location first and later on for the location of the actual database files. If you choose two locations on different drives then the installation will run through but the instance never gets created.
|
|
|
|
Long ts_internalname and/or ts_name doesn't work with AppScript with Oracle db
|
When referencing ts_name or ts_internalname in ts_states with an app script, if either is over 30 characters, it fails with "ORA-00972:Identifier is too long" which is due to an Oracle limitation. It appears we accommodate this limitation in other areas in Composer when creating names /internal names , States can still be created with long names /internal names .
|
|
|
|
Javascript: Form Validation does not work when two fields have the same display name
|
Example to reproduce: 1) Create a transition form with two text fields with the same display name (different db name ), make sure both are required 2) Enable form validation feature for this form
|
|
|
|
12.2.2.1 / Build => impacted targets not found when /TARGETS symbol is not specified int he BLD command
|
but the build doesn’t find all the targets in the build configuration . If you set up two targets with the same name and specification, these can each be fore quite distinct build plans For example
|
|
|
|
12.2.2.1 : Error when deleting a stream which has the same name in 2 products
|
DS "S1" COR4300107E Error: The stream specified - 'S11' - does not exist in the product => if you try to delete the stream in a third stream, it doesn't delete the expected the stream
|
|
|
|
12.2.2.1 : Error when deleting a stream which has the same name in 2 products
|
DS "S1" COR4300107E Error: The stream specified - 'DIME1' - does not exist in the product => if you try to delete the stream in a third stream, it doesn't delete the expected the stream
|
|
|
|
25 Character limit on names of Deployment Owner
|
When specifying a Deployment Owner during initial setup of a Deployment area, we are given an error stating that the name of the owner cannot be longer than 25 Characters. Currently it possibly to create names or both users and groups with names longer than 25 characters.
|
|
|
|
DIm CM 12.2: The use of --stream with the dm deliver command doesn't override default stream value
|
"--stream <stream_name> Specifies the name of the stream to update the work area from. If it is not specified, then the current stream will be used.
|
|
|
