I've collaborated with the ModelCHECK team to try to answer your questions. Please let me know if you have any follow up questions.
Is it possible to leverage ModelCheck, where the ModelCheck (MC) parameters are added to the Pro/E model automatically upon running MC, and not add the MC attributes to the EPMDocument (CAD Document) object type in Windchill? (Without getting check in warnings)
If the user intention is to skip the validation when performing checkin, then there are two ways of doing it, listed below:
1. Set the following preferences in Windchill to perform ModelCHECK validation at check in. If the requirement is to not to perform the check the user needs to set the ModelCHECK Validation (Boolean) to a value NO. These Windchill preferences are disabled and locked at the site level by default. Clearing the value of ModelCHECK Configuration will skip validation of the configuration files.
2. If you want to checkin the file without getting check in warnings, I believe you can set the option for ModelCHECK Number of Errors (integer) to a higher number (such as 69 or 70) so that even if the errors are reported WC Gatekeeper will allow the model to check in without any issues.
I am curious to see if it’s possible to implement ModelCheck without adding the MC attributes to the CAD Document type in Windchill AND users do not get check in warnings about the designated MC parameters in the Pro/E model.
I'm not sure I fully understand why you could want to do this. This is the basic requirement to map/configure ModelCHECK with Windchill, which I guess you are trying to get around. Therefore it makes sense to map/implement these basic attributes such as “MC_ERRORS, MC_MODE, MODEL_CHECK, MC_CONFIG” etc.
Is it even possible to undesignate those attributes?
From Windchill no and from Pro/ENGINEER no. The reason is because they are locked by ModelCHECK and are READ only.
Or how about preventing MC from adding those attributes to the CAD Document? (Not preferred for obvious reasons - just curious)
If this is the case, you can simply upload the file without creating IBA’s for validation. Also as additional information, beginning in PDMLink 9.0 M080 MC_MODE will be available to ModelCHECK Gatekeeper as an optional validation parameter.
On a side note - the config option, allow_create_pdm_params does not effect this undesignate ability for those parameters - nor do they permit the deletion of those attributes from the Pro/E model.
This config option is meant for other PDM created parameters. However, ModelCHECK related parameters are created by ModelCHECK and are locked by ModelCHECK because these are the parameters that the users should never have access to. From a Pro/ENGINEER point of view, if the user would like to avoid them then they need to turn off the parameter creation in ModelCHECK. One can do this by setting ADD_ERR_PARM, ADD_CONFIG_PARM, ADD_DATE_PARM and ADD_MODE_PARM to N in all ModelCHECK run modes, in the config_init.mc file.
Can I ask what version ofPro/ENGINEER are you running?
You mentioned that models are marked as out of date when the ModelCHECK parameters are updated, even when their values do not change. From my discussion with a few people at PTC this was a very old issue, which we all believe was fixed quite some time back. I'll continue to search to see if I can provide you with an exact version and build number.
Thingworx Navigate content has a new home! Click here to access the new Thingworx Navigate forum!
Check out the Windchill Tips Board! We're talking about
Whirlpool's use of digital twin, augmented reality, and data-driven design!
The NAVIGATE WORKING GROUP is here! Come innovate with PTC!
The NAVIGATE WORKING GROUP is here! Come innovate with PTC!Sign up for a Working Group