在 CATIA 3DEXPERIENCE 发布期间隐含消息
在使用 Windchill Visualization Services (WVS) 发布 CATIA 3DEXPERIENCE 设计数据时，警告消息有时会在弹出窗口中显示。这些消息可能导致 CATIA 3DEXPERIENCE 会话挂起。下图为此类警告消息的示例。
要避免此问题，您可设置一个环境变量，使 WVS CAD 工作器代理扫描 XML 文件的特定弹出窗口标题和消息，以在 CATIA 3DEXPERIENCE 发布期间将其隐含。指定要隐含的弹出窗口时，也可以指定基于不同消息类型执行何种操作。例如，“警告”- 继续发布作业，“错误”- 立即中止发布作业。
 | 在发布过程中隐含弹出窗口可能导致所发布数据集的更新不完整或不正确。但是，如果数据集不完整，这可能是一个可取的解决办法。 |
要设置 CATIA 3DEXPERIENCE 作业发布期间 WVS 弹出窗口的隐含：
1. 如果 CAD 工作器正在运行，请将其停止。
3. 在 suppress.xml 文件的适当位置记录导致失败的警告窗口的标题和消息文本以及在未来作业发布期间显示此窗口时所需采取的操作 (“警告”继续作业或“错误”立即中止)。
例如，您可以使用以下定义：
<popup_definition title=”Hole*” message=”Geometry*” action=”Warning”>/
| | 如前一示例所示，可使用通配符 (*) 来简化定义。 |
4. 将 suppress.xml 文件保存到系统中的位置。
5. 创建名称为 "PTC_WGM_CATIAV6_POPUP_SUPPRESS_DEF_FILE" 的系统环境变量并将其值设置为 suppress.xml 文件的路径。
6. 重新启动文件同步 CAD 工作器管理应用程序并重新提交发布作业以测试之前所记录弹出窗口的隐含情况。
| | 如果 PTC_WGM_CATIAV6_POPUP_SUPPRESS_DEF_FILE 环境变量的值为初始定义或更改，则必须重新启动运行工作器的工作器 Daemon。或者，如果工作器是作为服务运行，则应从服务控制台重新启动服务。 |
发布作业可能成功，也可能发生如 WVS 作业监视器 (更高版本的 CAD 工作器) 窗口记录面板中所示的其他失败。
7. 如果发生其他失败，则重复此步骤直到作业成功完成而不被弹出消息挂起。
包含指示的 supress.xml 文件示例
<?xml version="1.0" encoding="UTF-8"?>
<!--
INSTRUCTIONS:
- in worker mode, during job processing, the adapter suppresses CATIA popups defined
in the <popup_definition> tags and performs an action specified in the "action"
attribute
- action attribute can only have one of the following case-sensitive values:
"warning" - Log warning, continue job
"error" - Log error, exit CNEXT.exe, job fails without delay
- for a window to be suppressed, its title has to match the pattern specified in the
"title" attribute (case-sensitive) and its message has to match the pattern specified
in the "message" attribute (case-sensitive)
- using a wildcard (*) is supported in the "title" and "message" definitions where <*>
matches any (zero or more) characters, for example:
string "ABC abc" matched with:
pattern: "*" -> match
pattern: "ABC*" -> match
pattern: "*A*" -> match
pattern: "*bc" -> match
pattern: "a*B" -> no match
- examples
<popup_definition title="*Err*" message="*twisted*" action="Warning"/> causes suppression of all popups having "Err"
in the title and "twisted" in message body
<popup_definition title="*" message="*" action="Warning" /> causes suppression of all popups
- in cases where there are intersecting "error" and "warning" definitions and the popup
matches both of them, the "error" definition applies, regardless of the order listed
in the XML,(error definitions are processed first):
<popup_definition> title="*" message="*" action="Warning"/>
<popup_definition title="AB*" message="TEST*" action="Error"/>
Error def is used if popup matches
-->
<popups_to_handle>
<popup_definition title="*diameter was changed*" message="*need update geometry*" action="error"/>
<popup_definition title="*Admin*" message="*Reque*" action="error"/>
<popup_definition title="*" message="*twisted*" action="error"/>
<popup_definition title="*" message="*" action="error"/>
</popups_to_handle>
<!--
INSTRUCTIONS:
- in worker mode, during job processing, the adapter suppresses CATIA popups defined
in the <popup_definition> tags and performs an action specified in the "action"
attribute
- action attribute can only have one of the following case-sensitive values:
"warning" - Log warning, continue job
"error" - Log error, exit CNEXT.exe, job fails without delay
- for a window to be suppressed, its title has to match the pattern specified in the
"title" attribute (case-sensitive) and its message has to match the pattern specified
in the "message" attribute (case-sensitive)
- using a wildcard (*) is supported in the "title" and "message" definitions where <*>
matches any (zero or more) characters, for example:
string "ABC abc" matched with:
pattern: "*" -> match
pattern: "ABC*" -> match
pattern: "*A*" -> match
pattern: "*bc" -> match
pattern: "a*B" -> no match
- examples
<popup_definition title="*Err*" message="*twisted*" action="Warning"/> causes suppression of all popups having "Err"
in the title and "twisted" in message body
<popup_definition title="*" message="*" action="Warning" /> causes suppression of all popups
- in cases where there are intersecting "error" and "warning" definitions and the popup
matches both of them, the "error" definition applies, regardless of the order listed
in the XML,(error definitions are processed first):
<popup_definition> title="*" message="*" action="Warning"/>
<popup_definition title="AB*" message="TEST*" action="Error"/>
Error def is used if popup matches
-->
<popups_to_handle>
<popup_definition title="*diameter was changed*" message="*need update geometry*" action="error"/>
<popup_definition title="*Admin*" message="*Reque*" action="error"/>
<popup_definition title="*" message="*twisted*" action="error"/>
<popup_definition title="*" message="*" action="error"/>
</popups_to_handle>