ModelCHECK: Required ability to use asterisks in ModelCHECK configuration files
- 2 replies
- 57 views
1. Describe the Problem
It would be helpful if there was a way to use asterisks in ModelCHECK's configuration files, e.g. in the condition.mcc file, to call a special check profile if the model contains one or more parameters that begin with "USR_", for example. If "MODE_UPDATE" is set to "Yes" in config_init.mc and the "EXTRA_PARAMS" option in the *.mch file is also set to "Yes", all parameters that are not present in the template defined under "PRT_TEMPLATE" in the *.mcs file will be deleted. This means that all parameters added by the user will be deleted. This is dangerous because not all parameters are used by a relation and these are therefore deleted by ModelCHECK. By using an asterisk in the condition.mcc file, it could be detected whether there are multiple user-defined parameters that begin with "USR_", for example. This condition in the condition.mcc file could look like this:
IF (USR_*) config=(check/mat.mch)(check/usr.mch)(start/mat_mm.mcs)(start/usr_mm.mcs)(constant/mm.mcn)(status/status.mcq) (name/Userparameters)
Or like this:
IF (CONF_*) config=(check/mat.mch)(check/kon.mch)(start/mat_mm.mcs)(start/kon_mm.mcs)(constant/mm.mcn)(status/status.mcq) (name/Configuratorparameters)
In this case, you could set "EXTRA_PARAMS" in the *.mch file to "no" to prevent ModelCHECK from deleting these parameters.
Would it be possible for PTC to create a new condition called PRT_PARAM_WANTED or ASM_PARAM_WANTED in the *.mcs file to prevent the deletion of parameters beginning with, for example, "USR_"?
This could look something like this: PRT_PARAM_WANTED USR_*
Therefore, it should also be possible to use asterisks in the condition. This would also allow parameters beginning with "USR_" to be deleted. This could look something like this: PRT_PARAM_UNWANTED USR_*

2. Are you using a workaround?
There's no workaround. You can only allow the deletion of all parameters that aren't included in the template. However, this will also delete all custom parameters. Or you can prohibit the deletion of all parameters. It's not possible to specifically control the deletion of parameters.
3. What is the use case for your organization?
If it were possible to use asterisks, one could, for example, delete all parameters in legacy data that don't begin with a specific text, such as "USR_." This would improve data quality and allow legacy data to be brought up to a new company standard.
4. What impact does this problem currently have on your organization?
Old parameters currently have to remain in the models because there is no way to delete them specifically and without huge effort.
