| |
Results |
|
Dim RM 11.2.4: A script alert is generated when running IE 8 for long running queries
|
This problem is reproducible using IE8 but not Firefox or IE9. This problem is data dependent so the more attributes and larger valid lists you have the more likely it is that this script alert will be generated. The user can just keep choosing to run the script and eventually the values will be returned.
|
|
|
|
Dim RM 2010 R1: Running a script with syntax errors may result in an rmAppServer crash
|
Dim RM 2010 R1: Running a script with syntax errors may result in an rmAppServer crash
|
|
|
|
HotFix for "Runtime Error" returned when trying to run a Traceability report or in queries like filters or scripts under Dimensions RM 10.1.3 using Oracle 10g.
|
A "Runtime Error" will be returned when trying to run a Traceability report. It could also happen when trying to execute Filters or Scripts under RM 10.1.3 using Oracle 10g.
|
|
|
The doc_out tool allows you to run an RTM reporting script from the command line and to generate the output to a variety of formats
|
The doc_out tool allows you to run an RTM reporting script from the command line and to generate the output to a variety of formats. Using doc_out enables you to extract data from RTM Workshop without invoking a Windows-based RTM session. Scripts can be prepared before extraction for batch processing of reports.
|
|
|
|
Large Documents cause Script warning on large documents when moving requirements
|
Large Documents cause Script warning on large documents when moving requirements For a large document with many requirements, in document view, we are drag/dropping requirements objects to create a requirement hierarchy. (e.g. requirement 4.1 as a component under requirement 4). For this large document, each drag/drop takes a long time and we get a pop-up saying that the script is running slowly.
|
|
|
|
RM Install: The RM install media must provide access to setup SQL scripts without running the installation
|
RM Install: The RM install media must provide access to setup SQL scripts without running the installation All SQL scripts used to configure RM or integration systems must be provided without the need to install RM first. In the install media provide a copy of SetupDatabase.bat, setupRM.SQL, and all other SQL that may require a DBA or system admin to run . This is required at most large customers that have a dedicated DBA department which must setup the database independently of the Windows department.
|
|
|
|
New setupRTM.sql script for running on Oracle 9.2.0.7.0
|
-- RTM V5.3.5 Oracle9i setup script. This script must be run as the Oracle sys user.
|
|
|
|
RM Script Syntax Errors with Mixed case KEY words
|
TITLE from Component_Requirements ## comment where STATUS in ('Current') order by PUID calculate all count[Row Count:]PUID For key words: SELECT, FROM, WHERE, ORDER, BY, and possible others if they are mixed case they do NOT work and generate a syntax error. If the key words are lowercase or UPPERCASE the scripts run correctly.
|
|
|
|
RM ignores column widths from the script, if script contains PLUS statement
|
If you are running a report and edit the script to specify column widths for the selected attributes and include a “PLUS” statement to add a new selection, RM will not honor the column widths you specify. Dimensions RM will determine the appropriate column widths for the report. There is no known work around at this time.
|
|
|
|
DIM RM: Permissions on Scripts do not work properly
|
Situation: 1. User1 creates a script – this will be private and he (and only he) can see and run this script This is implicit read permission for the creator of a script
|
|
|
