209346
Animation: When user selects Enable Operation Calls in the Advanced Instrumentation Settings window, the generated code results in compilation errors.
This problem has been corrected.
223668
Animation: When using animation for a SysML activity diagram, the generated code results in compilation errors.
This problem has been corrected.
102769
Rhapsody API: Request that a method be added to the IRPFlowchart interface for adding a reference activity.
The IRPFlowchart interface now includes a method called addReferenceActivity.
105972
Rhapsody API: Request that the API provide a way to download application to (and unload application from) a target.
The following methods have been added to IRPApplication: connectToTarget, downloadToTarget, unloadFromTarget, and disconnectFromTarget.
109121
Rhapsody API: Property IRPFlow.direction does not behave as expected.
This problem has been corrected.
110391
Problem compiling the com.telelogic.rhapsody.wfi.rhapsodyListeners sample.
This problem has been corrected.
110462
Rhapsody API: When you use the Rhapsody API to add classes to an OMD, their ports are not displayed even though the appropriate properties are set to display ports.
This problem has been corrected.
219381
Rhapsody API: Request that a method be added to the interface IRPRelation to get the association class for a relation.
A new method called getAssociationClass() has been added to the interface IRPRelation.
75679
UI: Request that the GUI provide drop-down lists for setting the "Default Value" field for parameters of a template class, and for setting the "Value" field for parameters for a template instantiation.
This feature has been added.
90787
Code Generation (C++): Incorrect code generated for link that instantiates association between a class and a template class.
This problem has been corrected.
98639
Code Generation (C++): Incorrect code generated when a template class has ports.
This problem has been corrected.
101180
Code Generation (C++): When using templates, Rhapsody generates an unnecessary .cpp file.
This problem has been corrected. cpp file is now generated only when instrumentation is set to Animation or Tracing
104511
Code Generation (C++): Request that Rhapsody automatically generate the "typename" keyword in method declarations where this is required.
Since support for the "typename" keyword varies between compilers, an environment-level property is used to specify generation of this code. To have "typename" generated, set the property CPP_CG::[environment]::UseTemplateTypename to True.
105757
Code Generation (C++): Property UseTemplateTypename does not affect code generation as it should.
This problem has been corrected.
106164
Code Generation (Ada): Request that RhapsodyCL be capable of generating Ada code.
This is now possible. When generating Ada code with RhapsodyCL, make sure to include "-lang=ada" in the command.
108926
Code Generation (C++): When using template specialization, the generated code does not compile.
This problem has been corrected.
109466
Code Generation: If a project is read-only and you regenerate the makefile, the resulting file sometimes differs from the one generated when the project is not read-only.
This problem has been corrected.
109653
Code Generation (C++): When you try to use RhapsodyCL to generate code on Red Hat Linux 5, a segmentation fault results.
This problem has been corrected.
109811
Code Generation: In certain situations, code is not generated for Actors.
This problem has been corrected.
109841
Reverse Engineering: When adding files for reverse engineering in tree view, Rhapsody seems to have a problem with directories that begin with an underscore.
This problem has been corrected.
109860
Reverse Engineering: If you use the Tree View to select files for reverse engineering, packages are merged when the files are imported.
This problem has been corrected.
109880
Code Generation (C++): Objects running in the wrong task.
This problem has been corrected.
110309
RiA: Request that the RiA documentation include more detailed information regarding the updated Ada95 OXF, and the implications of the changes that were made.
This information has been added to the documentation.
110329
Code Generation: When using RhapsodyCL to generate code with dependencies, return code was 0 even though the code generation failed.
This problem has been corrected.
110359
Roundtripping (C): If you remove the keyword "static" from an existing function (or add it), it has no effect on the code regenerated after roundtripping.
This problem has been corrected.
110365
Reverse Engineering (Java): When code is regenerated following reverse engineering, Rhapsody removes package names from classes but does not add the required import statements.
This problem has been corrected.
110440
RiA: Incorrect code generated for interface with dependency, resulting in compilation errors.
The code is now generated correctly, but the user must explicitly add the dependency to the class that is generalized from the interface.
110445
Code Generation: If .sbs file of Simulink block is set to read-only, .h file that is generated does not contain declarations for flowports.
This problem has been corrected.
110454
Code Generation (C): When the scope of a component is limited to only some files in a package, the generated code has types appearing after the variables, resulting in compilation errors.
This problem has been corrected.
110465
Roundtripping (C): After roundtripping, code for enums is incorrect - last literal is followed by comma.
This problem has been corrected.
214261
Code Generation: If the property GeneratedCodeInBrowser in set to True, Rhapsody does not generate flowport-specific code in setters.
This problem has been corrected.
214280
Code Generation: Values of attributes are not propagated through flowports in parts which are implicit.
This problem has been corrected.
215587
Code Generation: When property ActiveBaseUsage is set to False, there are mismatches in the generated code between function definitions and calls to those functions.
This problem has been corrected. However, you must also modify the value of the property ReactiveInit to match the code required.
216713
Reverse Engineering: After reverse engineering code containing nested preprocessor definitions, #endif is missing in the generated code.
This problem has been corrected.
217000
Code Generation: Code generation takes longer than with previous version of Rhapsody.
In this version of Rhapsody, significant improvements have been made in terms of code generation time.
218962
Code Generation (C): The property File::InvokePostProcessor does not affect code for ports - the post-processor is not called.
This problem has been corrected.
219548
Code Generation: When using the Rhapsody Eclipse Platform Integration with Java, there is a discrepancy between the model package structure and the folder structure of the generated code.
This problem has been corrected.
219814
Code Generation (C++): After making code changes in the Active Code View window, package code disappears when code is regenerated.
This problem has been corrected.
219898
Code Generation: Operation disappears from code after roundtripping.
This problem has been corrected.
219971
Code Generation: Code generation time is significantly longer when model contains component files.
This problem has been corrected.
220203
Reverse Engineering: When a profile contained values for the properties CPP_CG::Configuration::DefaultImplementationDirectory and CPP_CG::Configuration::DefaultSpecificationDirectory, these values were not displayed in the appropriate fields on the Mapping tab of the Reverse Engineering Advanced Options dialog box.
This problem has been corrected.
220946
Code Generation (C++): After roundtripping, generated code contains duplicate global comment for friends.
This problem has been corrected.
220992
Roundtripping (C++): When a friend relationship between a class and a template function is roundtripped, the generated code does not compile because the friend keyword is generated in the wrong location.
This problem has been corrected.
221166
Code Generation: When SysML project that uses flowports is broken into a number of components, the function InitRelations is missing in the generated code.
This problem has been corrected.
221636
Code Generation: In getter generated by Rhapsody, code does not indicate that the return type is a pointer to the user-defined type rather than the type itself.
This problem has been corrected.
222088
Roundtripping: After roundtripping, code contains extra attributes.
This problem has been corrected.
222190
Code Generation: When using RhapsodyCL to generate code with dependencies, return code was 0 even though the code generation failed.
This problem has been corrected.
222415
Roundtripping: After roundtripping, attributes are missing from structures.
This problem has been corrected.
222533
Code Generation: Rhapsody reports fatal error after code generation invoked.
This problem has been corrected.
222544
Roundtripping (C++): Rhapsody reported a parsing error when roundtripping compilable code that contained a superfluous namespace prefix.
This problem has been corrected.
223675
Code Generation: Forward declarations for private methods no longer appear with rest of forward declarations, appearing instead right before the function call. In some cases, this results in compilation errors.
This problem has been corrected.
223757
Request that it still be possible to work with Visual Studio 2005.
This is now possible. If you only have Visual Studio 2005, select Visual Studio 2008 during installation. Rhapsody will detect that only Visual Studio 2005 is installed and will create an appropriate MSVC9MAKE.bat file under share\etc. All the user has to do is recompile the framework and make sure the configuration environment is set to MSVC9.
224180
Roundtripping: When code is regenerated during roundtripping, "typename" is missing from template parameter declaration.
This problem has been corrected.
59609
DiffMerge: Request that Rhapsody support graphical merge for all diagrams.
DiffMerge now allows graphical merging of all diagram types.
94984
DiffMerge: Request that it be possible to graphically merge all diagram types.
This feature has been added.
95181
DiffMerge: Request that it be possible to graphically merge all diagram types.
This feature has been added.
101891
DiffMerge: Request that Rhapsody support graphical merge for all diagrams.
DiffMerge now allows graphical merging of all diagram types.
108979
DiffMerge: DiffMerge closes unexpectedly during attempt to merge sequence diagrams.
This problem has been corrected.
109337
DiffMerge: When exiting DiffMerge, the following error message is displayed: "Failed to deregister COM root object".
This problem has been corrected.
109805
Configuration Management: Request that Rhapsody warn the user when changes made to model elements impact elements that cannot currently be updated because they are read-only.
Now, if a change is made to an element, and there are dependent elements that are read-only, a dialog is displayed notifying the user of the problem. The dialog allows the user to check-out the read-only files, modify the element without modifying the dependent elements, or cancel the operation. This feature can be turned on/off using the boolean property General::Model::ShowPotentialUnresolvedReferences.
109852
Configuration Management: Conflict due to Rhapsody fetching units added by reference.
This problem has been corrected.
212384
Configuration Management: When working with ClearCase, Rhapsody closes unexpectedly when the cleartool checkout command is issued.
This problem has been corrected.
220543
Referenced units not loaded if relative path is long.
This problem has been corrected.
222026
DiffMerge: DiffMerge can't display Korean characters in the package pane, and merge attempt hangs when elements in sequence diagram contain Korean characters.
These problems have been corrected. DiffMerge now supports Korean characters.
222168
DiffMerge: DiffMerge reports no differences in cases where differences exist.
This problem has been corrected.
223333
Activity Diagrams: When user tried to connect action pin on an action to a second action, Rhapsody displayed the error message "You cannot create an object flow between two actions".
This problem has been corrected.
47185
In the diagram editor and browser, template instantiations should be shown with dependencies and "bind" stereotypes.
Now, if you define a stereotype called "bind", you can set a template instantiation by adding a dependency from an ordinary class to a template and applying the "bind" stereotype to it.
100175
Activity Diagrams: Request that it be possible to reorder swimlanes.
This capability has been added.
109059
Activity Diagrams: In certain situations, Rhapsody does not allow you to connect an Activity Flow to a Condition Connector. It displays the message "Illegal Target".
This is now possible when working in Analysis Only mode.
109127
Collaboration Diagrams: When a stereotype image is associated with a classifier role, the image is not displayed on the diagram until an update is forced by a user action such as changing display options.
This problem has been corrected.
109221
Object Model Diagrams: When using templates for policy-based instantiation, can't use inheritance arrow to point to class argument. When superclass is added in browser, inheritance arrow does not show up in the object model diagram.
If you put the class that represents the template parameter on the diagram, this is possible.
109223
Activity Diagrams: Request that it be possible to add swimlanes to subactivity diagrams.
Call Behavior elements can be used to reference other activity diagrams, and swimlanes can then be added to these referenced diagrams. In this version of Rhapsody, the introduction of a new element called Activity Frame provides a way to use action pins on such referenced diagrams to represent inputs and outputs.
109516
Activity Diagrams: Request that it be possible to rename package-level activity diagrams even if there is only one diagram in the package, and that it be possible to move such diagrams to different packages.
Both of these actions are now permitted.
109618
Statecharts: When using the Alt+drag feature to change the size of a state without changing the size of objects within the state, the size of the contained objects remains the same but any And lines are moved.
This problem has been corrected - And lines now remain in their original location when using Alt+drag.
109973
Request that the pop-up menu for objects in diagrams include an option for navigating directly to the class on which the object is based.
Now, when you display the pop-up menu for objects, the Class submenu includes an option called Locate In Browser.
110025
Object Model Diagrams: When you resize diagram elements while holding down the Alt key, port locations get messed up.
This problem has been corrected.
110075
Component Diagrams: If a component diagram is defined under a component, Rhapsody does not allow you to drag an interface from the browser to the diagram. Yet, in the same situation, you can create an interface on the diagram using the appropriate tool on the Drawing toolbar.
This problem has been corrected - you can now drag an interface to the diagram.
208961
Activity diagrams: Rhapsody does not allow you to draw an outgoing transition from a junction connector to a condition connector. It displays the message "Illegal Target".
This problem has been corrected.
209473
Activity Diagrams: Rhapsody does not allow you to draw an outgoing transition from a diagram connector to a condition connector. It displays the message "Illegal Target".
This problem has been corrected.
212852
Activity Diagrams: Request that it be possible to include Flow Final elements in activity diagrams.
This is now possible.
218524
Object Model Diagrams: When using the Alt+drag feature to change the size of a class without changing the size of contained elements, the locations of ports change.
This problem has been corrected. Now, when using Alt+drag, ports remain in their original locations.
219367
Sequence Diagrams: If you have used a "new term" to create a customized type of sequence diagram, the Open Reference Sequence Diagram menu option is grayed-out if the referencing sequence diagram is read-only.
This problem has been corrected.
220129
Activity Diagrams: Request that Termination State in activity diagrams be renamed Activity Final, which is the term used in UML.
This change has been made. In addition, the Features dialog for Activity Final has been modified such that you can no longer define actions for such a node (entry action, exit action, reaction in state).
220984
Object Model Diagrams: Flows not displayed on diagram after "Complete Relations".
This problem has been corrected. Before running "Complete Relations", make sure that all ports are visible.
221293
Statecharts: After adding an action to a transition, using the features dialog box, the trigger/guard/action is displayed for the transition even though the relevant properties were set to display the transition label.
This problem has been corrected.
222334
Sequence Diagrams: Messages are changed from synchronous to asynchronous after showing diagram frame.
This problem has been corrected.
223019
Sequence Diagram Comparison: For messages that are not synchronized, the relevant arrows are displayed in orange, but the corresponding text is not.
This problem has been corrected. Now, for messages that are not synchronized, the text is also displayed in orange. However, if the comparison finds changes in the arguments, the text will be displayed in pink.
223345
Activity Diagrams: Can't edit trigger/action on existing transitions in activity diagram. Relevant fields are grayed out in Features dialog box.
A property has been added to the pre75 compatibility profiles to allow editing of this information on diagrams from older versions.
223605
Request that the Move Without Contained menu option operate in a toggle manner, rather than requiring you to select the option before each such move that you would like to make.
This change has been made - now the menu option toggles the feature on/off. If you only want to perform one such move, you can hold down the Alt key while dragging.
79696
Framework: Framework code contains violations of MISRA 98 Rule 59 - statements forming the body of conditional or loop constructs must be enclosed in braces.
This problem has been corrected.
94187
Framework: On Linux, return code of sem_wait not checked in OXF (linuxos.cpp). This is significant with Linux kernel 2.6.
This problem has been corrected.
109416
MicroC Profile: Request that memory section mapping be added to the MicroC profile.
This feature has been added.
109945
Request that it be possible to use Rhapsody with both Visual Studio 6.0 and Visual Studio 2005 on the same computer.
This version of Rhapsody contains separate environments for Visual Studio 6.0 ("Microsoft") and Visual Studio 2008 ("MSVC9"). You just have to select the relevant environment.
224147
Framework: User application crashes when using OMTimerManager on 64-bit Linux.
This problem has been corrected.
104510
Request that Rhapsody support use of the "typename" keyword in type specification.
This is now possible - set the value of the property CG_CPP::(environment)::UseTemplateTypename to True.
107843
If you merge a unit into a model, and the model already contains a unit with the same filename, Rhapsody automatically adds a numerical suffix to the filename in order to differentiate it from the existing file. This is problematic in scenarios where it is important that the original name of the unit be maintained.
A new property, General::Model::DefaultUnitFileName, has been added. This property can be used to define a "template" for creating filenames on the basis of element names. In cases where there is a possibility that units will be merged from other models, this property can be used to establish unique file-naming schemes before development of the models begins.
108713
Code Generation: MISRA 98 Rule 13 violation: Although there are MISRA-C compliant typedefs in the framework, auto-generated code does not use them.
This problem has been corrected.
108717
Code Generation: In the MISRA98 profile, the property MainGenerationScheme is set to UserInitializationOnly. As a result, the operations DefaultComponent_Init and DefaultComponent_Cleanup are automatically generated by Rhapsody, but the generated code does not contain calls to these operations. This is a violation of MISRA Rule 52.
Two new properties, CG::Component::GenerateComponentInitialization and CG::Component::GenerateComponentCleanup, have been added to Rhapsody, and in the MISRA98 profile these properties have a default value of Never. As a result, the operations DefaultComponent_Init and DefaultComponent_Cleanup are not generated.
108718
MISRA Rule 52 violation - function DefaultComponent_Cleanup defined but not used.
When using the MISRA98 profile, this function is no longer generated by default. Generation of this function is controlled by the property CG::Component::GenerateComponentCleanup. This applies also to the function DefaultComponent_Init, which is controlled by the property CG::Component::GenerateComponentInitialization.
108719
MISRA Rule 52 violation - function Default_OMInitializer_Cleanup() defined but not used.
Now, if you set the value of the property CG::Package::GeneratePackageCleanup to Never, the function will not be generated.
108720
MISRA Rule 22 violation - static struct Test_reactiveVtbl accessed in only one function.
This problem has been corrected - the definition of Test_reactiveVtbl is now contained in the function that accesses it.
108951
When user tries to change project from C++ to Java, the values of certain language-specific properties are not updated accordingly.
This problem has been corrected.
109021
Request for a better mechanism to prevent the creation of unresolved model elements.
Now, if a change is made to an element, and there are dependent elements that are read-only, a dialog is displayed notifying the user of the problem. The dialog allows the user to check-out the read-only files, modify the element without modifying the dependent elements, or cancel the operation. This feature can be turned on/off using the boolean property General::Model::ShowPotentialUnresolvedReferences.
109331
UI: Request that it be possible to zoom by using the mouse scroll wheel while a certain key is pressed.
This feature has been added. You can now zoom in/out by using the scroll wheel while holding down the Ctrl key.
109458
Licensing: Request that Rhapsody allow "borrowing" of licenses.
This is now possible.
109460
Request for a better mechanism to prevent the creation of unresolved model elements.
Now, if a change is made to an element, and there are dependent elements that are read-only, a dialog is displayed notifying the user of the problem. The dialog allows the user to check-out the read-only files, modify the element without modifying the dependent elements, or cancel the operation. This feature can be turned on/off using the boolean property General::Model::ShowPotentialUnresolvedReferences.
109515
When using RhapsodyCL on CentOS, segmentation fault occurs.
This problem has been corrected.
109686
Rhapsody hangs when you try to copy a large number of elements.
This problem has been corrected.
109848
If a profile contains multiple stereotypes that share the same name but are applicable to different metaclasses, there are situations where these stereotypes are applied incorrectly.
This problem has been corrected.
110131
When using RhapsodyCL on Suse Linux, segmentation fault occurs if the model contains a sequence diagram.
This problem has been corrected.
110140
Installation: During installation of System Designer edition of Rhapsody, option for selecting TeamCenter is grayed-out.
This problem has been corrected.
110153
Panel Diagrams: Request that it be possible to use types defined in SysML profile (such as meter or second) with panel diagrams.
This is now possible. To see the SysML types, select the Display All Types check box on the Element Binding tab.
110177
Rhapsody truncates description entered for tag in Features dialog box due to limit on length.
The permissible length for element descriptions can now be modified using the new property General::Model::DescriptionTextLimit. The default value for the property is 32768 bytes.
110242
Model Checking: When using custom checks, many model elements are not checked against the rule, for example, events and ports.
This problem has been corrected.
110401
Request for tighter integration with Visual Studio in terms of roundtripping support, similar to Rhapsody's integration with Eclipse.
This feature has been added.
110436
Check Model (RiA): Port-related checks are disabled in RiA.
This problem has been corrected.
110466
Inherited substatechart with entry/exit and history connector results in corrupted repository.
This problem has been corrected.
110469
Installation: During installation, if you select both the Red Hat C++ libraries and VBA options, the VBA installation fails.
This problem has been corrected.
209663
RhapsodyCL's runexternalprogram command does not work.
This problem has been corrected.
211483
The (U) symbol is not displayed for unresolved events.
This problem has been corrected.
212676
When searching for missing units, Rhapsody brings the absolute file path into the model even though the value of the property ReferenceUnitPath is set to Relative.
This problem has been corrected.
214689
Model Checker: Request that the performance of the model checker be improved - a small change to the model can result in a long model-checking process before code is generated.
Now, when code is generated, model checking is performed only for the elements that have been modified.
216753
Search: If you use the "Only unresolved/unloaded" option, the search results returned are not correct.
This problem has been corrected.
217381
UI: Request that it be possible to zoom by using the mouse scroll wheel while a certain key is pressed.
This feature has been added. You can now zoom in/out by using the scroll wheel while holding down the Ctrl key.
219044
User encountered XML error when trying to report a problem using Help > Generate Support Request.
This problem has been corrected.
219303
Request that Rhapsody support the compiler in Microsoft Visual Studio 2008.
Support for Visual Studio 2008 has been added.
220131
Activity Diagrams: Request that Junction Connectors be renamed Merge Nodes in order to increase compliance with UML standard.
This change has been made.
222304
Rhapsody closes unexpectedly.
This problem has been corrected.
222311
Code Generation: When dependency with "friend" stereotype is used, generated code contains namespace prefix even though both classes are within the same namespace, resulting in compilation errors.
This problem has been corrected.
222396
Code Generation: With MicroC profile, you do not have to define a matching attribute for an output flowport, but in cases where an attribute was not defined, the generated code resulted in compilation errors.
This problem has been corrected.
222643
Automotive: Generated AUTOSAR xml file contains errors.
These problems have been corrected.
222969
Automotive: After importing AUTOSAR xml, the package ModelDeclarationGroup is not in the correct package.
This problem has been corrected.
222970
Automotive: When importing AUTOSAR xml, port not imported correctly.
This problem has been corrected.
222973
Automotive: After importing AUTOSAR xml, links to operation are incorrect.
This problem has been corrected.
222975
When user tried to open error log following import of AUTOSAR XML, Rhapsody became unresponsive.
This problem has been corrected.
223328
UI: The "Navigate to DOORS" option should be included in the Navigation submenu.
This change has been made.
223538
When using Japanese settings in Rhapsody, guillemets for stereotypes appear garbled.
This problem has been corrected.
223609
When you fill out a support request and then click Preview and Send, Rhapsody closes unexpectedly.
This problem has been corrected.
224054
Rhapsody closes unexpectedly when user tries to add DiffMerge results to model.
This problem has been corrected.
214999
Eclipse Integration: When using the Eclipse workflow integration, if a relative path is used as the directory for code generation, roundtripping does not work.
This problem has been corrected.
219847
Eclipse Integration: When using the Eclipse platform integration, if you add the SysML profile and open a SysML diagram, the Drawing toolbar contains only the UML elements, not the SysML elements.
This problem has been corrected.
35064
Import from Rose: Rhapsody does not import any of the information defined in Rose property sets.
This feature has been added - Rhapsody now imports certain information defined using Rose properties.
95523
Import from Rose: Importing of large Rose models takes an excessive amount of time.
Import time has been reduced substantially.
96055
Import from Rose: Rhapsody does not import user-defined properties from Rose.
This feature has been added.
109484
Import from Rose: Request that the import feature include the ability to merge the code base with the imported model.
This feature has been added.
109675
XMI: Error reported when user attempted XMI export of SysML model from Rhapsody, using UML 2.1.
This problem has been corrected.
109698
Simulink Integration: After importing Simulink model that uses custom types, code generated by Rhapsody results in compilation errors.
This problem has been corrected.
109783
Import from Rose: When interface realizations are imported from Rose, they are converted to generalizations in Rhapsody.
This problem has been corrected.
109792
Import from Rose: Role names show up sometimes in diagrams.
This problem has been corrected - role names are no longer displayed in diagrams.
109795
Import from Rose: Associations imported with illegal names.
This problem has been corrected.
220762
Import from Rose: When importing from Rose, realizations are converted to generalizations.
This problem has been corrected.
221533
Import from Rose: When importing from Rose, Rhapsody does not handle static arrays correctly, resulting in the generation of incorrect code.
This problem has been corrected.
223761
Import from Rose: Import process is very slow if Rose model makes extensive use of links between diagrams.
This problem has been corrected.
51560
Documentation: Request that the documentation explain what happens when you have timeouts that expire at the same time.
The documentation regarding timeouts has been improved.
87337
Documentation: Request that the User Guide provide a better explanation of the difference between a Termination State element and a Termination Connector element.
This information has been added.
93623
Documentation: Request that the Framework Reference include detailed information on OXF usage, including classes/methods available for use.
The newly combined Frameworks and Operating Systems Reference contains an entire chapter entitled "OXF Classes and Methods".
98586
Documentation: Framework Reference was replaced with a smaller document that is missing signification information.
This information is now included in the new document, "Frameworks and Operating Systems Reference".
101067
Documentation: The documentation for Rhapsody in C does not provide details for the OSAL class RiCHandleCloser, which might be needed in new RTOS adapters.
This information has been added.
102085
Documentation: In the RTOS Adaptor Guide, the RiCOSEventFlag Interface section contains a number of sentences where the term "reset" seems to be used erroneously instead of the term "signaled".
This problem has been corrected in the Frameworks and Operating Systems Reference, which has replaced the RTOS Adaptor Guide.
105875
Documentation: System Engineering Tutorial is out-of-date.
The Systems Engineering Tutorial has been updated.
109034
Documentation: It is not clear from the documentation what exactly Rhapsody does when you select the Code > Re Generate option.
The documentation for this option has been expanded to remove any ambiguity.
109265
Documentation: Request for detailed information regarding the Rhapsody in C framework.
This information can now be found in the new manual "Frameworks and Operating Systems Reference".
109308
Documentation: The documentation for the API method IRPModelElement.setPropertyValue contains inaccurate information with regard to the syntax to use.
The inaccurate documentation has been corrected.
109440
Documentation: In the help page entitled "Launching DiffMerge Inside Rhapsody", the section "Comparing an Archived Unit to the Current Version" states that the "Compare with..." dialog is displayed, allowing you to select the archived version you want to run the comparison against. However, when you use Rhapsody with Synergy, this dialog is not displayed.
The documentation has been updated to reflect the fact that Rhapsody displays different behavior in this situation when used in conjunction with Synergy.
110029
Documentation: The Rhapsody API documentation does not include any information regarding the method isReferenceUnit().
This information has been added to the Rhapsody API documentation.
110050
Documentation: IRPBlock has been deprecated but this is not reflected in the documentation of the Rhapsody API.
The API documentation now indicates that IRPBlock has been deprecated and IRPInstance should be used instead.
110052
Documentation: Request for additional information regarding the format of .hep files.
Additional information has been added for this topic.
110081
Documentation: The Systems Engineering tutorial seems to imply that requirements can be created in Gateway, and this is incorrect.
The problematic text has been corrected.
110448
Documentation: Request that the User Guide provide more details regarding the linking of objects.
This information has been added in a section titled Connecting Ports.
110470
Documentation: In Team Collaboration Guide, section titled Using Synergy with Rhapsody contains vague information.
The section on using Synergy with Rhapsody has been updated.
213128
Documentation: Request for more details regarding the individual checks that are carried out in the framework of "Check Model".
Additional details have been added to the "List of Rhapsody Checks" section in the User Guide.
213930
Documentation: In the RTOS Adapter Guide, the section RiCOSOXF Class specifies "long" as the type of the following constants RiCOSDefaultStackSize, RiCOSDefaultMessageQueueSize, and RiCOSDefaultThreadPriority, but this actually depends on the deployment environment.
This has been corrected in the Frameworks and Operating Systems Reference, which has replaced the RTOS Adapter Guide.
215848
Documentation: Request that the documentation include more information on the SPT profile.
A new section titled "Using the Schedulability, Performance, and Time (SPT) Profile" has been added to the Rhapsody User Guide.
216224
Documentation: In the Installation Guide, the section Running Different Editions of Rhapsody does not mention the -architect switch which is used to launch Rhapsody Architect.
This information has been added.
217029
Documentation: Documentation for reverse engineering has not been updated to reflect the changes made to the GUI.
The documentation has been updated to match the GUI.
219086
Documentation: The Installation Guide does not contain any information regarding the use of Windows 2003 as an application server.
A topic titled Windows 2003 Application Server has been added to the Installation Guide.
222065
Documentation: In the Team Collaboration Guide, the section on DiffMerge command-line options has to be updated.
This information has been updated.
223900
Documentation: The Installation Guide should note that Citrix users must move the rhapsody.ini file from the installation directory to the system's Windows directory.
This information has been added to the Installation Guide.
109096
ReporterPLUS: When using the ContainedElements feature, ReporterPLUS reported elements not shown on a diagram.
This problem has been corrected.
110396
ReporterPLUS: Request that it be possible to filter out unresolved operations when iterating over operations.
The introduction of a new model element attribute called isUnResolved now makes this possible.
219092
ReporterPLUS: Request that it be possible to change the default format for images generated by ReporterPLUS.
The image format used by ReporterPLUS can be changed using the Options dialog.
97214
Gateway: Gateway does not read DOORS modules if they contain an extra space at the end of the module name. A "conversion problem" error is reported.
This problem has been corrected.
102298
Gateway: When exporting elements to DOORS, the dialog box does not allow you to expand the top-level package and select individual sub-packages of requirements from the Rhapsody model.
This is now possible.
108221
Gateway: When using Gateway to export a Rhapsody model to DOORS, the export process uses the clipboard, and this prevents the user from using the clipboard for other actions while the data is being exported.
This problem has been corrected.
109566
Gateway: Launching Process dialog box remains on screen, must be closed manually.
This problem has been corrected.
210178
Gateway: Request that there be a synchronization mechanism that allows you to change a requirement in either Rhapsody or DOORS.
This feature has been added, and its use is documented in the Gateway documentation.
223759
Gateway: Request that the Source UML Model tree allow you to expand the top-level packages to select packages lower down in the hierarchy for export.
This is now possible.
223916
Gateway: Request that there be a synchronization mechanism that ensures that changes made to requirements in Rhapsody will be automatically reflected in DOORS.
This feature has been added, and its use is documented in the Gateway documentation.
224046
Gateway: Request that packages and requirements exported to Rhapsody not be renamed - currently, periods are replaced by underscores.
Rhapsody allows a label for each element, in addition to the element name. When requirements are brought into Rhapsody, the original name is preserved as the label.
89472
DoDAF: Request that the pop-up menu in System view include an option for adding an interface.
This feature has been added.
109132
DoDAF: On block definition diagrams, Rhapsody allows you to change an aggregation between blocks that have the System stereotype into a directed composition, but the UI does not allow you to draw a directed composition between such blocks using the appropriate tool on the Drawing toolbar.
This problem has been corrected.
110261
SysML Profile: When flow ports and attributes are typed using the Ampere and Kelvin units provided in the SIDefinitions package of the SysML profile, the generated code contains two operations with the same name.
This problem has been corrected.
210364
SysML Profile: When using non-atomic flowports, it is not possible to connect an output to multiple inputs.
The new port multicast feature now makes this possible.
220112
SysML Profile: In SysML, constraint parameters do not have a direction. The graphic editor and Features dialog should reflect this.
This has been corrected - the Direction field is grayed out in the Features dialog, and direction is not shown in the graphic editor.
93514
TestConductor: Request that it be possible to record performance data during execution.
This is possible using TestConductor's integration with Rational Test Real Time.
105973
TestConductor: Request that the TestConductor CLI provide "generate and make" options for: all CG configurations related to TestConfigurations, a specific test package, a specific test context, a specific test case.
These options are provided. See the TestConductor User Guide for details.
106691
TestConductor: Request that there be a way of controlling execution order when executing multiple TestCases.
Test execution order can be controlled using the properties TestConductor::Settings::TestCaseExecutionOrder, CG::Class::OperationsAutoArrange, and Browser::Settings::ShowOrder. See the documentation for details.
110223
TestConductor: Code generated for driver operations attempts access via pointer in cases where this is not possible.
This problem has been corrected.
110307
TestConductor: For flowcharts, text execution ignores the value of the property TestConductor::TestCase::ExecutionIdleTimeout. TestConductor times out after 60 seconds regardless of the value of this property.
This problem has been corrected - now, the property ExecutionIdleTimeout applies to Code, FlowChart, StateChart, and SequenceDiagram-based TestCases.
110357
TestConductor: The TestConductor User Guide is out-of-date.
The User Guide has been updated, and documentation has been added for the new features in this release.
222197
TestConductor: When building a component, error message "Cannot instantiate abstract class" is displayed.
This problem has been corrected.
224426
TestConductor: Incorrect code generated for Singleton object, resulting in compilation errors.
This problem has been corrected.
213310
Webify: Webify not working with VxWorks 6.5 RTP.
This problem has been corrected.