What's new in Rhapsody Model Manager 7.2

Learn more about what’s new and changed in the Rhapsody® Model Manager 7.2.

Milestone 13

Entry and exit actions visible in the Properties panel
The entry and exit action values for state chart states model element are now displayed in the Properties panel for the state, making a state model element logic easier to review and debug.
Activity state action content is visible
Action value of the action model element is now displayed in the Properties panel for the action which ensures consistent, accessible action details for all activity states.

Milestone 12

Collaborate on model elements
Rhapsody Model Manager web UI now supports enhanced collaboration on design artifacts through the Review Comments panel. You can perform the following actions:
  • Create new comments, reply, or mark them as resolved.
  • Mention any user who has access to the project area where the model element resides when creating or replying to comments.
  • Edit or delete comments as needed.
  • Filter comments by author for targeted review.
  • Initiate and manage discussions directly on model elements.
The following are the various states of comments:
  • New: A newly created comment.
  • Resolved: Marked as resolved and locked from further edits.
  • Reopened: A resolved comment that is reopened and is editable again.
  • Archived: Deleted comments are moved to the archive when no longer needed.
For more information, see Managing discussions on model elements.
Report generation with reportable Rest APIs

You can now filter architectural elements by their modified date in IBM Rhapsody Model Manager’s reportable REST APIs. Use Start Date and End Date fields to constrain results to a specific time window, making it easier to generate precise, change-focused reports. This helps isolate updates between milestones, audit periods, or deployment windows without manual post-processing.

Milestones 7 to 11

These milestones contain only quality improvements.

Milestone 6

Reportable REST API now includes the Rhapsody GUID of the model elements

Use the new guid field in the Rhapsody Model Manager reportable REST API to show the Rhapsody GUID of the model elements in reports. The query parameter of the field specifies the information to include in the API response.

Reportable REST API filtering capabilities

You can now filter architecture elements by tag names and tag values through Rhapsody Model Manager REST API, providing enhanced flexibility in generating reports that include only the desired architecture elements.

filterTagNames

Use the filterTagNames query parameter to include only architecture elements that contain specific tags by name in your report. To filter the architecture elements by multiple tags, use a comma-separated list of tag names. The filter applies OR logic, meaning that model elements are included in the report if they contain at least one of the specified tags.

For example, if you use 'filterTagNames=propertyA,propertyB', this returns architecture elements that contain either a tag 'propertyA' or 'propertyB'.

filterTagValues

Use the filterTagValues query parameter to include only architecture elements that contain specified tag with a matching string value. You can combine filterTagValues with 'filterTagNames', since 'filterTagNames' defines the ordered list of tags that you want to assert the tag value on) and each must match the same comma-delimited size.

For example, if you use filterTagNames=propertyA,propertyB and filterTagValues=valueX,valueY, this returns architecture elements that contain a tag called 'propertyA' with a string value 'valueX' or another tag called 'propertyB' with a string value 'valueY'.

filterTagDelimiter

Use an optional filterTagDelimiter query parameter to specify a custom delimiter string for tag names and values. This is useful if the tag values contain a comma, since it is the default delimiter.

For example, you can use a semicolon as the delimiter if you are looking for model elements with a tag named 'tagA' that has a value of 'X,Y' using: &filterTagDelimiter=;&filterTagNames=tagA&filterTagValues=X,Y

Milestone 4

Notification regarding configurations that are not published to the Rhapsody Model Manager TRS feed

You can now see a notification when one of your working configurations is not published to the Rhapsody Model Manager TRS feed. The configurations that are not published to the Rhapsody Model Manager TRS feed are unavailable for Rhapsody Model Manager reporting through Lifecycle Query Engine (LQE). Also, the other projects are unable to discover the incoming AM-AM links by using Link Index Provider (LDX).

Image displaying the notification message in the Rhapsody Model Manager web-UI:

Click show details link for detailed information about the configurations that are not published and the guidance for the administrator to publish the configuration to the TRS feed.

Image displaying the detailed message:

Milestone 3

This milestone contains only quality improvements.

Milestone 2

This milestone contains only quality improvements.

What's new in other IBM® Engineering Lifecycle Management applications