Resolving To Do List Messages - Intergraph Smart 3D - Troubleshooting

Intergraph Smart 3D Troubleshooting Reference

Language
English
Product
Intergraph Smart 3D
Subproduct
Troubleshooting
Search by Category
Troubleshooting
Smart 3D Version
11 (2016)

Resolving To Do List messages requires work on both the project administration side and the software user (or client) side.

On the administrative side:

  1. Decide on a goal, by discipline, for the number of acceptable To Do List messages.

  2. Monitor To Do List messages. This can be done easily by running the summary To Do List message report weekly, or daily.

  3. Look for To Do List messages that are not caused by users but are more administrative related. Then, fix them or have them fixed by the person responsible of this area, for example:

    1. Unregistered or missing custom DLLs - These can include naming rules or Hanger and support Assembly Information Rules.

    2. Missing custom files - These can include drawing templates, labels, or reports. This may be caused by not having the custom data correctly delivered and registered. The issue can be local to the user machine or in the SharedContent shared folder.

  4. Be sure that some operations, such as synchronized models, are processed in each location in a global workshare configuration, to reduce the number of "out-of-date" To Do List messages.

  5. Be sure that the number of database integrity problems is minimal as a large number can prevent solving some To Do List messages.

  6. Be sure that tools, such as the Tools > Verify Consistency command in the Catalog task, are run and that problems are fixed because this can be the cause of many To Do List messages, especially in the Piping task.

In the summary To Do List message report, some To Do List messages associated with interference detection may show up. These To Do List messages are caused when a user does not have write access to interferences when either the related business objects are deleted or some of their properties have changed. The interference name is often computed using name of the two related business objects. The administrator with full access can update the To Do List messages and they are resolved; however, this is not necessary, as the interference detection server automatically deletes the unnecessary interferences or triggers the naming rule. Many To Do List messages are associated with interferences because the interference detection server was stopped. These To Do List messages will be solved when the interference detection is re-started and then re-processes these objects.

The standard To Do List message report includes the monikers of the associated business objects in the hidden column B. The Excel filter capability and the delivered custom command "SP3DFindObjectByReport.FindObjects" can be used. The command uses the Excel report as input. The command opens the Excel report and you can select To Do List messages. The software places the associated business objects in the select set, indicated by a highlight, so the object property can be found. This procedure can be used when trying to find information about specific To Do List messages without knowing what or where the objects are.

On the user side:

Always have the To Do List dialog box open while modeling so that you know when new To Do List messages are created or deleted.

  1. Open your session file. This could be based on the assigned areas, systems, permission groups, and so forth.

  2. Open the To Do List. Show only the object that you have write permission for.

  3. Update the out-of-date To Do List messages. The software can do this "blindly" in bulk or one by one.

    If you choose to do it in bulk, sort the messages by State and select all the "Out-of-Date" items. You can then click the update using All in the locate filter.

    If you choose to process the To Do List messages one by one, you probably want to check the results. In this case, select the row, then fit (display), adjust the display (zoom, rotate, and so forth), and update the To Do List message. Remember, you can always undo the change.

  4. "Update" the warning and error To Do List messages. Some To Do List messages may have been caused by external causes that have been corrected and updating the To Do List message may just solve it. This does not take too much time and may actually save time. An example of an external cause could be:

    • Missing custom DLLs or files,

    • Unregistered DLLs,

    • Specifications

    • Database integrity problems,

    • Software problems.

  5. Ignore the To Do List messages associated with interferences. Report to the administrator.

  6. Report to the administrative person those To Do List messages that seem to be caused by administrative problems such as missing DLLs.

  7. For each remaining problem, do the following:

    1. Select the row in the To Do List. It will put the associated business object in the select set. Use All in the locate filter.

    2. Fit and arrange the views.

    3. Press F1 or look in the Troubleshooting Reference Guide for information about what may have caused the problem and how to fix it (recovery).

    4. When you determine the object, move to the task associated with this object. This is important because the modify command will automatically start and only the modify command in the native task will have all the functionality.

    5. Fix the problem. Sometimes the problem cannot be fixed because of external causes. For example, in piping a "No Part Found" message might mean that either the piping specification is incomplete or that the user may have use a wrong specification or one with incorrect properties, such as NPD, temperature/pressure, and so forth. When a problem cannot be solved, contact the support organization.

  8. Change the option to see all the To Do List messages, including the ones for which you do not have write permission. The fact that you do not have write permission can occur because the object is not in working status, such as being "in review," or that the object is in a permission group to which you do not have write access. Verify that the item is correct. You might want to change the objects that are "in review" to "Working" and update the To Do List message.

The error log can be turned on. Level 2 is adequate. The error log shows information to help resolve the To Do List message. Also, the support group may request the log when you contact them.