Skip to main content
B
BuddyHudson1-Visitor
1-Visitor
February 12, 2014
Question

ModelCHECK Gatekeeper - almost there...check in still being blocked...

  • February 12, 2014
  • 1 reply
  • 2030 views

Need some MC insight here,

I have added the required options into ModelCHECK config_init.mc file.

I have added the IBAs using the Type and Attribute manager in Windchill at the Organizational level.

Created a test part, run model check, errors are 0, try to check in and get the following (see attached image)

There is something really minor going on. The one thing I do not see is the MC_VERIFIED parameter being added into the part.

Any help would be awesome!

Thanks in advance,

Buddy

1 reply

M
22-Sapphire I
MikeLockwood22-Sapphire I
22-Sapphire I
February 12, 2014

Just a comment...

PTC provides a mechanism to prevent checkin if ModelCheck errors are > some value.

We are of the opinion that this is not the best way to handle. You want the data checked in - possibly to allow another user to fix the problems that caused the errors.

Instead, you need to prevent the data from maturing such that it can be used by the business (e.g. prevent getting to Released state). We added code in our Promotion workflow that branches if any affected object has ModelCheck errors (ignores warnings). This works very well.

B
BuddyHudson1-VisitorAuthor
1-Visitor
February 12, 2014

Hey Mike,

Thanks for the quick reply. That does sound like a better way to do it...care to share a screen shot of your workflow...or if not could you explain in a little more detail about how this works?

Thanks,

Buddy

B
BuddyHudson1-VisitorAuthor
1-Visitor
February 13, 2014

Mike,

Can you show me what and where to change in this code? I am not a programmer and I also see "alcon" in the context. I know what the "Conditional" is but not sure exactly where to put it in the workflow...would appreciate you spelling it out if not too much trouble or time.

Thanks,

Buddy Hudson

Terms & ConditionsCookie settingsAccessibility statement