ModelCheck - Optional Parameters - If Parameter Exists Then Check

[lhoogeveen]

Please add support for optional parameters within ModelCheck:

• Example: we have parameters that aren't always required but if they exist in the models, then we want them designated to Windchill to be searchable, be a string, etc.
• Optional parameters should be listed in the start.mcs files or in external list file.
• Support for wildcards in optional parameter names - we have parameters like CH_MFG_1, CH_MFG_2, etc. where having ? (single) and * (multi) character wildcards would be helpful rather than having to list all of them. 

[BenLoosli]

If you have an optional parameter, how does the system know that if it is missing that this file is still good because it did not require the parameter.

Put all parameters to be checked in an external file is a good idea. Format the file with fields for parameter name, required/option, designated.

Too many variations with wildcards for something like a checking program. What if you have your CH_MFG parameters require a number but someone puts a letter. With wild cards it would pass. If there is an external file for all parameters, list them all and let the system do its checking by parsing the list. This would also flag parameters that are not on your list as possible errors or at least warnings.

[lhoogeveen]

@BenLoosli For some of our Creo models, we have a list of 100+ possible parameters that maybe be used in any combination in the models. Conveniently, they pretty much all start with CH_MFG or something similar. Currently, there's no way to check to make sure these optional parameters are designated to Windchill and thus searching is difficult in Windchill.

Maybe I should have clarified that having the option of wildcards as a 'nice to have' feature as I'd be fine with a list of optional parameters. If users type a wrong parameter that isn't setup in Windchill, designating does nothing. PTC could implement single character wildcards for letters or numbers. Your company doesn't have to use wildcards but some companies may like using them.

I don't believe PARAM_CHECK is currently capable of having some parameters as errors and some as warnings. It's all errors or all warnings. This is really inflexible and doesn't fit the use case above.

[DomenicLaritz]

I'm not sure if this is the solution for your requirement, but we use the condition.mcc file to perform parameter dependent checks - for example:

IF (PARAMETERNAME) config=...

This way it is possible to check that if a parameter with a certain name exists, whether it is also designated.

[lhoogeveen]

@DomenicLaritz I don't believe that would work. The way I understand the condition.mcc file is that the first condition that is satisfied is the only ModelCheck setup that will run. This works great for IF (SHEETMETAL) config=(check/sheetmetal.mch)(start/sheetmetal.mcs)... then a specific list of sheetmetal parameters would be required. Not a flexible list of optional parameters that need to follow a specific format if they exist. Maybe I'm missing something?