Need help? Send notifications of a problem, suggest improvements for our modeling tools, or ask about new features.
Anchor
offline
offline
Report an issue when the program is unresponsive
If you encounter an issue or the modeling tool becomes unresponsive, a separately executable tool is provided for analyzing the status of the process to aid in bug submission. In these situations, manually start the submit_issue.exe file (located in the <modeling tool installation directory>\bin folder). After you start submit_issue.exe, the Report an Issue dialog opens.
In this dialog, you can easily dump threads or memory heap into files and provide those files when reporting an issue to the support team.
Dump Threads to Log File - threads will be dumped to a Log file.
Dump Memory Heap to File - memory heap will be dumped to a new .hprof file.
Reporting Issues Through Email
The e-mail address for registered users to access our customer support system is support@nomagic.com.
The system allows you to include keywords in the email’s subject line. These keywords will enable us to route the issue to the proper support organization more quickly and resolve the issue in a more timely manner. They also allow the definition of many fields for the newly created issue (reporter, project, priority, affected components, affected version).
Note
title
Support Issues
Support Issues can only be reported or commented on from the email address registered in your www.nomagic.com account.
The parameters are listed below:
#PROJECT
#SECURITY_LEVEL
Tip
title
Format of the Email
For example, if you have a question about documentation in UPDM, you might submit the following email:
This email sent from the registered user will create a support issue in the UPDM project. The Issue’s component will be Documentation and Requirements Management and its severity will be low.
Note
title
Parameters
Parameters should be listed in the email subject line with a single space between them.
No commas should be used between parameters.
No spaces should be used in the body of the parameter.
If a parameter value contains spaces, you must replace each space with two underscore characters. For instance, #COMPONENT=Test__Component associates the issue to Test Component. If you specify an invalid component or none at all, the issue is associated to No Component by default.
Emailing support requests can be faster compared to the web interface http://knowledgebase.nomagic.com; however, when reporting issues through email, additional important information might be lost. This information loss can be mitigated by including parameters from the list above.
If an email has email addresses in either the CC: or the BCC: fields, they will be added to the support issue as External Watchers. All watchers receive email notifications about any activity on the issue.
Note
title
Support Issues
Support issues that are marked private are not viewable within the support system, even if you are listed as an external watcher. Non-registered users also will be unable to see issues within the support system.
Commenting on a Support Issue
To comment on an existing support issue, please reply to the notification email. The body of the email will become your comment on the issue. If you send attachments with your email, they will become attachments on the issue.
Note
title
Issue ID
It is important that the issue id (e.g. [MDUMLCS-2058]) exists in the subject line.
Warning
title
Not a registered user
If a commenter is not registered in www.nomagic.com, his or her comment is not recorded in the support issue.
View and Submit Internal Errors
Internal errors are displayed as notifications by default. The internal error does not necessarily mean damage to your data, but can be a reason for unexpected tool behavior. We highly recommend submitting internal errors to No Magic for further investigation. We strongly recommend attaching the log file. An internal error message appears at the bottom of the modeling tool.
Example of Internal Error message in MagicDraw modeling tool
To view internal errors
To view internal errors you must open the Internal Errors dialog, using one of the two methods outlined below:
Click the Viewinternal errors button in the Notification Window.
Click the notification icon on the status bar.
To submit an error
Open the Internal Errors dialog.
Click the Export To File button. Image Added
Specify the name and location of the error log file and click Export.
