|
Application: Process Version: v3.2 Tool: All Records found: 9 Status: P: Pending, S: Suspended, C: Corrected, R: Not reproductible. |
| Tool | id | description | comment | date | status | forecast |
|---|---|---|---|---|---|---|
| BE | 4758 | The way to indicate invalid values for simulation parameters is confusing: the verification is done as the value is typed, but an invalid value simply appears red, which could easily be missed or misinterpreted. It would be better to have a much clearer indication that the current value is valid or invalid. | Done. A visual indicator is now present in each field, showing a green checkmark if the field is valid, and a red cross if it isn't. A tooltip on the indicator displays the reason why the value is invalid, as well as the actual value for the field, i.e the last one that was valid. | 2024-02-20 | C | v3.2 |
| BE | 4730 | The hover buttons allowing to create successors and flows from a symbol can appear under the symbol if the mouse button if closest to the symbol's bottom side. This is very unpractical for symbols such as events or getways that have their text under them: the buttons are masking the text, and clicking on the text to edit it can become very tricky. | Done. For symbols having their texts under them, the hover buttons can now appear above it or at its right or left side, but no more under it. | 2024-01-17 | C | v3.2 |
| BE | 4688 | The display of a big model in the editor window can end up being a bit long. When it is, nothing indicates that the editor is just busy. The cursor could be set to the 'wait' cursor, but this doesn't seem to work on Windows. Another way of displaying that something is going on should be introduced. | Done. Each time a model or diagram is displayed, a progress wheel is now displayed in the diagram zone and updated regularly until the model or diagram is completely displayed. | 2023-10-23 | C | v3.2 |
| BS | 4726 | In the dialog allowing to define simulation scenarios, the main diagram for a scenario indicates the diagram's index in addition to its name. It would be nice if the diagram index appeared also in the diagram browser to be able to identify it more easily. | Done. The diagram index has been integrated in the diagram browser in the model editor. The same thing was true for resource definition sets associated to scenarios: there is an index shown with the resources file name in the scenario definition dialog that wasn't appearing anywhere else. It is now displayed in the tooltip shown when hovering over the resource definition set in the project tree. | 2024-01-12 | C | v3.2 |
| BS | 4722 | When displaying the execution logs after a simulation, the time and cost values are displayed using a non-specified unit (it's actually microseconds for the time and cents for the cost). It would be better to display them in the time and cost units specified for the scenario, and to display these units to make them clear. | Done. The times and costs in the logs are now displayed in the units defined in the scenario, which are displayed on the line in the tree showing the scenario name. | 2024-01-05 | C | v3.2 |
| BS | 4698 | In CLI simulation, it would be nice to have the same execution options as in GUI simulation, notably allowing message flows in the same lane and sequence flows between participants. | Done. Options -m -s are available in CLI simulation. | 2023-11-20 | C | v3.2 |
| ME | 4728 | When comparing MSC diagrams, the labels for the differences can be difficult to understand or even not make any sense: activities are called "action symbols" and their actual type don't seem to be considered, sequence flows are called "operation calls", and so on... | Done. Concepts in the differences descriptions are now correctly named. The comparison now also takes into account the type for activities in the MSC diagrams: plain activity, start only, end only, call activity, and so on. If an activity changes its type between the compraed diagrams, a difference will be reported, which was not the case previously. | 2024-01-15 | C | v3.2 |
| PM | 4711 | The dynamic grouping and sorting of nodes in the project tree introduces a lot of complexity and seems of little use with the number of node types there is today. It would better to replace it with a static configurable grouping and sorting feature, allowing to group nodes by types, order types in a custom way and optionally sorting nodes by name in groups, but statically: the grouping and sorting is not kept automatically if nodes are added later. | Done. The option to group and/or sort elements in a project has been replaced by a static grouping and sorting, available via the 'Group/reorder items...' in the 'Edit' menu. It allows to group elements by type, customize the order of the groups, and optionally to sort the elements in the groups by their file name. The configuration is automatically stored in the preferences, so the options and the group order is kept across sessions. | 2023-12-13 | C | v3.2 |
| PM | 4700 | The application menu in the project manager contains only the entries to open the preferences and quit the application. It would be nice to also have an entry to check for new application versions and to manage PLM licenses, just as in Studio. | Done. Th entries "Check for new version" and "Manage PLM licenses" have been added to the application menu. | 2023-11-29 | C | v3.2 |