Skip to main content
A
avengerlegal1-Visitor
1-Visitor
June 25, 2010
Question

PDMLink Version Series

  • June 25, 2010
  • 12 replies
  • 2406 views

Does anyone know of a way to set the versioning series of a Part to do the following.

Start a ProE part in Prototype at 1.1 then when that part gets released it goes to A.1 without using the revise function.

12 replies

avillanueva
23-Emerald I
avillanueva23-Emerald I
23-Emerald I
June 25, 2010
Its documented. State based versioning.


M
22-Sapphire I
MikeLockwood22-Sapphire I
22-Sapphire I
June 25, 2010
This is the single most important set of configurations there is in PDMLink.

Need to envision Next Revision / State change as X and Y axes on a graph. States are the X axis; Revisions are the Y axis. The Lifecycle Diagrams from PTC do not lend themselves to clear thinking / planning / training on these concepts.

Changing the state of a given Revision is a horizontal (X axis) change; the content does not change when only the state changes. No new data is created.

Changing the Revision is not really that - instead it is a Save-As operation, leaving the previous Rev alone, and adding a new thing to work on at the new Revision, generally also that "working state" for that Revision. At the end of executing New Revision, you have the original item plus another identical copy at the New Rev and at the working state.

When the Revision series needs to follow Numbers, then Letters, there are two choices - simple file-based or state-based. Much more to this - we can chat off-line if you like.

This is the single most important set of configurations there is in PDMLink.

D
ddemay1-Visitor
1-Visitor
June 25, 2010
I actually just opened a call similar to this where if you reassign from a lifecycle using numeric to one of alpha and you do a revise it doesn't pick up the change. My OIR uses hardvardseries.statebased.

But yeah it would be nice to have more flexibility here ootb without a file based xml load file. My issue is not having a known sequence between numeric and alpha hence the two LC solution.




Sent from my Verizon Wireless BlackBerry
S
SteveVinyard1-Visitor
1-Visitor
June 25, 2010
Unfortunately StateBased versioning doesn't do this OOTB to the best of my knowledge. When you promote to Released, the Rev will not change from 1 to A...its only the NEXT time it's rev'd that it does the switch from 1 to A. There is a way to do this but it requires a modification to which ever workflow you are using to get up to released. Usually that is the "Promote" workflow. I don't have the information on hand on how exactly it's done at the moment.

Do you have to have the Rev changed when moving to Released? The software is designed to indicate, on the drawing, if something is released by mapping the "Lifecycle" state to the drawing and conveying the info in that method instead of the Rev.


Steve Vinyard
Application Engineer

[cid:image001.gif@01CB144B.3AB87160]
M
22-Sapphire I
MikeLockwood22-Sapphire I
22-Sapphire I
June 25, 2010
Need to also configure each LC state to use Numeric or MILSTD - have you done this?
D
ddemay1-Visitor
1-Visitor
June 25, 2010

Sure did!

We loaded in series resource bundle an additional one called alpha. I switched all states in one LC template to alpha and in the other all numeric.






Sent from my Verizon Wireless BlackBerry
S
SteveVinyard1-Visitor
1-Visitor
June 25, 2010
Hi Dave, you might try reassigning the lifecycle again and then watch the MethodServer output...or review the log for it. At times there can be some issues behind the scenes that aren't apparent from the what the UI would tell you.

Steve Vinyard
Application Engineer

[cid:image001.gif@01CB145F.06132E00]
M
22-Sapphire I
MikeLockwood22-Sapphire I
22-Sapphire I
June 25, 2010
The whole point is that in a single Lifecycle template, some of the states are NUMERIC and others are MILSTD.

When you Revise from a state that is NUMERIC, it Revises to the next number Revision
When you Revise from a state that is MILSTD, it Revises to the first / next alpha Revision


From: - [
S
sdrzewiczewski10-Marble
10-Marble
June 25, 2010
There is utility I don't have it handy to make objects change the versioning series called out by the oir

Let me know if you want me to dig it up

Sent from my iPhone

On Jun 25, 2010, at 3:07 PM, "Lockwood,Mike,IRVINE,R&D" <mike.lockwood@alconlabs.com> wrote:

> The whole point is that in a single Lifecycle template, some of the states are NUMERIC and others are MILSTD.
>
>
>
> When you Revise from a state that is NUMERIC, it Revises to the next number Revision
>
> When you Revise from a state that is MILSTD, it Revises to the first / next alpha Revision
>
>
>
>
>
> From: - [
>
D
ddemay1-Visitor
1-Visitor
June 25, 2010
I posted to this because I don't want states in the same LC to have different versioning series.

I understand how it is designed to work though.

Ideally, by having a reassign lifecycle it should behave the same way, but I'm going to customize to create new rev automatically and set it to a different LC template.

What this allows is for me to avoid calling the state of the object "production inwork" vs. "Inwork" . With one LC you would have to name your states with some kind of prefix to distinguish production vs prototype. I'm trying to avoid that.

So not to confuse anyone. I just thought I'd mention using two lifecycles to switch from versioning in prototype to production needs a little customization logic it appears.




Sent from my Verizon Wireless BlackBerry
Show more replies
Terms & ConditionsCookie settingsAccessibility statement