Skip to main content
M
mschulze14-Alexandrite
14-Alexandrite
October 24, 2025
Solved

MC Gatekeeper: Prevent checkin if attribute is changed in the workspace after MC verification

  • October 24, 2025
  • 4 replies
  • 671 views

Version: Windchill 12.1

 

Use Case: I am looking for a solution to prevent the check in of ModelCheck (MC) validated data having MC_ERRORS = 0 if attributes are modified e.g. in the workspace after MC was executed.


Description:

Here is an example:
1) configure MC Gate Keeper and do not allow data to be checked if MC_ERROR > 0
2) We've defined a simple MC configured to run on each save. So we are sure, that MC was run when last modified.
3) MC e.g. evaluates certain attribute values and will mark it as error, if validation fails.

 

Now the user does the following:
1) Saves a CAD file with ATTRIBUTE = "X" (this is a valid for MC) => ATTRIBUTE = "X" and MC_ERROR = 0
2) User changes ATTRIBUTE = "X" to "Y" in the Workspace ("Y" would be an invalid values for MC) => ATTRIBUTE = "Y" and MC_ERROR = 0 (remains unchanged)
3) User checks in the cad file and the gatekeeper does not prevent the check in as MC_ERROR still equals 0 !

How can this be prevented without programming a trigger?

 

Best answer by mschulze

Well since there seems to be not OOTB working solution, I created enhancement request.
If you like it please vote for:
Extend WT ModelCheck Gatekeeper to prevent modifications in the workspace

 

4 replies

M
mmeadows-316-Pearl
16-Pearl
October 24, 2025

I haven't tried this in many years.  Last time I set up gatekeeper, we defined visibility of the ModelCheck attributes in Windchill as Read Only.  That way they could only be driven from Creo during upload.

Create New = Read Only

Edit = Read Only

EPM Upload = Read/Write

mmeadows3_1-1761332579921.png

 

If you really need these attributes mapped into Windchill, I would suggest setting them up so they can't be modified from the Windchill side.

 

M
mschulze14-AlexandriteAuthor
14-Alexandrite
October 27, 2025

Thank you for the Feedback, yes that's what I also thought about, was a workaround. 
I opened this question mostly to check if I have overseen some better solution. 
If there is no better solution on this, I'll probably create an enhancement request

joe_morton
18-Opal
joe_morton18-Opal
18-Opal
October 24, 2025

I haven't done this myself, but see: https://support.ptc.com/help/creo/creo_pma/r12/usascii//index.html#page/model_analysis/modelcheck/Configuring_ModelCHECK_for_Gatekeeper.html#

 

Are you using this?: 

ADD_VERIFIED_PARM—Creates the MC_VERIFIED parameter that verifies if the model has changed since the last Creo ModelCHECK run.

 

I would think that if the file was modified after MC was run, the MC_VERIFIED parameter would change to prevent check in.

M
mschulze14-AlexandriteAuthor
14-Alexandrite
October 27, 2025

Well yes, that how it is configured. But the parameter will not change when the attributes are changed in the Workspace instead of Creo p.

    M
    22-Sapphire I
    MikeLockwood22-Sapphire I
    22-Sapphire I
    October 25, 2025

    For many years, I have thought that preventing checkin is absolutely not the way to approach this.

    If there is an error that a user is having trouble eliminating, you want the data checked in and possibly another user to work on it.

     

    Rather than using the MC parameter to prevent check in, use whatever workflow (e.g. promotion or change task) is used to "release" the data and prevent it from going forward if not = 0.

     

    Something to carefully consider.

    M
    mschulze14-AlexandriteAuthor
    14-Alexandrite
    October 27, 2025

    I understand your point, but in our case it is important to identify the bugs early. As users may e.g. not see, that a non metric system is used. 

     

    M
    mschulze14-AlexandriteAuthorAnswer
    14-Alexandrite
    October 31, 2025

    Well since there seems to be not OOTB working solution, I created enhancement request.
    If you like it please vote for:
    Extend WT ModelCheck Gatekeeper to prevent modifications in the workspace

     

    Terms & ConditionsCookie settingsAccessibility statement