cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Have a PTC product question you need answered fast? Chances are someone has asked it before. Learn about the community search. X

Add Windchill preference to allow overridable conflict for ModelCheck Gatekeeper

Add Windchill preference to allow overridable conflict for ModelCheck Gatekeeper

Status: Archived Submitted by 13-Aquamarine on ‎Oct 12, 2018 06:35 PM
6 Comments (6 New)

ModelCheck gatekeeper has limited usefulness as currently implemented. Once turned on, there are no options to allow the checkin to proceed if the criteria defined in the gatekeeper preferences aren't met.

 

Add a preference called "ModelCheck Gatekeeper Conflict Override" that when set to yes would generate an overridable conflict in the event viewer to notify the user that the models checked in do not pass ModelCheck but still would allow the user to check in the content. Most companies would like to allow ModelCheck errors on checkin yet prevent promotion/release of the content later. While it's easy enough to add an expression in the releasing workflow to prevent promotion of state with ModelCheck errors, a checkin warning is more difficult to implement as a customization.

See more ideas labeled with:
6 Comments
lhoogeveen
17-Peridot
17-Peridot
‎Oct 30, 2018 09:05 AM
‎Oct 30, 2018 09:05 AM

Having a Gatekeeper Warning Mode could definitely be useful - the current all or nothing is quite limiting. Admins may want the ability to specify: allow override # of errors, allow override of Gatekeeper Time Window, or both. Otherwise users may just skip ModelCheck altogether before checking in.

jwagh
16-Pearl
16-Pearl
‎Oct 30, 2018 09:11 AM
‎Oct 30, 2018 09:11 AM

And of course, a promotion request gate keeper as well! 

We want our users checking in, we don't want our designs being released with these issues. We don't care if there are missing parameters during the design, as it may not be known yet. By the time it gets released, it needs to be done. This should be specific to certain states as well, as a prototype state should have different requirements than production release.

Thanks!

jwagh
16-Pearl
16-Pearl
‎Oct 30, 2018 09:12 AM
‎Oct 30, 2018 09:12 AM

If we can specify the pass/fail by check name as well, that would be even better (but more unlikely).

MikeLockwood
22-Sapphire I
22-Sapphire I
‎Oct 30, 2018 11:33 AM
‎Oct 30, 2018 11:33 AM

Far better in general to allow all checkins and instead, branch a workflow (Promotion or Change) based on the value of MC_ERRORS.

lhoogeveen
17-Peridot
17-Peridot
‎Oct 30, 2018 02:08 PM
‎Oct 30, 2018 02:08 PM

Many companies do not use workflow. Giving options allows companies/admins to configure Gatekeeper to meet their needs.

olivierlp
Community Manager
Community Manager
‎Jan 03, 2023 03:23 PM
‎Jan 03, 2023 03:23 PM
Status changed to: Archived

Hello,

We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.

You can always post a new idea with all the details required in the form.

Thank you for your participation.