Article - CS325902
How to handle error with deprecated config.pro option regen_failure_handling (default) no_resolve_mode with Creo 7.0 Customization APIs
Modified: 04-Jun-2020
Applies To
- Creo Parametric 7.0
- All Creo Parametric Customization APIs
Description
- How to avoid the warning message Attempted Use of Deprecated Config Option that pops-up while using deprecated configuration option regen_failure_handling with Creo Customization APIs
- Creo Parametric handles Failure of Model regeneration in two modes
- no_resolve_mode: This is the Default mode. In this mode, any regeneration failures will not force user to enter Resolve mode.
- resolve_mode: In case of regneration failure, enters resolve mode. Where, user has to resolve the failures by using either redefine (edit definition), suppress or delete to continue model regeneration.
- Except Creo Parametric TOOLKIT, all other Creo Customization APIs like OTK C++, OTK JAVA (both FREE & Licensed versions), VB API & WebLink does not support Regeneration handling in no_resolve_mode.
- For example, when regen_failure_handling is set to no_resolve_mode, calling methods like Solid::Regenerate() or Solid::ExecuteFeatureOps() will fail with exception pfcExceptions.XToolkitBadContext (TOOLKIT Equivalent error is PRO_TK_BAD_CONTEXT).
- So, Creo OTK C++, OTK JAVA (both FREE & Licensed versions), VB API & WebLink Application developers are forced to set regen_failure_handling value to resolve_mode to be able to succdessfully use the above mentioned APIs.
- Since Creo Parametric 7.0 release, the configuration option regen_failure_handling has been deprecated and is NOT advised to be used.
- While using regen_failure_handling config option, user is presented with the warning message To use a deprecated config option, you will need to supply an authorization code with allow_deprecated_config. Please see article CS260154 for more information.
This is a printer-friendly version of Article 325902 and may be out of date. For the latest version click CS325902