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

The PTC Community email address has changed to community-mailer@ptc.com. Learn more.

APP Ignore Version Mismatch

APP Ignore Version Mismatch

We use PE-APP and APP-Desktop.  Unfortunately because they are given a different build number for essentially the same product (I hope) APP-desktop will show a version warning for documents built by PE-APP and there is no way to stop this.  (We are currently on PE 7.1 M20 and APP-11.2M20 (latest) which should be the same APP)

 

We would like the ability to switch this warning off for all or some mismatches.  For background, because we need to ensure the correct library is used we implement "library versioning" and  APP system versioning is less important.  We would like to be able to manage Version mismatches, to not make it us specific I would recommend that mismatches can be suppressed based on a range where each component of the version can be selected.  I.e.

 

I think the basic feature would be like this:-

 

Suppress versions:

[11][2]M[00] to [11][2]M[20]
- Ignore build number (checkbox)

 

Where anything in []’s is a drop down of all values available (+ignore value, +any). Ideally you would be able to create multiple “rules” like this

 

So you could create:-

• [11][2]M[00] to [11][2]M[20] Ignore build = true
ignores any build between 11.2M00 and 11.2.M20
• [11][IGNORE]M[IGNORE] to [11][IGNORE]M[IGNORE] Ignore build = true
Ignores any version 11 documents
• [11][1]M[20] to [11][1]M[20] Ignore build = false
Only ignores build number differences i.e. PE Desktop mismatch.

• [IGNORE][IGNORE]M[IGNORE] to [IGNORE][IGNORE]M[20] Ignore build = false

 

That way over the lifetime of the library you can test and validate which versions work with which based on the features used etc and only provide version feedback when it is appropriate.  I hope this gives a reasonable idea of what we're we would like to achieve.  Although some special fields, options, would make it easier i.e. a simple Ignore PE/APP differences for same version, ignore ALL,  ...  I am sure the developers can spec something decent from this.

3 Comments
GarethOakes
16-Pearl

I agree, James. The fundamental requirement is to handle equivalent versions of APP Desktop and Publishing Engine. A .3D file produced by Publishing Engine of a certain patch level (e.g. 7.1 M020) should not trigger errors on APP Desktop of equivalent patch level (e.g. 11.2 M020), and vice versa. That also provides compatibility between PE and the old APP-E product - 3D files from APP-E of the same patch level would not trigger errors in APP Desktop.

SimonTaylor
11-Garnet
Status changed to: Delivered
 
GarethOakes
16-Pearl

Cheers!