Release date: 3rd December 2013
1.1. Process Portal Report
1.2. Resource assignment to Activities
1.3. New element in Organization Structure diagram
1.4. Quick assigned resources display on BPMN Process diagram
1.5. Easier navigation between diagrams
1.6. Business Model Creation Wizard
1.7. Smart packages
1.9. Gradual upgrade of Teamwork Server clients
Now you can generate web reports and publish business process information in HTML for easier business process analysis.
You can now assign as Activity resource these elements:
- Organization Unit
- Information System
You can now set the Assigned Resources property to Activity elements not only in the Specification window but also by simply adding the Activity element onto the Lane representing the particular resource.
Validation rules ensure the consistency between Activity recourses and lanes.
An Information System element is added to the Organization Structure diagram.
You can now display resources assigned to the Activities on a BPMN Process diagram.
You can now easily navigate between diagrams using a new toolbar on the diagram pane. The toolbar offers navigation action to
- Previous diagram
- Next diagram
BPMN diagrams in addition allows for navigating to
- Upper level diagram
- Related process diagrams
In a diagram, move the pointer over the bottom-left corner of the diagram pane to see the new toolbar (see the preceding figure).
In dependency matrices, relation maps, and generic tables, find the new toolbar on the toolbars area.
Use the Business Model Creation Wizard to jump-start creation of your business model. On a new project creation the wizard helps you to define main business elements such as:
- Business concepts
- Organization structure elements
- Main Processes
The wizard creates the project with business model elements and diagrams.
Need to see all non-verified requirements of the particular version in a single view? Have all frequently used elements within the same package? Get a list of all the interfaces used in the model? Pick up elements from different places of the model, into one package, for easier scope definition when generating a report? Use smart packages!
The smart packages do not hold anything, but display elements stored elsewhere in the model and continually update to display elements that meet the search criteria specified by a query. The smart packages save your time when you would otherwise need to rebuild a search from scratch. They also help to find, track, and organize your model elements. The smart packages are treated like regular packages and can be used in Dependency Matrices, both Find and Quick Find dialogs, element Selection dialog, and other places in the application.
Creating a smart package is as simple as creating a regular package.
Once the smart package is created, you are ready to specify the query for gathering its contents. For specifying queries, use the Query dialog, which reflects numerous enhancements of the powerful expression evaluation engine. Let’s say we need to have all requirements from the package HSUV Requirements with tag value version=5.
Tip! If you perform a search after specifying criteria the Find dialog, and only then realize it would be handy to have a smart package that uses those criteria, simply save the search results as query of a new smart package.
From now on every new requirement in the package HSUV Requirements will be automatically included into the smart package if tagged with version=5.
The smart package can be selected as the row or column scope in a dependency matrix. The scope will update after any update of the smart package contents.
You can also select the smart package as a search scope in both Find and Quick Find dialogs, element Selection dialog, and other places in the application.
Save time by marking any element that you regularly use in your model and need to access quickly as a Favorite.
Using Favorites also speeds up the scope selection in:
- Quick Find dialog
- Element Selection dialog
- Autocompletion lists
The new version of the client application can connect to an earlier* version of Teamwork Server. This feature enables the gradual upgrade of Teamwork Server, which will make the upgrade process smoother in larger organizations.
By using the gradual approach for upgrading Teamwork Server, different teams from the organization can migrate their server projects independently of each other and still work with the same Teamwork Server. A team that has switched to the new version of the client application, and needs to work with server projects, no longer has to wait while other teams complete their work with the earlier version of the client application in order to upgrade the server. Upgrading Teamwork Server is not required to access server projects with the upgraded version of the client application. The upgrade of Teamwork Server can now be postponed until all client applications are upgraded.
An additional benefit of the feature is the ability to try out the new version of the client application with real-life server projects without upgrading the server.
*Starting with Teamwork Server 17.0.4 (update the license key of the server to enable connections from specific versions of client applications).
- When drawing new paths, MagicDraw automatically chooses the optimal route to avoid crossing of shapes.
- When drawing a new path, the path end is connected to the shape center. Note this is valid if the shape is small enough.
- Layout inside Pools has been enhanced and now symbols are layed out based on the Lanes to which they belong.
- Labels no longer overlap after applying the automatic layout on the diagram.
- The shape no longer changes position after selecting to display related elements.
- When inserting a shape into a path in an Business Process or Collaboration diagram, a space is made automatically for the new shape and shapes no longer overlap each other.
- Cameo Business Modeler introduces the smart shape sizing when drawing new shapes from other shapes via paths. The size of the newly created shape is kept the same as the size of the shape from which the path is drawn.
The Represent Properties dialog is a helping hand when creating pools.
When you create a pool from the Diagram pallet in the diagram of the particular classifier, the Represent Resources dialog appears. This dialog gives you all available properties related to that particular classifier.
- Designing of tables and trees in the User Interface Modeling diagram is now more flexible. Reorder columns or nodes and leaves simply by changing their numbers.
- Symbols that overlap with a Pool on the Business Process or Collaboration diagrams are now highlighted as invalid.
- Diagrams look cleaner now - grid lines no longer display on diagrams by default (snapping to grid lines will still be on).
You can now easily identify different relation criteria represented on a relation map. For this capability, the relation map has been enriched with the following enhancements:
- Colors. Select the colors when specifying the relation criteria you need to see on the relation map.
- Legend. Identify relation criteria by colors. The legend will be included in a report, image, or printed copy of the relation map.
- ToolTips. Move the pointer over an arrow to see the relation criteria it represents.
The ability to represent colored relation criteria on relation maps will help you when performing a traceability, impact, or coverage analysis. As the following figure shows, you can now
- Use the same or similar colors to represent different relation criteria between the elements in the same phase of a project development.
- Use different colors to represent relation criteria between the elements that belong to separate phases of the project development.
- You can now sort both rows and columns either in ascending or descending order (see the following figure) or create your own order by shifting selected items (either grouped or non-grouped) from one place to another. The sort order persists after changing the row or column owner's display mode.
To shift the selected items, use either appropriate commands from the row or column shortcut menu (see the following figure) or key combinations, such as Ctrl+Arrow.
- Now you need fewer clicks to create or remove a relationship.
You can now use the open API to
- Create custom types of the dependency matrix. Customize a dependency matrix as follows:
- Configure the toolbar (1), shortcut menus of the row or column element (2), cell (3), and Criteria area (4).
- Assign shortcut keys for commands.
- Define custom dependencies that can be created in the matrix (5).
- Specify the appearance of the matrix, that is, change the default colors of the cell and both row and column headers, assign custom icons to represent dependencies, etc. (6).
- Define cases when specific dependencies should be updated without rebuilding the whole matrix.
- Export the data of a dependency matrix to any format (7).
No Magic, Inc. provides instructions on how to use the open API and a sample project, which can be found in
- You can now start a quick search by clicking a new toolbar button on any open tab (Containment, Diagrams, etc.) in the Model Browser.
Note: You can also open the Quick Find dialog from the main menu, as in earlier versions.
Select Edit > Quick Find.
- You can now see the full length of a long text that is cut off by the border of a list or a tree area. Move the pointer over a cut-off text to see the full length.
- A list of suggested elements can now be reduced by clicking a specific button. As a result, all irrelevant elements will be excluded from the list.
- You can now lock, unlock, or discard changes of multiple elements just in one click. The appropriate commands have been added to the shortcut menu of multiple elements selected on a diagram.
- The shortcut menu of an element selected in the Model Browser has been refined as follows:
- The Create Symbol command has been excluded.
- The Generate Code Framework and Check Syntax commands have been moved to the submenu of the Tools command.
The export to BPMN2 and export/import to XPDL file formats have been enhanced for these elements:
- Resource Role
Cameo Business Modeler now automatically checks for updates according to the Check for Updates option and displays a notification if updates are found.
The Resource Role and Participant metaclass was changed to Class in the UML profile for BPMN (BPMN2 Profile.mdzip).
Be informed that starting with the next version, Cameo Business Modeler will stop supporting both Mac OS X Leopard and Mac OS X Snow Leopard.
Also, Cameo Business Modeler will no longer be compatible with Java SE 6, thought Java SE 6 based code engineering will still be supported.
To open the list of publicly available or your own issues those have been included into version 17.0.5 FR, click here.
Note: You will be required to login. Use the same username and password as for www.nomagic.com.
You may find many more possible solutions for known issues at No Magic Community Forum that is regularly updated with new topics.