It is possible to prevent users or suppliers from checkin with the wrong creo version.
This can be a matter if you have suppliers which are working for several customers with different creo versions.
PDMLink provides the possibility to allow specific versions or disallow them. See CS60297
In PDMLink provides a not that common version scheme for creo versions. See beneath
I´m looking for a complete mapping scheme on which PDMLink version belongs to which Creo Version.
I´m curious about your thoughts and findings.
e.g. 34 J-01 belongs to Creo 2.0 M090
<!-- PROE [25 J-03] [26 J-03] [27 J-03] [28 J-03] [29 J-03] [28 L-01] [29 L-01] [30 L-01] [30 L-03] [30 J-01] [30 J-03] [31 L-01] [31 L-03] [31 L-05] [31 J-01] [31 J-03] -->
<!-- PROE [32 J-01] [32 J-03] [32 L-01] [32 L-03] [32 L-05] [33 J-01] [33 J-03] [33 L-01] [33 L-03] [33 L-05] [34 J-01] [34 J-03] [34 L-01] [34 L-03] [34 L-05] -->
As we were playing around with this loadfile thing and didn´t get the expected result, we were looking for another solution to accomplish this.
Anyway this can be accomplished with a PRE_CHECKIN event .
We have it still under investigation as PTC would say.
If you have any input to this discussion please do not hestitate to comment.