Product Documentation
Abstract
This document contains a complete listing of releases, refreshes, fix packs and interim fixes sorted by version for IBM Rational DOORS Requirements Management Framework.
Content
Tab navigation
- Release 6.1- selected tab,
- 6.0
- 5.4
- Support Resources
IBM Rational Software Support Communities
Helpful Hints For Obtaining Technical Assistance:
- Visit the IBM Support Portal to configure your support portal experience and review FAQs, lists of known problems, fixes, and a wealth of important support information.
- Visit developerWorks to access an online collection of tutorials, sample code, standards, forums and other resources provided by experts at IBM to assist software developers using Rational tools including access to the IBM RFE Community.
- Visit the Jazz Community if you use a Rational product created using the Jazz platform to interact directly with the Jazz development team and other community members, download product trials and betas and track development progress.
Helpful Hints For Obtaining Technical Assistance:
Before you contact IBM Rational Software Support, gather the background information that you need to describe the problem. When you describe a problem to an IBM software support specialist, be as specific as possible and include all relevant background information so that the specialist can help you solve the problem efficiently. To save time, know the answers to these questions:
- What software versions were you running when the problem occurred?
- Do you have logs, traces, or messages that are related to the problem?
- Can you reproduce the problem? If so, what steps do you take to reproduce it?
- Is there a workaround for the problem? If so, be prepared to describe the workaround.
If you have helpful information to diagnose or identify the problem on your system, you can provide this data by following the instructions to exchange information with IBM Technical Support.
Table of Contents:
| Link | Date Released | Status |
|---|---|---|
1 April 2016 | Current |
| Component | APAR | Description |
| API | PI52806 | The function probeAttr_ may generate DXL errors or return unexpected values if the file addins\irdrmfao\includes\api.inc is loaded during the startup. |
| Compare Module / Transfer Analysis | PI49102 | The API function "compareModules" cannot be bundled with the file addins/irdrmfao/includes/api.inc, otherwise the following DXL errors occur: -E- DXL: |
| PI54388 | Using DOORS 9.6.1.4, DXL errors occur when launching the tools "Compare Module" and "Transfer analysis". | |
| PI43477 | The following DXL error can occur when running the transfer -R-E- DXL: | |
| Create/Tag a RMF Project | PI53987 | Prevent from changing the definition of an enum attribute from multi-valued to single-valued if at least one value would be altered. |
| RMF now displays the errors and warnings that will prevent the synchronization from completing entirely before actually tagging or synchronizing the selected module(s) and ask confirmation. New API function API_CreateTagModules (please refer to RMF_API.pdf). | ||
| Since DOORS 9.4.0.1, all the attributes types have a URI, and enumerations also have a URI for each individual entry of the enumeration. RMF 6.1.0.9 now synchronizes this information (provided DOORS version 9.4.0.1 or higher is used). | ||
| RMF/synchronize may unduly report that a view is different in a module as compared to the same view in its template. | ||
| Dashboard | PI52115 | The result of the 'Count Linked Objects' metric is incorrect when the direction is set to "INOUT". The result should be the number of objects having at least one link no matter its direction. |
| A DXL error "unknown Module attribute (IE Metric UID Counter Increment)" can occur when creating a new metric specific to a module. | ||
| The "Configure Dashboard" does not record the list of metrics to be exported correctly. | ||
| DOC | PI45995 | The output of the command "Generate History of Document" is slightly different since RMF 6.1.0.6 as compared to the version 6.1.0.1. The history of baseline document versions used to exclude the objects whose state is "working". The API and the User Interface have been modified to enable to choose whether to include the "working" versions into the history of baseline document versions or not. |
| Baselining a document may be aborted with an error message "module is currently open". The name of the module that cannot be baselined should be displayed. | ||
| A DXL error may occur while baselining a document if some "working" objects are automatically completed and their Change Request(s) as well. | ||
| PI48688 | The command "Generate history of document" is much slower when integrated within the "Manage documents" window. | |
| Sort the documents by name by default. | ||
| Also record the time in the date of creation of a new document version. | ||
| PI58466 | Prevent the following error from occuring while saving the generation context after (after the modules of a document have been exported): "error opening conf file /DocMngr/.../views.txt for write Permission denied". | |
| Disable the "Version Name" field when its input is unecessary. | ||
| DOC properties whose attribute have a base type which is neither "string" nor "text" can now be exported as well. | ||
| Exchange | Prevent the import of modules from being interrupted by a popup message when tagging a module to warn that an enumeration is different in the imported module as compared to the template. | |
| PI50251 | Inherited values are exported as normal value. So the Inherited status is lost at import. | |
| Explorer | PI47598 | Unfriendly error message "module ... is not accessible" sometimes when running the command "RMF > Explore > Module". Explain (in the error message) the possible causes and actions to solve this issue, ie: - the module may not be displayed because it is out of the current scope => inactive the current scope - the module may have been created after the last time the internal cache has been updated => run the command "Refresh Project content" - the module is located in the Config folder |
| PI56226 | Unfriendly error message "module ... is not visible in current view" sometimes when running the command "RMF > Explore > Module". This can occur if the selected module cannot be displayed according to the current settings (list of templates / modules types to be displayed). Should that happen, offer the user to reset the options to default so that the module will not be filtered out. | |
| Using DOORS 9.5.2 and higher, the command "Linkset > Set all visible linksets as default linkset" in the Explorer displays an error message "This perm cannot be called inside the link module descriptors iterator". | ||
| Integrity Check | PI45546 | When a module is setup so that the Integrity Checks are run each time the module is closed down, the report is actually not recorded the first time the checks are run. |
| The status can sometimes abnormally become "CORRUPTED" instead of "JUSTIFIED" or "WARNING" or "ERROR". | ||
| kitchen | Increase the width of the source lists when resizing the dialog box and display the selected source and target modules in fields as well. | |
| Manage Objects | PI53459 | Do not duplicate the links defined as volatile (in the Project Profile) when duplicating an object (no matter which object it is or whether the module is controlled by RCM or not). |
| Volatile attributes should never be duplicated when duplicating a RCM controlled object. But this issue occurs when the "XML Source Ref" attribute is not empty on the object to duplicate and not modifiable by the current user. | ||
| PI55487 | Using DOORS 9.6.1.4, the text of objects merged using the "Join" button is missing line breaks and sometimes bullets. The same issue exists when merging and identifying several objects at the same time with the button "Identify". | |
| Miscellaneous | PI58034 | Incompatibility issue of RMF 6.1.0.8 with DOORS 9.3 up to 9.3.0.4 (included).The DXL error message below appears when launching DOORS: " |
| RCM | PI44664 | RCM sometimes leaves a Change Request open in exclusive edit and not displayed when an error occured while changing its status. |
| RCM may fail to change the status of a Change Request to "completed" if an impacted object has several "impact" links from modules with the same name. | ||
| New usercallout function RCM_UC_preChangeObjStatus enabling to prevent some objects from being switched back to "working" when a Change Request is reworked. This function is also called when a Change Request is completed, and then if it returns false for one object, the Change Request completion aborts. This function is defined in addins\irdrmfao\startup\usercallout\rcmusercallouts.inc. | ||
| When creating a new object version marked as suppressed (with the "Delete" button), the text of a new object may be incorrect if there are some backslash in the text of the previous version. The fix is implemented in the file addins\irdrmfao\startup\usercallout\rcmusercallouts.inc. If you have modified this file, please merge the modifications. | ||
| When double-clicking on an object, RCM may display a confirmation message offering to create a new version of that object. The checkbox "do not display this message anymore" enables to get rid of this confirmation message. A new radio button has been added to let the user decide which behaviour RCM should have if the confirmation message is discarded when double-clicking on an object: either edit the object (as currently) or create a new version with confirmation. | ||
| PI54640 | The "Delete" button in the window "Manage Objects" creates a new version of an object and marks it as deleted. It also modifies the text as it become strikethrough. A problem occurs when the text contains an OLE object: a space character is added (in the new version). | |
| PI58036 | If the "Manage documents" window is open while changing the status of a CR, an error message gets displayed. This message indicates that the "Document index" module cannot be closed down. | |
| PI58379 | In the "RCM > Manage CR" window, pressing the Enter key should not close down the window when the advanced filtering options are displayed. And it should be easier to take into account the filtering options entered (currently users have to run the command "View > Refresh"). Two choices are now available: either click on the new "Refresh" button (only displayed when the advanced filtering options are visible) or simply press the Enter key when a filtering field has the focus. | |
| Display only one confirmation message when changing the status of several CR. | ||
| When double-clicking on an object, RCM displays a confirmation message offering to create a new version of that object (if the preconditions are met). The checkbox "do not display this message anymore" enables to get rid of this confirmation message. A new radio button has been added to let the user decide which behaviour RCM should have if the confirmation message is discarded when double-clicking on an object: either edit the object (as currently) or create a new version with confirmation. | ||
| WEXP | PI46578 | RMF 6.1.0.8 does not export captions (either Figure or Table captions) if only the tiltle of the caption is specified (either in "WEXP Figure Caption" or "WEXP Table Caption"). Specifying the style, or a label or the position of the caption can be used as a workaround. |
| PI46787 | The spooler does not monitor the export properly when the generated document is periodically saved and closed, which can result in the spooler terminating the export before it completes with the error message JOB KILLED BY SPOOLER: NO PROGRESS TIME > 20 min. | |
| The spooler fails to move a job to the state "done" when the export job aborted before setting the job "in progress". | ||
| Manage WEXP Jobs: an error occurs when restarting two export jobs for the same module at the same time with the error message "Job is already in the todo folder". | ||
| PI46887 | The export may abort with the error "Cannot self-embed view" when exporting several inserted views in Book mode. | |
| PI46687 | Even if the option "Enable splitting cells" is ON, cells containing OLE objects are not split when the table is exported directly to MS Word (ie. using the "Table" format). | |
| PI50630 | Incorrect export of inserted views containing rotated column titles. When a column title has the format "Title R", WEXP change the orientation of the title (set vertically). In that case, an issue occurs if the view is exported via a RTF file (format = "RTF Table"): once the table has been fully exported, the export resumes not directly under the table but further away. In some cases the export can resume in the Object Templates section. As this section is removed by default, a whole part of the generated document is then missing. | |
| PI52988 | Hyperlinks too long are not generated. This occurs when the text to display plus the URL exceeds 255 characters. | |
| PI53081 | Hyperlinks are not generated if there is a paragraph break in the pattern [ text to be displayed "URL of the hyperlink" ]. | |
| PI53497 | Since version 6.1.0.5, exporting MS Word OLE objects "inline" takes more time. The extra processing introduced in 6.1.0.5 has been improved and now is much faster. | |
| PI53672 | An isolated OLE object in "Object Text" with some text on the same line is not exported separately any more so that the OLE object and the text remain in the same paragraph in the generated document. This behaviour can be overriden by creating an object attribute "WEXP Export OLE separately" and setting its value to "true". | |
| Empty the clipboard before closing the generated document to prevent MS from displaying a blocking confirmation message. | ||
| PI54276 | Indents and bullets can be lost when a combination of WEXP options is selected: "Treat line breaks..." = [When Required] and "Do not strip.." = [Yes] To prevent this, it is no longer possible to select this combination of options. And for modules already configured that way, WEXP avoids the situation by automatically switching the option "Do not strip..." to [No]. | |
| When a WEXP object attribute does not have the expected type, WEXP recreates it. But WEXP should then make sure to keep some details of the definition of the attribute unchanged: "Description", "Locale", "Inherit value", "Affect change bar", "Affect change date", "Generate history". | ||
| PI56114 | WEXP now detects the modification of an enumeration used by a WEXP attribute. For instance, if the type "WEXP Export Style" is missing one of the labels "Book", "Table" or "RTF Table", then WEXP should repair that problem. | |
| WEXP now records all the export options including the filter used, in a new module attribute named "WEXP Export Options 5" (Please refer the WEXP reference manual for more details about its content). | ||
| PI59752 | Make it possible to generate index entries containing colons (by modifying "WEXP Index On". Please refer to WEXP reference manual for more details). | |
| Word import macros | The Table split macro no longer adds a page break before the tables that do not need to be split into smaller tables (because they fit in one page). | |
| The Table split macro offers to process all the tables of the document (when none are selected) but actually leaves some unprocessed. | ||
| When converting a table into an OLE, the resulting paragraph shall have the same style as the paragraph following the table. | ||
| When converting a table into an OLE, the runtime errors '4198', '5153' and '5849' can occur. | ||
| When converting a table into an OLE, the resulting OLE may be only partially visible (when the paragraph is indented). | ||
| PI48500 | When converting a table into an OLE, the table may look different in the resulting OLE (the text font and paragraph settings may change). This issue is associated to some specific Normal.dotm. | |
| PI49574 | When no drawing is selected, the macro "RMFConvertDraw" issues a warning but offers to convert the selection anyway. If the user chooses to convert the selection, the selection is replaced by an empty OLE object. | |
| PI50366 | The MS Word macro provided by RMF to import a Word document may stop with a runtime error message '5941'. | |
| PI50343 | When converting a drawing into an OLE (RMFConvertDraw), the runtime error '4605' can occur. |
| Link | Date Released | Status |
|---|---|---|
26 June 2015 | Superseded |
| Component | APAR | Description |
| Compare Module / Transfer Analysis | Transfer Analysis: add a User Callout fonction in charge of duplicating a link. This allows to implement the (selective) copy of the attributes of a link. | |
| Created an API for modules comparison (using the 'hierarchical' method only). Please refer to the "RMF API" manual and the following example: $RMFHOME\irdrmfao\misc\api\compare_modules.dxl. | ||
| Create/Tag a RMF Module | PI33986 | When synchronizing a view, the "Show all table cells" filtering option is ignored (its value is not replicated). |
| Dashboard | DXL error during batch processings (update, update&export, export) if the pathname of the log file contains backslashes and there are several dashboards to process. | |
| Error message (Kitchen icon folder not found in '') during batch update and update&export when using DOORS 9.3 or 9.4. | ||
| Datamodel | Loading a module containing a view with a column "Link Indicators" or "Change Bar" in DOORS Web Access, makes DOORS interop process crash. Since the view "40. Link Info" contains a column "Link Indicators" since RMF 6.1.0.5 (in both the ATM2000 project and the default generic datamodel), modules created with such project may have the problem. Both project archives have been modified (the column "Link Indicators" has been removed). | |
| DOC | Move the function RECORD_DOC_Versions() that defines which modules of a document, DOC should modify to record the document version the objects belong to (in the attribute "IE DOC Versions") when baselining a document from: addins\irdrmfao\startup\userdefs.inc to addins\irdrmfao\plm\usercallout\docversion.inc | |
| DOC does not record the export options when the export is sent to the WEXP server. | ||
| When exporting a baseline, DOC does not record the export options in that baseline (but in the current version). If the user is a DOC manager and therefore has the sufficient rights, DOC should record the export options into the baseline. | ||
| Exchange | PI34695 | Exchange may fail to create links, in all the commands that enable to create links ("Exchange > import modules", "Exchange > import module content" and "Exchange > restore links"). No error is displayed. This error occurs when the target objects (of the links to be created) have a unique ID whose module ID part is different from the ID of the module they belong to. This can occur for several reasons, for instance because those objects have been imported. |
| PI35359 | In the window opened by the command "RMF > Exchange > Generate universal Ids", the "Generate all IDs" button does not modify the existing IDs and actually behaves just as the "Generate undefined IDs" button. | |
| Faster generation of universal Ids. | ||
| Faster import of links. | ||
| PI34985 | Make it possible to abort an import by clicking the "cancel" button on the progress bar. | |
| Document the API functions to generate UIDs or check them. Please refer to the manual named "RMF API" (new name of the manual previously named "RCM & PFM API"). | ||
| The export commands restricted to an Exchange manager ("Export modules", "Export baseline sets" and "Export modules with exchange" (available within the explorer window)) now restrict the access rights to the attribute "XML Source Ref" (which stores the UID of objects) to Exchange Managers only. The modules to export are opened in exclusive edit mode if possible (if not in read only). The UIDs of the RMF objects is set and the modules are saved after the export. If a module has some unsaved changes before the export starts, the user is asked confirmation to continue as those changes will be saved at the end of the export. | ||
| PI39035 | The Exchange commands within a formal module are available to all users. As a consequence, the import commands within a formal module should not restrict the access rights to the attribute "XML Source Ref" when run by an Exchange manager (so that subsequent imports can be run by any user). | |
| PI40570 | Exchange may import some symbols incorrectly. This issue has been fixed in RMF 6.1.0.8, in the import. So any export generated with another version of RMF can also be imported correctly using RMF 6.1.0.8. | |
| kitchen | Fixed three issues in the "Copy links from another module" script: 1) DXL error when selecting a module located in a sub-project, 2) DXL error when trying to create a link from or toward a deleted object. 3) any modules with the same name as the current module are ignored (not displayed in the list of the modules of the project). | |
| Manage Objects | PI33715 | The command "Manage Objects" may generate a DXL error when run on a module missing some attributes such as "IE Mod Type", “IE Object Type” or “IE PUID”. |
| PFM | Let the API function about applicability be customizable (non encrypted) in the new file addins\irdrmfao\startup\usercallout\pfmapplicability.inc | |
| RCM | PI33938 | The command "Synchronize CR" does not detect any change in a new RCM object version if the change has been performed in an OLE. To benefit from this fix, you need to replace the template "CR" by the one provided in %RMFHOME%\irdrmfao\migration\cr.dma. |
| New usercallout function called when setting a module under RCM control, named RCM_UC_postSetModuleUnderRCMControl (defined in the file addins\irdrmfao\startup\usercallout\rcmusercallouts.inc). | ||
| Also record the time (not just the date) a CR has been set to "completed" or "cancelled" (in the module attribute "RCM Accepted On" or "RCM Cancelled On"). | ||
| Under some circumstances, right after creating a new version of a controlled object, this new version can have suspect links whereas the previous one does not. | ||
| WEXP | PI32027 | WEXP may generate unwanted page breaks before a table generated from an inserted view. |
| PI35221 | In some rare circumstances, WEXP may hang while exporting an OLE if the option “Export isolated OLE objects as Inline data” is enabled. | |
| PI35225 | WEXP fails to export some OLE or export them as a metafile picture, when the exported document is displayed. | |
| The export processes spawned in batch mode by the WEXP server sometimes do not end and the WEXP server has to terminate them. This is due to the fact that the export processes should not open the modules displayed (but rather in the background, not displayed). | ||
| Enable to export an inserted view from a baseline. Please find the new syntax of the attribute “WEXP Module view” in the WEXP reference manual. | ||
| PI37553 | WEXP always exports the attribute "Object Text" of a cell even if the DOORS table is configured to display another attribute. | |
| PI33634 | RMF command Extract text from OLE objects" has been fixed : it did not work with Office 2007 up to 2013. | |
| The WEXP server has been improved: whenever an export reaches an error condition, the job completes gracefully which enables the server to start another job right away. | ||
| WEXP now keeps open the last four modules whose views have been exported (inserted views). Since version 6.0.0.3, WEXP used to close down a module right after exporting one of its view, to save memory. But this can slow down the export if several views of the same module are exported in a row. The number of modules remaining open at a time can be modified in the User Interface (advanced options). The default value (four) can also be modified as it is defined in the unencrypted file "addins\irdrmfao\wexp\include\userdefs.inc". | ||
| WEXP now also enables to create a cross-reference to a bookmark that only displays the chapter number (or figure label) of the paragraph where the bookmark is located. This can be achieved by using the new keyword "number", eg. [refer to "number:name_of_a_bookmark"]. | ||
| Figure captions (or Table captions) are now correctly inserted above the figure (or Table) when adding the keyword "above" in the attribute "WEXP Figure Caption" (or "WEXP Table Caption") eg. "[above]Figure Caption:ATM". This is achieved at several conditions though: 1) there must be only one OLE object in the Object Text, 2) the OLE object can be preceded or followed by some text but not both, 3) the OLE object must belong to an application that is registered in the system. | ||
| Figure captions can now be placed in a table exported from a DOORS table. | ||
| When a caption is to be inserted, an isolated OLE should not be exported "inline" (ie. its content expanded directly in the generated document) even if the option "Export isolated OLE objects as Inline data" is ON. | ||
| The text of an object followed by an OLE is sometimes exported with the style used for the OLE ("OLE style" by default) if the option "Treat line breaks in Object Text as new paragraphs" is equal to [When required]. | ||
| An error may occur when exporting a Word OLE containing some tables within a DOORS table if the option "Export isolated OLE objects as Inline data" is ON. | ||
| PI39835 | The end of the generated document may be missing if the bookmark defining where the export starts is located just before the section break of the Object Templates. (With at least one paragraph break in-between, the issue did not occur). | |
| Enable to force the value of some options displayed in the start window (Please refer to the files addins\irdrmfao\wexp\menu calls\wexp.inc and addins\irdrmfao\plm\doc\managedocuments.inc for DOC). | ||
| Enable to run a user-defined pre-check before starting the export (in order to make sure the values of some attributes such as "WEXP Module View" are valid for instance). This new usercallout function is named "usercallout_precheck" and defined in addins\irdrmfao\wexp\include\usercallouts.inc | ||
| PI37934 | Environment variables can be used in file paths since RMF 6.1.0.7. But in that version, it has a permanent side-effect on the value of environment variables within DOORS: after WEXP is run, any change of the value of any environment variable outside of DOORS is not seen within DOORS. This issue has been solved and the syntax to insert environment variables has been changed. Please now add dollar signs before and after the name of an environment variable, eg. $TEMP$\my_document.docx | |
| PI40464 | After a while, the WEXP spooler may stop because of a stack overflow error. | |
| PI41332 | After exporting an inserted view, the module containing the view is sometimes not closed down. This occurs when the module has been opened before by loading a module or a view (due to layout DXL or DXL attributes). The module is then only closed at the end of the export which results in an unneeded consumption of memory. This issue has been fixed. | |
| Using DOORS 9.6.1.3, OLE objects may not be exported if the option "Do not strip unsupported RTF markers before copy/paste" is not ticked. | ||
| The spooler may stop due to a DXL error if the language of the OS is not English. | ||
| Word import macros | PI37918 | DXL Errors may occur while exporting a MS Word to DOORS if RMF is installed in DOORS home directory: |
| Link | Date Released | Status |
|---|---|---|
05 December 2014 | Superseded |
| Component | APAR | Description |
| Compare Module / Transfer Analysis | NEW alternative to "transfer analysis": the new command "RMF > Reconcile > Update from a newer module" propagates the changes introduced in a newer version of the same module (object move, creation, deletion, attribute updates). | |
| Configure Project | A dxl error may occur when accepting the changes in the "Configure Project" window if the project has just been upgraded and is configured for RCM: -R-E- DXL: {addins/irdrmfao/startup/rcm/rcmcr.inc:827} An unexpected error has occurred | |
| Create/Tag a RMF Project | PI29614 | RMF does not check the right registry key to find where the project archives are when RMF is installed on a 64 bit windows. |
| Dashboard | RMF> Dashboard > Configure > Edit Scope: the filter drop-down list is not visible at first and when the tab "link reference" is selected, the description of the filter is not correctly displayed. | |
| RMF> Dashboard > Configure: error "attribute {attr name} of metrics {metric name} can't be deleted" when removing a metric that has just been created. | ||
| RMF> Dashboard > Configure: in the "data" creation window, when selecting a data name, the "DOORS attribute" field is only updated the first time. | ||
| RMF> Dashboard > Configure: in the "export to excel" configuration window, if a date has been entered, its format/validity should be checked when clicking "OK". | ||
| RMF> Dashboard > Configure: in the "export to excel" configuration window, the DXL error "-R-E- DXL: {addins/irdrmfao/Dashboard/include/excel.inc:288} null Stream parameter was passed into argument position 1" occurs when clicking the "Organize" button if the export is configured to update a file that does not exist. | ||
| DOC | In the "Manage document" window, enable to scroll the list of documents using the keyboard (the focus used to move to the list of version when a new document was selected). | |
| In the "Manage document" window, enable to sort the document list and version list (by clicking on the column headers). | ||
| In the "Manage document" window, resize the list of documents when the window gets bigger to make it easier to find a document. | ||
| Improve the "Find Document" feature by enabling to look for a piece of text in any part of a document name, not just the beginning of it and by supporting regular expressions as well. | ||
| No longer save the views (used for the generation) in an attribute (DOC View Description) but in a hidden file inside the database instead (as for the Word template) to avoid recording many data in the doc index module and therefore decreasing performances. Those files can be exported and imported in another database if needed (by using the "Export templates" and "Restore templates and references" in the "Administration" window). | ||
| Enable to use environment variables in file paths (template, log file, output file): RMF records the file paths with the name of the environment variables and only replaces them by their values when used. | ||
| New usercallout function DOC_UC_pre_GenerateDocument called before generating a document version. This new function is defined in addins\irdrmfao\plm\usercallout\docusercallouts.inc. | ||
| Miscellaneous | PI27164 | The Tool "RMF > Tool > save links in attribute" generates a DXL error if the user does not have access to one of the modules linked to the current module (either with outgoing or incoming links) and this module is not listed in the User Interface. |
| RCM | Prevent PUIDs from getting renumbered when completing a Change Request if the "IE Undefined PUID Keyword" object attribute is empty in the Project Profile. Should the attribute be empty, its default value is now considered to be TBD. | |
| WEXP | PI26805 | WEXP does not export the text before an OLE if : - the OLE type is "MS Word" and the option "Export isolated OLE objects as Inline data" is ON, - and the OLE is on the same line as the text before. |
| The message "[UnsetLock] ** no lock file ... Todo.rck" is sometimes issued in DOORS DXL interaction window when downloading the files generated by WEXP remotely (using a WEXP server also called spooler). | ||
| In the "Manage WEXP Jobs" window, clicking the "Monitor" button or displaying the log file takes too much time when the log file gets big. | ||
| Enable to use environment variables in file paths (template, log file, output file): RMF records the file paths with the name of the environment variables and only replaces them by their values when used. | ||
| PI28634 | The separators for the options "split cells" and "split and merge cells" can now be both used in the same cell. | |
| The first line is never merged even though the option "split and merge cells" is checked and the next line has the same content if the option "Do not strip unsupported RTF markers before copy/paste" is checked and if the view is exported directly (not using a temporary RTF file). | ||
| PI29616 | WEXP now enables to export a bookmark in a table cell. | |
| PI25892 | WEXP does not generate revision marks on headings properly, resulting in modified headings actually being seen as new. And as a consequence, the following headings are considered being renumbered. | |
| WEXP | Since RMF 6.1.0.6 improvement to export DOORS tables faster, some borders may sometimes not get exported. | |
| Word import macros | PI25614 | RMF export to doors macro may encounter an error on pictures whose layout is "inline with text". |
| Link | Date Released | Status |
|---|---|---|
05 September 2014 | Superseded |
| Component | APAR | Description |
| Dashboard | The "Configure dashboard" command now checks if the modules that have specific metrics still exists and displays the related metrics with a specific "warning" icon. | |
| The "Configure dashboard" window prevents from editing an export with an error message stating that the metrics used in the export should be enabled (though they may be already enabled). | ||
| The "Configure dashboard" window does not propagate correctly the renaming of a metric. As a consequence the exports and alarms based on the renamed metric become inconsistent. | ||
| DOC | PI19805 | The script "Generate history of document" may take an abnormal amount of time to generate the history of the modifications of the modules of a document when the document has many versions and modules. |
| Move the code setting the attribute "IE DOC Version" into a separate non encrypted file (addins\plm\usercallout\docversion.inc) to enable modifying it or calling it before baselining a document. | ||
| Display a splash window asking the user to please wait while opening the "Manage documents" window (and also for the "Manage RCM" and "Manage CR list" windows). | ||
| Enable to display a user-defined contextual menu in the listview of the "baseline" child window of the "manage documents" window. | ||
| Exchange | OLE are not exported in separate files, but instead in the XML files, if the RTF syntax is incorrect, resulting in a very slow import. | |
| The "import module content" command is very slow in RMF 6.1.0.5. This regression has been fixed. | ||
| Manage Objects | If the user clicks the "Select CR" button and then closes the current module by setting one of its CR to the 'completed' status, then a DXL error occurs when closing the "Select CR" window. | |
| Enable to identify headings as RMF objects. To do so, please run the "Configure Module" command and enable the option "Headings can be RMF Objects". | ||
| Miscellaneous | The "RMF > Select default linkset" command now opens up faster in big projects and also makes it easier to find the right link modules by organizing the link modules in a tree instead of a list. | |
| PFM | When creating a new configuration set by duplicating an existing configuration, the parameters values are correctly duplicated at first but they are not recorded. | |
| In the PFM browser, the property "Selected ?" is always equal to "No". | ||
| RCM | Using DOORS 9.3 and higher, the DXL attributes "RCM CR Name" and "RCM CR Description" of a new version of a controlled object are not updated automatically. The user needs to press the F5 button or close and reopen the module to get it updated. This issue has been fixed. | |
| The RCM check may recreate "follows" links mistakenly. This happens both when creating a new version N (the link toward version N-2 is sometimes recreated) and also when duplicating the version N (the link from the new object toward the version N-1 is always recreated). | ||
| The RCM check may report that a deleted "follows" link has been recreated whereas the link was not deleted. This occurs when a working object is deleted and then recreated. | ||
| The RCM check should not report the error 'Composite Object modification' (a descendant has been moved) when an object without descendant has an empty value for the attribute "RCM Object Structure". | ||
| The RCM custom filter provided as an example (working in review) does not filter out older versions in reference. | ||
| The "manage RCM" window may also list the controlled modules of another project located in the same folder and with a name starting identically. | ||
| In the "Manage RCM" window, when scrolling the items in the treeview, keep the focus there (instead of switching to the listview when the controlled module is selected). | ||
| Make sure that the RCM workspace Window is big enough to display all its content (it can be too small depending on Windows display settings), and enable to resize it. | ||
| Enable to use the RCM worspace window on a baseline and a non-controlled module (only to select a DOC version in that case). | ||
| A DXL error can occur when changing the status of a CR if an object impacted has several impacts links with different CRs. | ||
| WEXP | Export DOORS tables faster (twice as fast). | |
| DOORS tables with irregularly sized cells are not rendered as in DOORS (borders are not aligned the same way on the rows with irregularly sized cells). | ||
| Hyperlinks to bookmarks can be exported back again (regression introduced in RMF 6.1.0.3) (using the syntax [ text of the hyperlink #bookmarkname ]). | ||
| WEXP generates an empty paragraph at the end of the document when exporting an object containing one single OLE and some text before it. | ||
| Word import macros | When converting a table into OLE, the paragraph containing the OLE should keep the same style as the paragraph containing the table. |
| Link | Date Released | Status |
|---|---|---|
02 June 2014 | Superseded |
| Component | APAR | Description |
| Create/Tag a RMF Module | The module type of a module should be set even if an error occured during the synchronization. | |
| A DXL error occurs during the synchronization if the code of a DXL attribute to be synchronized is invalid. | ||
| When synchronizing a module, if its attribute "IE Mod Type" is empty then the user should be prompted whether the module should be synchronized anyway (instead of aborting the synchronization). And if its module type is different from the selected template, an error message should be displayed explaining that the module will not be synchronized. | ||
| When creating (or tagging) a module, do not force the value of the module attributes that do not have a specific value in the template. So that whenever their default value is modified in the template, their value changes in the modules after synchronization. | ||
| Added a new parameter to the API function API_CreateTagModule() to enable discarding any warning message while synchronizing a module with a template. Furthermore, if the messages are displayed, clicking on the button "Don't display anymore" is now effective. The warning messages are now issued into the log too. | ||
| When creating a new module from a template, set the module up for shareable edit mode if the template is. | ||
| PI14722 | RMF does not propagate the changes made to the code of a DXL attribute when synchronizing a module with its template. | |
| The synchronization of modules now checks filters in a more resilient way when copying a view (not based on its description any longer). | ||
| Dashboard | Even if a metric (or alarm) has been renamed, the view configuration window is now able to recognize a column displaying that metric (or alarm). | |
| The window allowing to display metrics in a view now recognizes all the types of columns (including the 2 new types of columns introduced in DOORS 9.6) when parsing a view, and lets the existing columns unchanged (width, justification, title). Last it no longer displays the message "The modifications done on the current view will be lost" needlessly. | ||
| Data model | Some views of the generic datamodel do not display incoming links unless the source module is already open. | |
| PI13679 | The files showInlinks.inc and showOutlinks.inc that can be used to design layout DXL columns have a flaw: the text of the descendants of the linked objects is sometimes not displayed. | |
| Add a new column "Link indicator" (only displayed in DOORS 9.6) in the view "40. Link info" of the generic datamodel templates. | ||
| DOC | PI07993 | An error occurs when clicking the « Browse » button and then selecting the same document index module in the « manage documents » window. |
| The modify command has a flaw. If a module is added to a document, its checksum is not set which results in an error message the next time the document index is opened. | ||
| When DOC creates a baseline of the document index (automatically to enhance performance), display a warning message to let the user know that a baseline is being created. | ||
| PI09237 | DOC should not open all the modules of a document when generating only some of them. | |
| In the "generate" window, the log message indicating whether the generation context has been saved or not is not accurate when the selected version of the document is a baseline. | ||
| Exporting from DOC using a WEXP server results in a DXL error with RMF 6.1.0.3 and 6.1.0.4. | ||
| Exchange | Exchange now exports filters in such a way that it can be imported very reliably. Only the comment used to be exported. Now a DXL script is generated as well. RMF, starting from version 6.1.0.5, uses this script to recreate the filter. The description of the filter is still recorded for older versions of RMF. | |
| Minor change in the User Interface of the command "export module content" so that if attributes and views are exported from a view, then only the objects from the display set get exported by default. | ||
| When exporting the content of a module using a filtered view, Exchange exports the objects that are not displayed with the text "Hidden text" only when it is really necessary to preserve the object hierarchy. Exchange used to do that when the option "show ancestors" was not checked even if the object hierarchy was valid. | ||
| Let the user know when they are about to import some modules that have already been imported elsewhere, so they can choose either to continue (creating new modules) or update the modules previously imported. | ||
| kitchen | PI07171 | The scripts generated by the RMF kitchen command "Save view as DXL" have a flaw on the creation of the view filter. The creation of the filter may fail with the following DXL error: R-E- DXL: null Filter parameter was passed into argument position 2 -I- DXL: execution halted. This errors can occur in various conditions: - if the filter is complex - if the kitchen command "Save view as DXL" has been run with a DOORS client session configured in another language than English - if the attribute(s) or column(s) refered by the filter contain(s) braces. The new implementation solves all those issues. |
| The "Extended copy objects" command creates a DXL error line 667 when run in DOORS 9.3 and higher. | ||
| Manage Objects | Add the new usercallout function UC_canClickButtonManageObject in addins\irdrmfao\startup\usercallout\usercallouts.inc allowing to add some new checks or override the default checks defining whether a given button of the UI should be enabled. | |
| Miscellaneous | In some occasions, the DXL error "sdo_startup.inc:328> unassigned variable iLevel" can occur. | |
| Incompatibility issues with DOORS 9.5.2.1 resulting in various DXL errors. | ||
| PFM | The layout of the graphical elements of the “PFM info” window is incorrect and the height of the dialog box should not change when clicking the "+" or "-" buttons. | |
| RCM | PI09040 | The RCM check should not repair a composite object in reference whose content has not changed since the latest baseline. If so, it is better to assume that it is the value of the attribute "RCM object structure" that should be updated. |
| Make it possible to prevent the RCM check from repairing the composite objects that are inconsistent by setting the new parameter RCM_REPAIR_COMPOSITE_OBJECTS to false in the file startup\usercallout\rcmusercallouts.inc. | ||
| PI09624 | Make it possible to have "heading" descendants objects in a controlled RMF object. This was no longer possible since RMF 6.0.0.4 and as a consequence the RCM check would delete the descendants objects of such a composite object. | |
| Enable to use an existing working CR to set modules under control and to leave the CR in the "working" status. | ||
| PI14905 | A DXL error occurs when setting several modules under RCM control with the same CR whenever the RCM project option "list of impacted modules" is set to "mandatory. | |
| Users should not be able to select a CR that is not assigned to them. | ||
| Miscellaneous improvements of the "Manage CR" interface: 1) all the commands now take into account both checked and selected Change Requests to avoid confusion, 2) some commands can be performed on a set of Change Requests (Status change, assign CR, set impacted modules, ...), 3) all the commands are now displayed in a menu instead of buttons (the floatting menu remains), 4) the advanced filtering options are hidden by default. | ||
| The RCM check now always recreates a "follows" link whenever it is deleted. Previously the RCM check used to recreate it only on objects in reference if the option "Repair out-link of an object in reference" was enabled. | ||
| No longer display the message telling that the module should be open in exclusive edit so that the RCM check can be run when the module has been closed without saving (using the "RCM > Close" command). | ||
| WEXP | WEXP throws an error when setting an empty value to a property of type "Date". | |
| PI10469 | In some occasions, WEXP does not export some module attributes into the document properties. | |
| PI10991 | While exporting an object using an object template, if the content of the clipboard is emptied by another application, then WEXP may delete some parts of the object template. | |
| PI11101 | Errors can occur after exporting an OLE of type Word that contains several tables if the option "Export isolated OLE objects as Inline data" is enabled and the option "Scale views (autofit behavior)" is set to [Autofit table to width of page]. | |
| WEXP fails to open a Word template whose pathname contains / instead of \. | ||
| PI11486 | Unregistered OLE can sometimes be exported incorrectly (converted into binary like characters). They are now exported as pictures. | |
| Word 2013 may crash when exporting many objects in a row using object templates. | ||
| PI11610 | When inserting a MS Word OLE as "inline data" (which means expanding its content in the generated document) the formatting of some pieces of text may change. This occurs when some styles used in the OLE already exist in the generated document but with a different formatting. | |
| The temporary bookmark "thistext" may remain in generated document. | ||
| When a table header has several rows, only the first is greyed out. | ||
| Using Word 2013, DOORS tables are sometimes not autofit to their content properly. | ||
| Using Word 2007 and higher, tables created from views are sometimes not autofit to the page width properly as they remain larger than the page width. | ||
| WEXP may sometimes not export a symbol. Only the first symbol is not exported. This happens if the symbol is also an ASCII character. | ||
| Enable to export the value of a WEXP option into a property of the document. For instance, add the line below in the module attribute "WEXP Document Properties" to export the filter used for the export into a property named WEXP_filter: WEXP_OPTION(Export filter)->WEXP_filter Please refer to the WEXP reference manual to find the name of all the WEXP options. | ||
| OLE are not exported if the RTF syntax is not fully enforced though the OLE is visible in DOORS and exported successfully with the standard export to MS Word. | ||
| PI15384 | An error may occur when exporting several inserted views at the same bookmark and with the table format. The content of a table may not be exported. | |
| Let a command named "View WEXP jobs" be available for users who are not WEXP spooler administrators in order to check the status of their export jobs, download the documents generated and restart a job if needed. | ||
| The WEXP server now spawns the export processes in batch mode to prevent any interaction (confirmation, error messages) from blocking the export. |
| Link | Date Released | Status |
|---|---|---|
06 December 2013 | Superseded |
| Component | APAR | Description |
| Configure Module | PM96990 | The command "Configure Module" generates a DXL error if the Project Profile contains duplicate Object Types. |
| Create/Tag a RMF Module | Views are incorrectly synchronized when they contain a filter that is not turned ON: the filter is not synchronized. As a consequence such a view is still reported as modified even after the synchronization. | |
| Dashboard | Improve performance by reducing the number of writes into the log file and make it possible not to generate a log file. | |
| PM97074 | The DXL error below may occur while updating a dashboard: -R-W- DXL: | |
| PM97896 | Some rules limiting the scope of the collection of the metrics are not properly processed. Besides, if the root folder is modified by selecting a sub-folder, then the next update is incorrect (no object are visible). | |
| The MS Excel application is sometimes not closed down at the end of an export or after configuring the export even though no MS Excel window is visible. | ||
| DOC | DOORS may crash while creating a baseline of a document if DOC is set up to accept working object versions automatically and if there is a RMF object that is working and whose PUID is not set. | |
| Make the document index configuration more resilient to changes such as renaming or moving the folder chosen to hold the definition of the baselinesets managed by DOC. | ||
| Exchange | The command "Export > baseline set" should enable to export the baselinesets located under the folder "Config". | |
| PM97513 | Exchange fails to import a view whose filter includes a rule based on an multi-valued enumerated attribute using the conditions "includes" or "excludes". It also fails to import a filter based on the rule "contains" (eg. | |
| PI04714 | When exporting modules with a filtered export view with the option "show ancestors" enabled, the hidden objects should not be exported. | |
| PI04933 | A DXL error occurs during the update of an existing enumerated attribute type if one of its label is empty. | |
| Colum title may not be correctly imported because "\t" is converted into a tab. As a consequence the title "_:join(\t)" becomes "_:join( )". | ||
| Manage Objects | An error error "identobj.inc:1763> null attribute type parameter was passed into argument position 1" may occur when opening a module if the "Manage Objects" window is open. | |
| The button "Duplicate" has a flaw when used on RCM controlled modules. The error occurs when duplicating a version of controlled object that is not the last version. In certain circumstances, the copy is created but is not modified accordingly (to set the attributes "IE PUID", "RCM Version", ...) and the next version of the original get modified instead (if the user has the "RCM Admin" role). | ||
| Migration Rules | PM97077 | The migration rule "TAGOBJ" generated the DXL error below when tagging a set of objects finishing with a DOORS table: |
| RCM | Enable an assignee to change the status of a Change Request from "to be reviewed" to "working". | |
| PM92322 | On some rare objects whose RTF content is not compliant to the standard, when creating a new deleted version of such object, the beginning of the text of the new version may get duplicated. This issue only occurs in RMF 6.1.0.3. | |
| In the suspect links management window, the command "select all" only selects the current link actually (affects RMF 6.1.0.2 and 6.1.0.3). | ||
| The suspect management GUI sometimes display the msg "the suspicion was cleared on " followed by the date of creation of the link. | ||
| PM96842 | If two different objects with the same PUID and version both have a suspect link, then the suspect management GUI only displays one. | |
| PM96699 | The suspect management GUI should disable the command duplicate when the selected new version already has a link, and should offer a new command "Select links manually duplicated" to highlight those links in the treeview. | |
| Under some circumstances the RCM suspect UI may display the text of an object incorrectly if the module is not visible. | ||
| PM96993 | When a new deleted version is created, the text of this version is strikedthrough correctly now, preserving symbols. | |
| The RCM suspect link user interface now enables to setup which attribute will be displayed when displaying another link (see new submenu "When displaying another link" in the menu "View"). 3 choices are offered: either keep the same attribute displayed, display Object Text or display one of the attribute modified in the selected proposed new target (preferably Object Text). | ||
| PM97894 | Switching from one suspect link to another in the RCM suspect links User Interface can take some time if the default view of the source module of the link is complex. Loading the standard view instead makes the processing faster. | |
| Make it possible to create additional DXL attributes in the controlled modules by editing the file addins\irdrmfao\startup\usercallout\rcmusercallouts.inc. | ||
| Make it possible to edit the rationale of an object directly in the controlled module by providing a new object attribute "RCM Justification" and keeping its value in synch with the same attribute in the CR module (when synchronizing the CR). | ||
| PM97894 | Modules are opened with the standard view instead of the default view in the suspect link management for performance reasons. | |
| PM98307 | In shareable edit mode, when clicking the button "Cancel Working" (in the Object manager user interface), the object is soft deleted (as it cannot be hard deleted in that mode). The outgoing links of the object should be deleted, in particular the "follows" link. | |
| Enable to remove non semantic links while creating a new version by defining a new attribute « IE Link is volatile » in the project profile (this new attribute is automatically created when running the command "RMF > Configure a RMF Project" and then clicking the "OK" button). Thus a type of link that is not semantic can now be non-volatile. | ||
| Make it possible to use the character '.' when setting a custom version number by choosing a different character used as branch separator in the usercallout fonction char RCM_UC_getBranchSeparator (defined in addins\irdrmfao\startup\usercallouts\rcmusercallout.inc) | ||
| The usercallout functions RCM_UC_createObject, RCM_UC_modifyObject and RCM_UC_deleteObject are now called at the very end of the creation process so that all the attributes of the new object are set at that time. | ||
| The impacted modules and assignees of a CR are recorded in a new fomat to specify the database they belong to. Thus a CR can be used in a database different from the one in which it has been created. The previous format is still supported for backward compatibility and an automatic conversion is performed under some conditions. | ||
| Enable not to display the RCM control box window (allowing to apply the RCM filters) automatically when opening a controlled module. To do so, a new command ("Show control box automatically") is available in the "RMF > RCM" submenu. It is checked by default. Each user can uncheck it (independently from the other users) so that the control box is no longer displayed automatically when opening a controlled module. | ||
| Enable to let the RCM filter "Conf Reference" display working objects or not. By default, working objects are displayed. To hide them, please edit the value of the constant RCM_FILTER_CONF_REFERENCE_DISPLAY_WORKING in addins\irdrmfao\startup\usercallouts\rcmusercallout.inc | ||
| Enable to define additional custom RCM filters by editing the new file addins\irdrmfao\plm\usercallout\rcmcustomfilters.inc | ||
| WEXP | PM91676 | When applying a filter "RCM working" or "RCM reference", objects that should not be exported are sometimes exported. |
| PM92203 | Error "undeclared variable richTextWithOleNoCache" when launching WEXP in RMF 6.1.0.3 using DOORS 9.3.0.0 up to 9.3.0.4. | |
| PM92557 | In RMF 6.1.0.3, the export is slower when the option "Treat line breaks in Object Text as new paragraphs" is set to [When required]. | |
| PM93288 | Using Word 2007 or 2010, tables are sometimes not autofit to the page width properly. | |
| PM93928 | Using DOORS 9.5, the line breaks are always exported as paragraph breaks even when the option "Treat line breaks in Object Text as new paragraphs" is set to [When Required]. | |
| PM94421 | MS Word may hang while inserting a view as a RTF table containing some text with bullets (affects RMF 6.1.0.2 and 6.1.0.3) | |
| Ability to export a document with the file extension .docx or .docm and select a template with the file extension .dotx or .dotm. | ||
| Ability to use a bookmark several times, only for exporting inserted views. | ||
| Support of Office 2013 | ||
| Consider an OLE as isolated even if there are empty lines or space characters before and after it. (several features are restricted to isolated OLEs). | ||
| Enable to generate a caption for any object (not just objects containing OLE) as before RMF 6.1.0.3. | ||
| PM99743 | Using Word 2010, the style applied to OLE may not be as expected. | |
| PI04706 | The "join(\t)" tag in a column title is not handled properly if the column is empty. As a consequence, the text is not exported with the expected style. | |
| PI06799 | WEXP may issue an error in the log file if the style "Normal" is missing in the Word template. | |
| WEXP fails to insert a sub-document with the error message "Unable to get path" in RMF 6.1.0.3. | ||
| WEXP fails to insert a sub-document whose file extension is .docx or .docm | ||
| WEXP fails to create a sub-document with a UNC pathname. | ||
| WEXP fails to export a sub-document in batch mode (with the error "Unable to get property ActiveDocument"). | ||
| WEXP does not generate revision marks for an attribute displayed in a column concatenated to the next column (using the "join" tag in the title of the column). | ||
| Word import macros | The conversion of tables into OLE does not preserve the styles of the cells when using Word 2007 or 2010. |
| Link | Date Released | Status |
|---|---|---|
14 June 2013 | Superseded |
| Component | APAR | Description |
| Create/Tag a RMF Module | The synchronization of a module may hang while copying a view containing a very complex filter. This issue also exists in the command "RMF > Tools > Copy Views". | |
| The new function API_CreateTagModule is available in addins\irdrmfao\includes\api.inc and documented in the "RCM & PFM API" manual. | ||
| Dashboard | Enable to export the DXL based metrics (called "data"). | |
| The exported Excel file is not closed (regression introduced in RMF 6.1.0.2). | ||
| DOC | A new script is provided to demonstrate how to generate all the master modules of a RMF/DOC document version by script (without using the 'manage documents' User Interface) (addins\irdrmfao\misc\wexp\docwexp.inc). | |
| The "Generate" window now opens faster as the master modules are not loaded beforehand anymore. | ||
| In the "Generate" window, the WEXP parameters of a master module sometimes are not recorded. It can happen if slave modules are in the list of the modules of the document before the master module and if the modules after the master module are not checked in the list of master modules. | ||
| Exchange | The import of a view throws a DXL error (null Array) if there are no columns in the view. | |
| lib_no_irdrmfao.zip | Prevent errors due to RMF persistent triggers when editing, without RMF, some modules created using RMF. (This is the purpose of the file lib_no_irdrmfao.zip which is available in /irdrmfao/misc/addins). | |
| Miscellaneous | The command "Tools > Save link attribute" makes DOORS 9.2 crash if the attribute selected already exists but is not a module attribute. This issue does not exist with higher versions of DOORS. | |
| The script "show-inlinks.inc" may sometimes not display some incoming links. This script is useful to quickly create a layout column displaying some incoming links. It is available both in addins\irdrmfao\layout and irdrmfao\libviews\traceability_column. | ||
| RCM | New usercallout functions RCM_UC_createObject and RCM_UC_modifyObject called when creating a new controlled object or a new version of a controlled object respectively (defined in addins\irdrmfao\startup\usercallout\rcmusercallouts.inc). | |
| The usercallout function RCM_UC_deleteObject now preserves the OLE and rich text formatting when striking the text (and semantic attributes) of a new deleted version of a controlled object. | ||
| Whenever a descendant of a composite object in reference has been moved, the RCM check now moves it back correctly. Since version 6.0.0.3, it used to moved it after the root object instead of below. | ||
| In the "suspect links" management User Interface, the command "File > Display log" may display an empty list when the log file is too big. | ||
| Two improvements on the management of suspect links : 1) keep the item selected in the explorer after running the command 'create new version' and warn the user that a new version is created only for the selected object. 2) record a message in the log when the modification are saved or rejected (by closing the module without saving). | ||
| If the RCM check is run when opening a module (which occurs if the module was previously closed using the command RCM > Close), then a message « no modifications on the composite objects have been detected during the check » may be displayed even though the check actually repaired some composite objects. | ||
| WEXP | Faster export, especially during repagination, and the default values of the advanced parameters have changed to speed up the export. | |
| Change in the advanced options: the option "OLE objects are compatible with DOORS 5 data format" has been removed and it now possible to specify the "number of objects after which to save Word document" (this option replaces the option "Save Word document during generation"). | ||
| It is now possible to place the tags <<OLE Object>> and <<Picture Object>> in a table within an object template. | ||
| Some DOORS tables may sometimes not be autofit to the page width correctly. | ||
| New object attribute "WEXP OLE as WMF Picture" enabling to export an isolated OLE contained in the "object text" as a WMF Picture on a per object basis. This attribute overrides the global options. It complements the already existing object attribute "WEXP OLE Inline". | ||
| The export may stop at the very beginning if the "Protected View" security option is enabled in MS Word and the template is not on a local drive. | ||
| If the option "Export isolated OLE objects as Inline data" is enabled then the tables contained in isolated MS Word OLEs are now autofit (according to the setting for inserted views). | ||
| Let the value of the attribute "WEXP Export Style" override the option "Export inserted views in table format as RTF files by default" so that one table can be exported directly though the default mode is RTF. |
| Link | Date Released | Status |
|---|---|---|
15 March 2013 | Superseded |
| Component | APAR | Description |
| Compare Module / Transfer Analysis | The option "add dynamic history column" should be disabled if the user does not have the required access right to create an attribute in the module. | |
| Dashboard | The dashboard does not export the right baselines when selecting the baselines to be exported according to their date of creation (using the option "Select by date" in the baseline tab). | |
| The sub-menu "RMF > dashboard" is not visible in a new dashboard just after its creation. The module has to be closed down and reopen for the sub-menu to be visble. | ||
| After having edited an export definition, it may disappear from the list of export definitions. | ||
| Data model | Support background coloring by attribute in columns (new feature in DOORS 9.4) when synchronizing a module with its template. | |
| DOC | Ability to discard the hidden Change Requests when generating the history of the modifications made between two DOC baselines. | |
| DOC now enables to define document properties based on attributes of any type (not just string or text). Besides the references to a document property <<document property>> are now case insensitive. | ||
| Manage Objects | Enable to enter a rationale when creating a new controlled object and record this text in the attribute "RCM Justification" of the impact object in the CR. | |
| New usercallout function called when clicking a button in the manage objects dialog which enables to prevent the related operation. This new function is named UC_preClickButtonManageObject and defined in addins\irdrmfao\startup\usercallout\usercallouts.inc. | ||
| Migration Rules | The new rules SETOBJRICHATTR and SETMAINOBJRICHATTR preserve formatting (bold, underlined,…). | |
| When some pieces of text are concatenated using the rules SETOBJATTR and SETMAINOBJATTR, a line break should be used as a separator if the attribute type is "Text". | ||
| Miscellaneous | PM78512 | Installation of RMF can result in bad performance when opening the Manage Users dialog. |
| RMF commands should not generate a DXL error whenever the definition of an attribute, type or view cannot be modified due to restricted access rights. | ||
| RCM | When the status of a CR changes from "completed" to "in progress", the contolled objects impacted that was "suppressed" are then no longer flagged as "suppressed". They should remain "suppressed". | |
| If the project is configured to enable links toward objects in working to be supect, then such a link should be suspect again if the object has been modified after the link was created or after its suspicion has been cleared. | ||
| The "RCM suspect links" user interface now enables to select several suspect links and to process them in batch (clearing, transferring or duplicating them). It also records all the actions taken into a log and displays the differences between the current target of a suspect link and the new version(s): modification of the attributes (semantic or not) and creation / deletion of links. | ||
| When a CR is synchronized, the attribute 'Object Text' of the impact objects is now updated to reflect the possible change of the PUID of the impacted object. | ||
| WEXP | Do not change the orientation (to "landscape") of all the sections at the end of the document if the last section generated is set up to the orientation "landcape". | |
| Objects configured to be exported as a table row (by setting the name of a view in the attribute "WEXP View Name") should not be exported if they are not displayed in this view. Furthermore, if the attribute "WEXP View Filter" is also set (with the name of another view), then WEXP should check if the objects are visible in this other view instead and export only the objects that are visible. | ||
| The WEXP spooler fails to launch a job if the pathname where RMF is installed contains accented characters. | ||
| When inserting a section break and changing the page orientation, WEXP does not preserve the top and bottom margin. | ||
| Sometimes index are not correctly updated. | ||
| Ability to include shapes in object templates. | ||
| The spooler sometimes aborts the export job for no reason. | ||
| The spooler should check the actual status of a job before sending a notification as it sometimes sends a notification with the status "SUCCEED' instead of "FAILED". | ||
| The bullets exported by WEXP on DOORS 9.5 do not have the usual look. |
| Link | Date Released | Status |
|---|---|---|
27 November 2012 | Superseded |
| Component | APAR | Description |
| Configure Project | The Project Configuration fails if at least one of the custom attribute types "RCM Control Mode", "RCM Repair Link Modification" or "RCM Suspicion Actions" are missing in the Project Profile with the error -R-E- DXL: | |
| Dashboard | The metrics of type "Evolution" and "Stability" should take into account the objects created as a copy. | |
| The metrics of type "Count Links" and "Count Linked Objects" do not take into account the incoming links from modules that are not open. | ||
| An error may occur when creating a view if the inserted metric has just been created. | ||
| Data model | Update the generic datamodel so that the PUID DXL column do not generate an error if the attribute IE PUID is missing. | |
| DOC | The export of several modules to MS Word may stop with a DOORS diagnostic log. | |
| Reduce the time needed to start the command "RMF > Manage Documents" on big projects. | ||
| Reduce the time needed to start the command "RMF > Manage Documents" and make updates for big document indexes by reducing the time to compute checksums. PLEASE NOTE that the existing document index modules MUST BE UPGRADED by a user with the role DOC Admin. To do so, please either run the command "RMF > Manage Documents" and browse all the document index modules one after another or run the script %RMFHOME%\irdrmfao\misc\migration\migrate-doc-index.dxl | ||
| When exporting a module from DOC, the RCM filter chosen is not taken into account if the user has selected "Load from module" then clicked the button "module parameters" and then clicked "OK". | ||
| Record the document versions that each RCM controlled object belongs to in a new attribute "IE DOC Versions" each time a document is baselined. | ||
| Before deleting a document, DOC should make sure that the user has the required power (manage database) to delete a baseline. If not, DOC shall warn the user and let them decide whether to delete the document without deleting the baselines or abort. | ||
| Add two new usercallouts, one called before and the other after baselining a document. These functions are defined in the new file addins\ìrdrmfao\plm\includes\doc\docusercallouts.inc. | ||
| Prevent the history of doc index modules from growing disproportionately by not recording the modifications of the attribute "DOC View Descriptions" in the history any more and by automatically baselining a doc index when it contains more than 1000 history entries. | ||
| Make the action "Refresh References" (in the Administration window) more efficient by updating the checksum of only the objects that have been modified. | ||
| The command "Generate History of Document" now also enables to ignore the modification whose Change Request is hidden. | ||
| Exchange | Do not "restore folders" when loading the header file but when actually importing the modules. | |
| When importing, the objects containing OLE should not be flagged as modified when the OLE have not changed. | ||
| Exchange may update enumerated attribute incorrectly if the order of the labels in the enumeration is different in the module as compared to the XML. | ||
| Exchange does not update an attribute type if its name is not the same as in the XML. | ||
| Errors such as "ERR:attributeDefinition 'Absolute Number' error in creating attribute definition" may be reported in the log while importing. Those errors can be discarded as the import is correct anyway. They occur on system attributes whenever the locale of those attributes is different in the source database. | ||
| Install / uninstall | If Office 2010 64 bits is installed, RMF fails to copy the file irdrmfao.dot in the startup directory of Office and displays the error message "irdrmfao.dot error - Couldn't locate MS Office". | |
| RCM | Display the "Manage RCM" user interface faster on big projects. | |
| The Project Index module is left unsaved and open in the background when setting or unsetting a module of a sub-project under RCM control. | ||
| When changing the status of a Change Request, the following error may occur: -R-E- DXL: | ||
| Make it possible to create a new version after a version "tagged as suppressed". This new version is created as a copy of the version just before the "suppressed" one. | ||
| If a CR is not assigned, make sure that anyone has sufficient access rights (RMCD) to work on the CR. | ||
| New callbacks called before and after changing the status of a Change Request (defined in addins\irdrmfao\startup\usercallout\rcmusercallouts.inc). | ||
| PM65534 | The RCM check now fully supports the modification of a composite object in reference by a RCM Administrator except the purge of a child object which is still not handled. You can add, move in, move out, reorder or delete child objects. | |
| WEXP | The export of an inserted view in book mode may fail on MS Word 2010. | |
| When exporting a big module, it is recommended to enable the option "Save Word document during generation". WEXP now also closes and reopens the exported document periodically when this option is enabled to prevent MS Word from generating errors. You can change the period (number of objects exported) by editing the file addins\irdrmfao\wexp\include\userdefs.inc. | ||
| Small DOORS tables are sometimes not autofitted when using the [Autofit table to width of page] setting. | ||
| The command "Extract words from OLE" leaves the temporary Word document open if the option "Process only the current object" is checked. | ||
| WEXP may export a text with two bullets if the style applied already features a bullet. | ||
| WEXP | The traces displayed by the WEXP spooler on the server side are now recorded in the log file as well (to read the log file, please run "RMF > Manage WEXP Jobs" as a WEXP spooler admin and then click "Monitor" first and then "Log"). | |
| Word import macros | Faster conversion of tables into OLE. |
| Link | Date Released | Status |
|---|---|---|
30 May 2012 | Superseded |
| Component | APAR | Description |
| Dashboard | A DXL error may occur in the file dashboard/layout/statusAlarm.dxl at line 58 using RMF 6.0.0.4 when displaying a view that shows alarms. A workaround consists in running the command "Configure Dashboard" once. | |
| At the end of an export, Excel is sometimes not refreshed. | ||
| The computation of a metric of type "Evolution" may be incorrect if the ending date is not specified. | ||
| DOC | The script "Generate doc history" is not restricted to master modules any more. | |
| An error may occur when clicking the "Module Parameters" button in the "Generate" window : -R-E- DXL: | ||
| Exchange | An error may occur when importing a module with readonly access rights : addins/irdrmfao/startup/exchange/xmldefs.inc:2469> An unexpected error has occurred | |
| PFM | When a new configuration is created, the value of its parameters is empty. They should be equal to those of the previous version instead. | |
| RCM | Changing the status of a Change Request to "Cancelled" fails if at least one impacted object is not composite (has no descendants) with the following error : "addins\irdrmfao\startup\rcm\rcmimpact.inc:977 | |
| When changing the status of a CR to "Cancelled", RCM should check also if the descendants of the impacted object have incoming links and display an error message easier to understand if so. | ||
| When a non-priviledge user run the command "set to be reviewed" in "manage CR" and does not confirm the action, then the CR is left open in edit mode and not visible. | ||
| When changing the status of a CR check if the CR has been opened in exclusive edit mode successfully. | ||
| To change the status of a CR from "to be reviewed" to "in progress", the "CR manager" role is sufficient: do not require the "RCM admin" as well. | ||
| When changing the status of a CR from "in progress" to "to be reviewed", do not open the impacted modules (in exclusive edit mode) as it is useless. | ||
| When changing the status of a CR, if an impacted modules cannot be opened in exclusive edit mode, do not display an error message for as many times as there are impacted objects, but only once. | ||
| When changing the status of a CR, make sure first that the impacted modules and the CR are not modified so that they can be closed down to abort the transaction should an error occur. If such a module is modified, let the user decide wether saving it or aborting. | ||
| When an error occur while changing the status of a CR, close down all the modified modules without saving in all cases. | ||
| Whenever the status of a CR has changed in another session, RCM may not be aware of it and therefore may not prevent a user from modifying an object whose CR is now "to be reviewed" for instance. | ||
| The RCM check may fail with a DXL error message "null LockRef". | ||
| Let CR modules be resilient to a change in the name of the impacted modules to prevent error when displaying view "11. Delta highlights". | ||
| The code of the RCM triggers can now be edited. It is available in the file startup/usercallout/rcmusercallouts.inc. | ||
| If the user double-clicks a column displaying a semantic attribute (not the main column) and a new version is created, then the value of the semantic attribute is reset for the new version. The RCM triggers need to be deleted and recreated to fix this issue. | ||
| WEXP | The UI "Manage WEXP jobs" now displays detailed information about the jobs that are inconsistent and allow to delete them instead of simply displaying the error "Some errors occurs when extracting data on waiting/in progress/completed jobs". | |
| When the export is sent to the spooler, WEXP should close the process winword.exe spawned when starting up WEXP. |
Table of Contents:
| Link | Date Released | Status |
|---|---|---|
24 February 2011 | Current |
| Component | APAR | Description |
| Dashboard | Scope rules now accept plain text in addition to regular expressions. | |
| Dashboard | Miscellaneous defects related to the management of the alarms have been fixed (status, global status, GUI). | |
| Dashboard | In some cases, the metrics of type evolution were not properly computed. | |
| Dashboard | Enable to express the dates relatively (as a number of days before the current date) in metrics of type "evolution" or "stability". | |
| Dashboard | The views created by the dashboard should have the same access right configuration as the dashboard module itself. | |
| Dasboard | Metrics based on an enumeration attribute: 1) display the values of the enumeration in the order they have been defined 2) if the attribute can take several values (multi) then display the overal number of objects instead of the total of values found. | |
| Dashboard | The export to excel generates an error in export.inc at the line 406 in the mode "All information in one sheet" when there is a deleted object in the dashboard module. | |
| Data model | The PUID layout column should not generate an error if the attribute IE PUID is missing. | |
| DOC | While exporting a document to Word, an EXCEPTION_ACCESS_VIOLATION may occur (at DocWexpInit.inc:29) if there are more than one master module in the document. | |
| DOC | DOC may fail to baseline a document if one module has been purged and recreated with the same name, unless the references have been updated. | |
| Exchange | On rare occasions Exchange may fail while exporting an object containing an OLE with the error startup/exchange/xmldefs.inc:310> null buffer parameter was passed into argument position 1. | |
| Exchange | Exchange does not support all the UTF-8 characters (such as ü, ö,…) in attribute names, module names or enumerations. | |
| Exchange | The command "Generate Universal IDs" now sets the UID of deleted objects too. | |
| Exchange | While importing links, Exchange now reports an error whenever duplicate UID have been found in a target module or when a link cannot be created because the target object is deleted. | |
| Exchange | If the button "Create Links" in the "Restore links" window is clicked twice, the links that have just been created are removed. | |
| Exchange | The 'Complete' button in the Export Definition GUI should also parse the DXL columns of the checked views to find out which attributes are needed. | |
| Exchange | The Universal Identifier of each object is now recorded while exporting a module (provided the module can be edited). Only the undefined or duplicated Universal Identifiers are recorded. | |
| Explorer | The explorer may take a long time to display when parsing a big project. To solve this issue, the list of the modules and linksets of a big project is now recorded, so that the explorer opens up more quickly the next time. You can have the explorer refresh the content of this inner list using the command "Refresh project content". Last this inner list is automatically updated when it gets older than one week time (this time period can be changed). | |
| Install / uninstall | PM56861 | RMF installer does not detect Office 32bit versions on windows 7. |
| PFM | Prevent the message "DXL Execution Timeout" from appearing by adding the instruction "pragma runLim, 0" to the code of the DXL attribute "PFM applicable ?". | |
| PFM | The current module is not updated when a work configuration is selected. | |
| PFM | Error "Cannot increment the revision number" issued when creating a new version in shareable edit mode. | |
| PFM | The status of the criteria of a package version may be incorrectly loaded if the same package version is used in another configuration. | |
| Project upgrade | A new script upgrading all the RMF projects of the database is now available in "\irdrmfao\misc\migration" ("upgrade-all-projects"). | |
| Project upgrade | When upgrading a project created with TREK 4.2 (or older), the DASHBOARD module template should be replaced. | |
| RCM | The RCM Object trigger should not prompt the user if they want to create a new version if no semantic attribute is displayed in the current view (for compatibility with TREK, and to avoid the annoyance of being prompted each time an attribute is edited). | |
| RCM | The RCM Object trigger displays a new option "do not display this message anymore" in the confirmation message allowing to create a new version. If this option is checked, this confirmation message is no longer displayed for the current module until it is closed. | |
| RCM | Whenever the RCM attribute trigger prevents the modification of a semantic attribute, copy the proposed text into the clipboard. | |
| RCM | The RCM Object trigger should not display the message "Beware : any modification of a semantic attribute will be rejected" when the module is in shareable edit mode and the object is not locked. | |
| RCM | Make it possible to export the list of Change Requests displayed in the "Manage CR" window to excel. | |
| RCM | The RCM check may report a false alarm "action 'Composite Object modification' (a descendant has been moved)" on the cells of a table located below a controlled object. | |
| RCM | When creating a new version of a controlled object, do not duplicate the Universal ID (used by Exchange) of the previous version. | |
| WEXP | PM56508 | Large DOORS tables are sometimes not autofitted when using the [Autofit to table content] setting. |
| WEXP | New means to add an offset to the level of headings in an inserted view: the object attribute "WEXP Heading Offset" (of type integer) in the exported module can take positive and negative values. The former means still exists : the module attribute "WEXP Base Heading Style" in the module containing the inserted view. Both means can be used together. | |
| WEXP | It is now possible to update the attribute "OLE Word List" with the command "Extract text from OLE objects". This attribute generated by the RMF Word import macro, records the text of the OLE objects contained in the "Object Text" of each object. | |
| Word import macros | Tables in a document with the .docx extension are always split when using Office 2010. |
| Link | Date Released | Status |
|---|---|---|
26 October 2011 | Superseded |
| Component | APAR | Description |
| Copy views | A DXL error may occur in file synchronize.inc at line 1501 in RMF 6.0.0.2 (and on a different line in other versions) : "An unexpected error has occurred". | |
| Create/Tag a RMF Module | PM46489 | The pseudo attributes such as 'Object Number' are not supported by the synchronization of views in 'Create/Tag a RMF Module'. |
| PM48404 | Attributes locale is not preserved neither by the module synchronization nor by Exchange. | |
| Dashboard | The time needed to collect metrics has been significantly reduced | |
| DOC | PM40159 | Closing the popup window "display context" within the "generate" window may generate a DXL error |
| Exchange | PM48498 | Exchange fails to import a module with an error "incorrect XML data" because of unsupported characters found in DXL attr |
| RCM | PM45440 | When changing the status of a Change Request from "In Progress" to "To be reviewed" or synchronizing it, the following error message is displayed in the RCM error window: ERROR: Can't save impacted object structure in CR |
| PM46084 | The button "Configure Module" in the window "Manage RCM" may generate a DXL error (-R-E- DXL: | |
| PM46209 | Non-RMF controlled objects created with TREK 5.2 and below are not migrated properly by the script migrate_rcm.dxl | |
| PM46211 | The RCM check can report undue errors on the composite controlled objects if they have many children objects (hundreds) | |
| Among all the new proposed target versions, the RCM suspect links GUI should display clearly those that are deleted (attribute "RCM is Tagged as Suppressed" equal to "True") | ||
| Make it possible to take into account the working objects when looking for suspect links. (To do so, the project option "Let new working targets generate suspect links" must be switched ON) | ||
| Enable the CR creators and the assignees to synchronize a CR whose status is working. | ||
| Do not overwrite the value of the attribute “RCM Version” when setting a module under RCM control. | ||
| Faster creation of a new controlled object (the CR is no longer saved twice). | ||
| Enable to enter a rationale when creating a new version by double clicking on the last version. | ||
| New view "12. Suspect Links" in the template CR showing the objects potentialy impacted by each new version. The view "11. Delta Hightlights" is also displayed quicker. (archive 'cr.dma' available in \irdrmfao\upgrade). | ||
| Whenever a descendant of a composite object in reference has been MOVED, the RCM check now simply moves it back instead of recreating the whole composite object. | ||
| Whenever a descendant of a composite object in reference has been PURGED, the RCM check can now recreate the composite object from the last baseline instead of the CR. Composite objects are no longer recorded in the CR. This enhances the performances when transitioning a CR to "completed", or setting a module under control or creating a new controlled object. | ||
| When changing the status of a Change Request to "completed", "impacts" links are created toward the descendants of the composite objects created using the CR in order to prevent those objects from being inadvertently deleted (and purged). This behaviour can be turned OFF thanks to the constant RCM_CREATE_IMPACT_LINKS_TO_CHILD_OBJECTS in the file adddins\irdrmfao\startup\usercallout\rcmusercallouts.inc | ||
| RCM triggers run faster as their code is now loaded at the startup. | ||
| A new controlled object shall not be created just after the selected object but after its last version instead. | ||
| RCM workspace control box: the buttons "working" and "latest reference" should not enable the the filter contained in the current view if this view is not filtered. | ||
| RMF menu | PM48598 | The command "Search suspect links from module" should be available on any module if the project is using RCM. |
| let any user with the right to create a project be able to create a RMF project, not just database managers | ||
| Make it possible to create a new RMF project with the "Administrator" user account | ||
| WEXP | PM46067 | When inserting a view filtered using DXL Filter whose objects are to be exported as a inline table, then the DXL Filter is not applied and the filter of the inserted view is applied instead. |
| PM47137 | WEXP should close the modules opened to export an inserted view as soon as the export of the view is completed. | |
| When revision marks are enabled, the generation is slow when the module has many baselines. The new algorithm requires only the reference baseline to be open instead of all the baselines starting from the reference baseline. | ||
| Word import macros | PM44277 | Error 5904 (Cannot Edit Range) with default options if there is a page break before the first title. |
| PM44278 | The prechecks should be run only on the part of the document that will be imported to DOORS. |
| Link | Date Released | Status |
|---|---|---|
13 July 2011 | Superseded |
| Component | CR | Description |
| Compare modules Transfer Analysis | 1017 | The analysis transfer may fail to create the attribute "TransferAnalysis_SuspicionGenerator" |
| 1036 | The static result attribute is set only taking into account the attribute "Object Text" when using the 'hierarchical comparison' algorithm | |
| 1044 | In the transfer analysis tool, set a more verbose warning message when an object has several comparison links (only one is expected and the others are ignored) | |
| Convert rows to objects | 890 | The script may fail if the first row has less cells than the other rows with an error "rowtoobj.inc:… unassigned array element (colMain[..]) |
| Create/Tag a RMF module | 787 | Sometimes the template is left open |
| The synchronisation of filtered views (of a module with its template) may fail on DOORS 9.3 if DOORS is not setup in English | ||
| The synchronization of filtered views may fail when the filter refers to attributes or values containing braces | ||
| When a error occurs while synchronizing a module with its template, the log should remain visible if an error occurred | ||
| Dashboard | 1030 | The "count links" metrics can only be displayed with the format "numerical". The two other types of columns (percent and bargraph) should be disabled. The creation of a new view is now also more intuitive. |
| 1034 | A DXL error occurs while updating the metrics if the root folder is the root of the database | |
| 1039 | The scopes of type 'fullname' are not properly processed if the path searched includes a project eg "/folder f/project p/module m" --> the module m is ignored | |
| 1040 | While updating a dashboard, some modules and folders may be ignored if their equivalent objects already exist but are deleted. New objects should be created instead. | |
| DOC | 978 | Display a warning whenever the expected DOORS baseline is missing (when running the "Generate Requirement History" for instance) |
| 1062 | Cannot generate a document using a WEXP server: the button "generate document in batch" is missing | |
| When generating a Word document, record the filter selected (in the attribute 'DOC Filter') | ||
| Exchange | 1021 | While importing a file, objects should be moved even if their universal ID is not defined in the file |
| 1035 | An object should not be deleted if one of its descendant should remain. Its attribute "XML Deleted" should be set instead. | |
| 1063 | Exchange fails when importing a deleted cell | |
| Explorer | 895 | Enable to take into account the WEXP attributes and types when displaying the delta between a module and its template |
| 1026 | The explorer may display an error "Can't communicate with the Graphviz COM object" when RMF is installed in workstation mode | |
| 1029 | Project names ending by a blank generate errors when saving a view or closing the explorer | |
| Running the command “Analyze links” on an object filtered out generates a DXL error in projectdb.inc:3572 | ||
| Generic datamodel | 983 | Traceability columns : if several linked objects have the same PUID and same absolute number then only one of them is displayed |
| Install | RMF is not properly installed if the setup is run in silent mode with the option “full install” (as opposed to “workstation”) | |
| Kitchen | 699 | Prevent the use of the script "flatten object hierarchy" in shareable edit mode |
| 778 | The "Delete Rich Text" command adds spurious newlines and do not preserve OLE | |
| Migration rules | 849 | SETOBJATTR does not work combined with a regular expression |
| Manage Objects | 1046 | The "Duplicate" button can generate errors if several objects are selected |
| 1047 | Display a more user-friendly error message when the "Duplicate" button fails to create a new object because the view is sorted | |
| 1060 | Error when switching from one module to another: "invalid index 1 to attribute type IE Object Type" | |
| PFM | Contextual attributes are now computed more efficiently | |
| When editing a contextual attribute of type "String", the message "Please select a parameter" should not be displayed if the key ENTER is pressed | ||
| Display a warning message if a contextual attribute has been edited but the modification has not been applied and is about to be lost | ||
| Prevent from setting a contextual attribute of type Integer or Real with a value that is not of that type | ||
| Renumber PUID | 1041 | If a PUID does not match the expected format and is left unmodifed (default "Don't modify PUID" option), then the internal counter may get incremented though under certain conditions |
| RCM | 1049 | Reduce the time needed to set a module under RCM control |
| 1054 | CR "in progress" created with a TREK version older than 5.3 are not properly migrated, which results in controlled objects remaining "in working" when the CR is accepted | |
| 1058 | The synchronize CR command may fail with an invalid lock request error message | |
| WEXP | 259 | Describe the limitations of the option "Use Word Revision Marks on changed objects" in the reference manual |
| 666 | Enable to rotate the column title of a table (by appending " R" to the column title in the DOORS view) | |
| 771 | The option 'allows table rows to break across pages' is ignored when exporting inserted views in RTF | |
| 795 | Prevent the WORD window from switching from minimized to normal state and vice versa, to avoid slowing down the export (only occurs with MS Word 2000) | |
| 897 | Inserted views should include deleted objects (currently exported only if using the RTF mode) | |
| 904 | In a list with bullets, a bullet should not be formatted as the preceding line | |
| 926 | Clarify the use of the attribute “WEXP File Name” to include sub-documents in the WEXP manual | |
| 975 | Clarify the WEXP manual about the extraction of UML diagrams: the interface with the modeling tool has to be implemented. Only the old versions of Rhapsody are natively supported. | |
| 1024 | Ability to define the style for isolated OLE in the attribute Paragraph style | |
| 1027 | "WEXP traceability view" backward compatibility : the last separator (the fifth colon) should not be mandatory | |
| 1037 | Do not display an error message when starting WEXP from a module that does not belong to a RMF project | |
| 1051 | When using the [Autofit to table content] setting, sometimes tables are not autofitted | |
| 1052 | WEXP cannot run in batch | |
| 1053 | When inserting a view, the value of the module attribute "WEXP Base Heading Style" (if exists) must be handled as an offset to be added to the style level of the headings --> currently doesn't work with RTF tables or templates not in French | |
| 1059 | When an object contains some text followed by an OLE, do not apply a style to the OLE to prevent the text from losing its indentation | |
| The formatting of the text within a DOORS table can sometimes be lost | ||
| Inline views: objects in-between 2 objects exported with the same inline view may not be exported if - the export view is not filtered - and the inline view is filtered and does not display the in-between objects | ||
| Word macros file | 767 | Heading numbers are always removed even when the option “Remove heading numbers” is off Rename this option “Record heading numbers” which is ON shall record the heading numbers into the object attribute “IE Original Heading number” |
| 930 | If the target module already exists, the "Module description" field is active and accept input, but though the description input is subsequently discarded | |
| 931 | The boolean values of the user defined properties shall not be recorded in the regional language but in English | |
| 1012 | Sign the macros contained in the file “irdrmfao.dot” so that the macro security level can be set to High | |
| 1045 | Extra characters may be displayed at the beginning of the “current DOORS path” field when using DOORS 9.3 with regional settings different from English | |
| Miscellaneous | 1042 | DXL errrors in the file "no_rmf_startup.dxl" available in the free addon “lib_no_irdrmfao.zip” allowing to open, without RMF, modules edited using RMF |
| Link | Date Released | Status |
|---|---|---|
17 December 2010 | Superseded |
| Component | CR | Description |
| Dashboard | 980 | Updates and exports fail in batch |
| 982 | The scope of a metric may not be recorded properly | |
| Exchange | 993 | deleted objects cannot be moved during an import (ERROR: Cannot move object xxx after/below object YYY) |
| Explorer | 1005 | DXL error when selecting a view in the "Model" tab (on the left) and then running the command "Edit item in Profile" |
| Configure module | 1004 | cannot modify the list of the rules to be checked |
| 1006 | 1) grey out the RCM option "Repair out-link modification of an object in reference" if "Change control mode"="not formal authorized" (also implemented in the dialog box 'configure project') 2) close the dialog box if the user closes the module 3) enable to open the dialog box even if the module is not in exclusive edit mode, but disable the dialog box if so | |
| Module synchronization | 985 | while synchronizing a view the justification of the columns is ignored |
| Convert rows to Objects | 986 | Running “RMF/Convert rows to Objects” with the option “Delete table after conversion” enabled, generates a runtime error in DOORS 9.2.0.4 |
| Project Configuration | 988 | The Project Configuration may crash if it is run in a row just after upgrading the project |
| Manage Objects | 991 | a DXL error “Canvas not realized” may occur on DOORS 9.2.0.2 (and over) if PFM is used |
| Project upgrade | 1001 | error while upgrading a project from TREK 5.2 (or earlier) to RMF: "invalid default value 'RMF Objects' for attribute 'RCM Control Mode'" |
| RCM | 972 | Error when assigning a CR to a user that belongs to the group of CR managers : ERROR: Cannot modify the access rights of ‘CR’ : The user ‘admin TREK’ doesn’t have control access |
| 984 | the RCM object trigger should prevent from creating a new version if the module is not set up for PFM | |
| 995 | add a new status “to be reviewed” in the lifecycle of a Change Request | |
| 996 | add a new group of users allowed to create Change Requests (but not to review and manage them) | |
| 1013 | RCM suspect links: display the text of the child objects of the current and proposed targets | |
| 1018 | RCM close trigger: if a controlled module is closed while editing in place an attribute, the modification is saved without confirmation message and the module is closed | |
| 1020 | when creating a new object version, the previous one should not remain selected | |
| PFM | 989 | if PFM is ON, when displaying a traceability column, you may get a RCM message “ERROR ASSERTION FAILED : the configuration (…) is not available in descriptor (…) at …” |
| 990 | the ‘insert DXL column’ command shall take into account the limit to 32 columns only in a view | |
| 994 | editing or creating a parameter with the ‘PFM information’ window makes the window of the current formal module stay on top of all the other DOORS windows | |
| 997 | the PFM setup should be able to convert the DXL columns created by the traceability wizard | |
| 999 | the value of a contextual attribute of type ‘text’ may be altered | |
| 1000 | Ability to add user-defined commands into the PFM browser (in the ‘tools’ menu) | |
| WEXP | 992 | when exporting a document with a PFM filter, WEXP records in a custom property of the generated MS Word document the name of the selected PFM configuration (this property is named “PFM Configuration” and it is created if needed) |
| 998 | When using MS Word 2000, isolated OLE are magnified by 33% | |
| 1002 | when exporting using the current filter some objects may not be exported (the one that would not have been visible if the filter of the view had been used instead) | |
| 1007 | WEXP does not export the text "A = B<<5 and C>>2" correctly, it renders "A = B 2" except if the usercallout “usercallout_executePostProcessModAttrs” is modified to return false (in the file wexp/include/usercallouts.inc) | |
| 1009 | WEXP: the text exported using object templates may be truncated (if it contains line breaks and the option "Treat line breaks in Object Text as new paragraphs" is not equal to "Always") | |
| 1014 | the references to module attributes <<attr>> located in headers or footers are not correctly processed if the option "Do not strip unsupported RTF markers before copy/paste" is ON and the option "Treat line breaks in Object Text as new para" is not equal to "Always" | |
| 1015 | MS Word may hang when processing an inserted view in RTF format if the option "Do not strip unsupported RTF markers before copy/paste" is enabled | |
| Startup | 1003 | RPE fails to open a DOORS session if RMF is installed |
| Silent uninstallation | 1016 | some files are not removed while uninstalling RMF in silent mode (among which the uninstall EXE file and the files named ‘irdrmfao.dxl’ located in the HOME directory of DOORS) |
| Link | Date Released | Status |
|---|---|---|
16 July 2010 | Superseded |
Table of Contents:
| Link | Date Released | Status |
|---|---|---|
22 April 2011 | Current |
| Component | CR | Description |
| Compare modules Transfer Analysis | 1017 | The analysis transfer may fail to create the attribute "TransferAnalysis_SuspicionGenerator" |
| 1036 | the static result attribute is set only taking into account the attribute "Object Text" when using the 'hierarchical comparison' algorithm | |
| 1044 | In the transfer analysis tool, set a more verbose warning message when an object has several comparison links (only one is expected and the others are ignored) | |
| Convert rows to objects | 890 | The script may fail if the first row has less cells than the other rows with an error "rowtoobj.inc:… unassigned array element (colMain[..]) |
| Create/Tag a RMF module | 787 | Sometimes the template is left open |
| Dashboard | 1030 | the "count links" metrics can only be displayed with the format "numerical". The two other types of columns (percent and bargraph) should be disabled. The creation of a new view is now also more intuitive. |
| 1034 | a DXL error occurs while updating the metrics if the root folder is the root of the database | |
| 1039 | the scopes of type 'fullname' are not properly processed if the path searched includes a project eg "/folder f/project p/module m" --> the module m is ignored | |
| 1040 | while updating a dashboard, some modules and folders may be ignored if their equivalent objects already exist but are deleted. New objects should be created instead. | |
| DOC | 978 | display a warning whenever the expected DOORS baseline is missing (when running the "Generate Requirement History" for instance) |
| Exchange | 1021 | while importing a file, objects should be moved even if their universal ID is not defined in the file |
| 1023 | Grey out the Exchange menu if the current project is not a RMF project | |
| 1035 | an object should not be deleted if one of its descendant should remain. Its attribute "XML Deleted" should be set instead. | |
| Explorer | 895 | enable to take into account the WEXP attributes and types when displaying the delta between a module and its template |
| 1026 | The explorer may display an error "Can't communicate with the Graphviz COM object" when RMF is installed in workstation mode | |
| 1029 | Project names ending by a blank generate errors when saving a view or closing the explorer | |
| Generic datamodel | 983 | traceability columns : if several linked objects have the same PUID and same absolute number then only one of them is displayed |
| Kitchen | 699 | prevent the use of the script "flatten object hierarchy" in shareable edit mode |
| 778 | the "Delete Rich Text" command adds spurious newlines and do not preserve OLE | |
| Manage Objects | 1046 | the "Duplicate" button can generate errors if several objects are selected |
| 1047 | display a more user-friendly error message when the "Duplicate" button fails to create a new object because the view is sorted | |
| RCM | 1013 | suspect links: display the text of the child objects of the current and proposed targets |
| 1018 | Close trigger: if the user closes a controlled module while editing in place an attribute, the modification is saved without confirmation message and the module is closed | |
| Renumber PUID | 1041 | if a PUID does not match the expected format and is left unmodifed (default "Don't modify PUID" option), then the internal counter may get incremented though under certain conditions |
| WEXP | 259 | describe the limitations of the option "Use Word Revision Marks on changed objects" in the reference manual |
| 666 | enable to rotate the column title of a table (by appending " R" to the column title in the DOORS view) | |
| 771 | The option 'allows table rows to break across pages' is ignored when exporting inserted views in RTF | |
| 795 | prevent the WORD window from switching from minimized to normal state and vice versa, to avoid slowing down the export (only occurs with MS Word 2000) | |
| 897 | Inserted views should include deleted objects (currently exported only if using the RTF mode) | |
| 904 | in a list with bullets, a bullet should not be formatted as the preceding line | |
| 926 | clarify the use of the attribute “WEXP File Name” to include sub-documents in the WEXP manual | |
| 975 | Clarify the WEXP manual about the extraction of UML diagrams: the interface with the modeling tool has to be implemented. Only the old versions of Rhapsody are natively supported. | |
| 1007 | WEXP does not export the text "A = B<<5 and C>>2" correctly, it renders "A = B 2" except if the usercallout “usercallout_executePostProcessModAttrs” is modified to return false (in the file wexp/include/usercallouts.inc) | |
| 1009 | the text exported using object templates may be truncated (if it contains line breaks and the option "Treat line breaks in Object Text as new paragraphs" is not equal to "Always") | |
| 1014 | the references to module attributes <<attr>> located in headers or footers are not correctly processed if the option "Do not strip unsupported RTF markers before copy/paste" is ON and the option "Treat line breaks in Object Text as new para" is not equal to "Always" | |
| 1015 | MS Word may hang when processing an inserted view in RTF format if the option "Do not strip unsupported RTF markers before copy/paste" is enabled | |
| 1024 | ability to define the style for isolated OLE in the attribute Paragraph style | |
| 1027 | "WEXP traceability view" backward compatibility : the last separator (the fifth colon) should not be mandatory | |
| 1037 | do not display an error message when starting WEXP from a module that does not belong to a RMF project | |
| Word macros file | 767 | Heading numbers are always removed even when the option “Remove heading numbers” is off Rename this option “Record heading numbers” which is ON shall record the heading numbers into the object attribute “IE Original Heading number” |
| 930 | if the target module already exists, the "Module description" field is active and accept input, but though the description input is subsequently discarded | |
| 931 | the boolean values of the user defined properties shall not be recorded in the regional language but in English | |
| 1012 | sign the macros contained in the file “irdrmfao.dot” so that the macro security level can be set to High | |
| 1045 | Extra characters may be displayed at the beginning of the “current DOORS path” field when using DOORS 9.3 with regional settings different from English |
| Link | Date Released | Status |
|---|---|---|
22 October 2010 | Superseded |
| Component | CR | Description |
| Exchange | 971 | On DOORS 8.3, importing with RMF Exchange a module with more than 500 links originating from one object fire an exception “stack overflow” and the operation is stopped. The problem has been solved by writing a more optimized code in the import operation. |
| RCM | 972 | Error when assigning a CR to a user that belongs to the group of CR managers : ERROR: Cannot modify the access rights of 'CR' : The user 'admin TREK' doesn't have control access |
| WEXP, Spooler | 973 | The export mode “As Book / As Table” selected in the GUI is not taken into transferred to the spooler, and only the default mode (As Book) was possible in batch mode. Thios option is now taken into account in interactive and batch mode. |
| Exchange | 974 | When using the option “move existing objects according source” on RMF 5.4.0.3 and all previous versions in Exchange import operation, the reorganization of the updated module structure may fail with a DXL error message display. The reorganization algorithm has been corrected to suppress this error. |
| RCM filtering | 977 | a DOC configuration whose version number would contain a “.” in the suffix would not be displayed |
| RCM, data model | 979 | The PUID column generates errors when displaying Working objects in DWA. A similar error exists also for RMF traceability columns. To update existing projects: -execute the “patch puid” script (correction of PUID and traceability columns) -you may also re-configure modules by applying the DXL column (only for the PUID columns in the current module) |
| Dashboard | 980 | updates and exports fail in batch |
| RCM / Close | 981 | RCM->Close may not close the module if the number of references to the module is greater than 1 |
| Dashboard | 982 | the object scope of a metric is sometimes not recorded |
| Module synchronization | 985 | while synchronizing a view the justification of the columns is ignored |
| Convert rows to Objects | 986 | Running "RMF/Convert rows to Objects" with the option "Delete table after conversion" enabled, generates a runtime error in DOORS 9.2.0.4 |
| RMF Menu | 987 | the RMF menu can take a while to open if the current folder is far from the root of the project |
| Project Configuration | 988 | The Project Configuration may crash if it is run in a row just after upgrading a project |
| Exchange | 993 | deleted objects cannot be moved during an import (ERROR: Cannot move object xxx after/below object YYY) |
| RCM | 995 | add a new status "to be reviewed" in a the lifecycle of a Change Request |
| RCM | 996 | add a new group of users allowed to create Change Requests (but not to review and manage them) |
| WEXP | 998 | When using MS Word 2000, isolated OLE are magnified by 33% |
| Project upgrade | 1001 | error while upgrading a project from TREK 5.2 (or earlier) to RMF: "invalid default value 'RMF Objects' for attribute 'RCM Control Mode'" |
| WEXP | 1002 | when exporting using the current filter some objects may not be exported (the one that would not have been visible if the filter of the view had been used instead) |
| Startup | 1003 | RPE fails to open a DOORS session if RMF is installed |
| Configure module | 1004 | cannot modify the list of rules to be checked |
| Explorer | 1005 | DXL error when selecting a view in the "Model" tab (on the left) and then running the command "Edit item in Profile" |
| Configure module | 1006 | 1) grey out the RCM option "Repair out-link modification of an object in reference" if "Change control mode"="not formal authorized" (also implemented in the dialog box 'configure project') 2) close the dialog box if the user closes the module 3) enable to open the dialog box even if the module is not in exclusive edit mode, but disable the dialog box if so |
| Link | Date Released | Status |
|---|---|---|
No download available | 15 April 2010 | Superseded |
| Component | CR | Description |
| RCM | 866 | If a working controlled object is cancelled but the module is not saved afterward, then the RCM check now recreates its impact object |
| DOC, RCM | 898 | DOC option "include RCM working versions" performance issue (the module is saved each time an object is set in reference) |
| Module Create/Tag, Compare/Transfer | 907 | To avoid for the user to always have to close the log dialog box, a new option has been added allowing to close automatically the log dialog box when no error have been recorded during attribute and view definition creation or update. |
| RCM | 908 | Ability to run the RCM migration script in batch (script located in “irdrmfao/misc/migrate” that is needed to migrate the RCM controlled modules created with TREK 5.2 or below) |
| RCM, Manage Objects | 909 | When clicking the "select CR" button, only the CR that can be used with the current module are displayed |
| Dashboard | 938 | The metrics restricted to RMF objects were badly defined in the dashboard of the ATM2000 example (they applied to all objects instead of only RMF objects) |
| Dashboard, RCM | 939 | A metric can now apply to all the versions of an object (the check boxes 'working' and 'reference' couldn’t be both checked) |
| Dashboard | 940 | Prevent from typing in the 'type of metric' drop-down list (an invalid input generates an error) |
| install | 941 | The silent installation fails in workstation mode (bad or missing parameter ‘IrdrmfaoDir’ in the file irdrmfao.ini) |
| RCM | 942 | Publish the RCM API |
| integrity check | 943 | Navigating to an object may fail (-R-E- DXL: |
| RCM, Suspect links | 946 | Objects with suspect links are not displayed if the PUID contains a character /. To be able to display the PUID in a DOORS TreeView, the / is replaced by a \ in the GUI. |
| RCM, Suspect links | 947 950 | The suspects links of a working object were not found |
| Word Importer | 948 | A VB exception is fired when using the option “Extract Words from OLE” with Word 2007. |
| WEXP | 949 | An error occurs when starting the Word generation on a non initialized module. The cause was a non protected access to an attribute. The defect has been corrected.. |
| RCM, Change Request | 951 | Accepting a Change Request when the impacted modules are opened in sharable mode may rise an anomaly; leaving the data in an inconsistent state. The defect has been corrected. |
| RCM, Close Trigger | 952 | Trying to close a baseline if the current module is till opened generates an infinite loop of close triggers. The reason was that the module(Trigger)dxl primitive always return the current module, not the baseline. This anomaly has been closed by using another primitive. |
| Dashboard | 953 | An anomaly has been detected when a module included into a dashboard scope is opened with showAncestors option turned on or has this option in the default view. The dashboard mechanism has been modified to avoid this problem. |
| Dashboard | 954 | When modifying dashboard scopes, the deleted objects corresponding to items removed from the scope are still taken into account when computing folders and projects values. This defect has been corrected. |
| Dashboard | 955 | The performance of the dashboard was very poor in case of RCM module, and if the number of metrics is high. The performance has been improved by optimizing the object scope mechanism and allowing reuse of scopes between different metrics. |
| Dashboard | 956 | The dashboard object scope GUI is too restrictive when working with metrics associated with “Any Module” or “Any RMF” types. This defect has been corrected. You can now enter any attribute name without any control. |
| RCM, Manage Object | 958 | The Select CR operation from Manage Object was not able to differentiate two CRs associated with two modules in the same folder with similar names (“SSS” and “SSS2” for example). This defect has been corrected. |
| RCM | 961 | the close trigger should detect the creation of an object by duplication and fix this issue (by removing it) |
| Manage Objects, RCM | 962 | a button "duplicate" has been added into the Manage Objects GUI to allow duplicating an object even if it is controlled by RCM |
| RCM | 963 | if the user closes a module without saving the modification whereas a new controlled object version has been created, then the RCM check removes the impact object in the related CR module |
| Exchange | 964 | importing modules may leave some locks on the modules imported and thus impede subsequent imports |
| RCM | 965 | whenever a module has been closed using the command RCM / Close then the semantic links should be checked when opening the module in exclusive edit mode afterwards (if the project is configured accordingly) |
| RCM | 966 | whenever a module is opened in exclusive edit while it has been closed without saving (using the command RCM / Close), RCM no longer report the same errors on composite objects several times (under certain circumstances) |
| Link | Date Released | Status |
|---|---|---|
No download available | 27 November 2009 | Superseded |
| Component | CR | Description |
| Word Generation | 937 | In some circumstances, the table of contents of a document was not updated at the end of the generation. The code has been modified to solve this problem. |
| Word Generation | 936 | When executing a user VB macro that is undefined or invalid a strange error message was recorded: While exporting DOORS object …, Word has reported the following OLE failure: (on calling method 'Run') OLE problem: Can't move focus to the control because it is invisible, not enabled, or of a type that does not accept the focus. Backtrace : |
| RCM, CR management | 935 | Some modification of the CR access rights have been introduced when users or groups are assigned to CR: -Delete perm for authors is now propagated, and no more associated with the CR module -Author access rights are removed when cancelling or accepting a CR |
| RCM, CR management | 934 | The Cancel of a Change Request does no more delete the existing impacts into the CR module. The impact objects are synchronize with the working objects before the deletion of the working to record the working state, allowing to keep the history of the non accepted proposal. |
| Explorer | 933 | A compatibility issue has been detected between the Explorer and the fix n°2 of DOORS 9.2. A DXL error on canvas realization occurs when executing the Explorer. The code of the Explorer has been updated to take care of this DOORS behavior modification. |
| RCM, Object Manager | 932 | RCM / Create a RMF Object : an error occurs whenever several objects are selected when creating a new RMF object in a RCM controlled module |
| Object Manager | 929 | The label “objets” has been replaced by “objects” in the Object Manager dialog |
| Explorer | 928 | The colors used in the graphical views of the explorer may now be redefined by changing constant values in the not encrypted file colors.inc |
| Dashboard | 927 | The main dialog box display is not refreshed correctly with DOORS 9.2 when using a add or modify item operation (scope, metric, data or export item) |
| Dashboard | 925 | If a metric is associated with a module or a template, this parameter must not be taken into account when using a EveryLink or AnyLink object scope in the definition of the criteria of the distant module. A text field is provided to allow the attribute name definition, without the necessity to select a name in the attribute list. |
| Dashboard | 924 | When modiyfing an existing, it may be necessary to enter again the template or module type associated with the metric |
| Dashboard | 923 | A regression in one DOORS 9.2 dxl primitive gives a wrong display in the alarm dxl column display |
| Dashboard | 922 | Inconsistency in the use of the object scopes for object count/summation and the other types of metrics. The summation metric may use now two object scopes: *the “standard” object scope as for other metrics *an object scope defined by the Parameter button in order to specify the set of object to count |
| Dashboard | 921 | The aggregate status of an alarm for a folder or a project was not taking into account the last object |
| Dashboard | 920 | If the status of an alarm does not change, no history entry should be created when refreshing a dashboard module |
| Dashboard | 919 | The Integrity check is now integrated with the Dashboard, to allow a global understanding of the integrity status into the project. The predefined “data” have been added into the dashboard. |
| Dashboard | 918 | The Dashboard kernel has been modified to automatically take into account the modules under RCM control. The metrics results are not modified when a standard module is put under RCM. By default, metrics are executed on the last reference version. |
| Exchange | 917 | The import operation fails if the module does not belong to a RMF project . |
| Object Manager | 912 | Scrolling objects gets slower when the Manage Objects GUI is open and the tab Create is displayed. |
| DOC, RCM | 910 | The option controlling the inclusion of RCM Working versions into DOC baselines should allow three modes: -abort baselining in case of working -continue baselining without any action in case of working -accept working objects and then baseline |
| RCM | 911 | When creating a new version of a controlled object the standard view is loaded (and the current view loaded back) without reason |
| RCM | 905 | The object trigger that control the action associated with the double click of a column cell in a view should have a smarter behavior, to eliminate unuseful messages. |
| RCM, Object Manager | 903 | RCM / Manage Objects : the 'Cancel working' button fails to delete a version created by the 'unidentify' button if the object is composite and the current object is not the root object and generate the RCM Error "No impact object associated with object.." |
| RCM, Object Manager | 902 | If the current object is a child object of a composite object, then clicking the 'modify' or 'delete' buttons creates a copy of the child object instead of the whole composite object |
| Explorer | 901 | Sub-projects are displayed several times when running the "start linkset" and "start model linkset" commands, this anomaly has been corrected. |
| Integrity Check | 900 | Upward compatibility issue between TREK 5.3p2 and RMF 5.4 (different include files) |
| Module Tagging | 899 | When tagging a module by script, the wrong template can be used if the name of the template is identical to the beginning of the name of another template. The anomaly has been corrected. |
| Dashboard | 585 | When exporting a metric for baselines and also the current version, a metric is not exported if it is not defined in the first baseline. The anomaly has been corrected. |
| Dashboard | 550 | There is a problem on the definition of an alarm when the min or max value is not selected: the corresponding limit is reinitialized to 50% even if it should be empty. The anomaly has been corrected. |
| Link | Date Released | Status |
|---|---|---|
23 October 2009 | Superseded |
| Component | CR | Description |
| Utilities | 894 | Error when running the scripts "create link attribute" and "restore link from an attribute |
| irdrmfao.dot | 893 | Word to DOORS macro crashes if the option "Convert Table to OLE" and "extract words from OLE" are both selected |
| RCM | 892 | Errors happens if the CR are located at the root of the project |
| DOC | 891 | Some WEXP options set into the manage documents GUI are not saved |
| RCM | 889 | Ability to use the control box on baselines |
| Exchange | 888 | No detection of a missing object attribute to define the color of a column when restoring a view |
| Exchange | 887 | Compatibility issue when importing data generated using a version of RMF < 5.4 (a version of TREK) |
| Traceability columns | 886 | Issue with indents and bullets.If the text of the linked object ends with a paragraph with indent and/or bullet, then the next paragraph (the separator or an attribute) used to have the same indent and/or bullet. This has been fixed. |
| Manage objects | 885 | If IE PUID is a DXL attr, the PUID of the next object to be created should not be displayed (in the manage object) because it is invalid |
| RCM | 884 | The RCM "delete" button issues an error message if IE PUID is a DXL attr |
| WEXP | 883 | Poor performance when inserting revision marks |
| WEXP / spooler | 882 | Prevent MS Word from prompting the user |
| Multi project environments | 881 | Some RMF command run at project level may fail whenever the current module does not belong to the current project |
| DOORS Find vs RCM trigger | 880 | RCM triggers should not prevent the DOORS Find command from entering in edition into controlled object that are in reference but not the latest version |
| Manage objects | 879 | Baselines should be supported |
| Configure module | 877 | The code of the DXL column displaying the PUID should be modifiable |
| Configure module | 876 | The conversion of the PUID column may fails on DOORS 9.1 due to a regular expression incompatibility |
| Dashboard | 875 | Compatibility issue between RMF 5.4 and dashboard modules created in previous versions |
| irdrmfao.dot | 874 | The MS word macro converting tables into OLE fails on MS Word 2007 |
| DXL Filter | 873 | Attribute whose name contains braces or accents are not supported |
| Integrity check | 872 | The project delivered as example is not correct (integrity.dpa) |
| Manage objects | 871 | DXL error when setting a MS style to the last object |
| Menus | 870 | RMF shall tolerate so that a RMF project be in a folder that users have no access to |
| RCM | 869 | Make it possible to define "IE PUID" as a DXL |
| WEXP Object templates | 867 | A character is removed |
| WEXP Object templates | 865 | WEXP issue with object template containing tables : OLE not exported |
| WEXP | 864 | WEXP issue in multi-language mode on "Figure Caption" and "Table Caption" |
| WEXP | 863 | WEXP issue in multi-language mode on "OLE Width" and "OLE Height" |
| Link | Date Released | Status |
|---|---|---|
27 May 2009 | Superseded |
Related Information
[{"Product":{"code":"SSKR2T","label":"IBM Engineering Requirements Management DOORS"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Rational DOORS Requirements Management Framework Add-on","Platform":[{"code":"PF033","label":"Windows"}],"Version":"6.0;6.1","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Was this topic helpful?
Document Information
Modified date:
01 May 2020
UID
swg27036730