cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Windchill Check In Failure in Creo - Automatic Popup to Make Failures More Obvious

Windchill Check In Failure in Creo - Automatic Popup to Make Failures More Obvious

When a Windchill Check In fails within Creo, users have to notice that their check in failed in text in the bottom left of Creo (not obvious), notice/click on a cryptic icon at the bottom of Creo (not obvious), and then have to dig through several menus to find out why (not obvious). This is frustrating - especially to new users. Please create an automatic popup window for critical Creo/Windchill event failures that allow users to easily see (within one click) why the check in failed. This could be applied to other important event failures: check in, check out, revise, etc.

 

Current State:

 

 

 

idea_0-1645632985155.png

 

 

 

 

 

Future State:
Check In Failed - Open Conflict Management.jpg

8 Comments
BenLoosli
23-Emerald I

Make it an option...experienced users know how to find their errors.

Config.pro setting: error_mode_display verbose|minimal

 

lhoogeveen
17-Peridot

If it is an option including Windchill in the name would be helpful. windchill_error_display_msg yes|no.

I would vote for setting this to yes by default.

lhoogeveen
17-Peridot

@lwestbrook This idea could help make using Windchill Gatekeeper with Creo ModelCheck easier.

lwestbrook
16-Pearl

@lhoogeveen Thank you! 

TomU
23-Emerald III

My users are struggling with this as well.  We have implemented business rules that prevent check-in under certain conditions and people often don't realize the check-in failed unless they notice the little red circle.  It would be great if the conflict management dialog (#4 above) would automatically pop-up.  Of course a config option (or Windchill preference) to control this behavior probably isn't a bad idea either.

MikeLockwood
21-Topaz II

I’m personally extremely against preventing check in for any reason.

PTC’s configuration for Modelcheck gateway is one of these.

 

You want all users to store all their data in Windchill – including all early conceptual and preliminary work.  It takes time to meet all requirements / business rules, etc., and if these are enforced early then users take to storing data outside Windchill and checking in only when needed. Super counter-productive.

 

Instead, recommendation is to focus on the approval / release process.  Allow 10 throw-away concepts to be checked in and abandoned. Enforce needed rules only for release.  One of these ways is enforcing Modecheck no errors thru workflow.  Another is applying business rules only when going to Released.

TomU
23-Emerald III

@MikeLockwood,

Users are still allowed to upload so work won't be lost but we're preventing check-in when new items have references to objects in certain contexts that should never be referenced outside that context.  Once something has a reference in Windchill, it can *never* be deleted unless everything else referencing is also deleted.  We're trying to prevent inappropriate references from being persisted to the database, and the only way I know to do that is block check-in.

JayCrook
5-Regular Member

I vote yes for default and allow experienced users to turn off notification as mentioned previously.