Skip to main content
A
amansfield10-Marble
10-Marble
January 4, 2011
Question

Modifying Revision sequence

  • January 4, 2011
  • 5 replies
  • 2031 views

When we were using Intralink 3.x we had a revision sequence that went from X0-X20,0,1,2,3...etc.

We have been using Intralink 9.1 since 9/09 and I have just discovered that we can only go as high as X10 before it increments to 0. I don't recall this being a limitation during migration and we obviously missed testing it..

I'm not sure we had any documents at rev X11 or higher, but today a user tried to revise to X11 and got an error message saying that the new revision did not exist or was not higher than the previous revision (X10)

Is there a way to update the revision sequence to add X11-X20 back in or is this a non-trivial task? It is the only sequence we have defined for documents.

I'm off to do some research..

5 replies

R
RussPratt8-Gravel
8-Gravel
January 5, 2011

Andrew,

You'll need to update your StateBasedRevision file (that might not be the exact name). I believe instructions are in the on line help and/or the Business Admin Guide.

Russ

S
SteveVinyard1-Visitor
1-Visitor
January 5, 2011
You can easily add revisions to the END of your revision sequence. Adding them into the middle is a different story and I'm not sure if it's possible or not.

[cid:image001.gif@01CBACAA.8996A480]

Steve Vinyard
Application Engineer
P
pwdmarshall1-Visitor
1-Visitor
January 5, 2011
Hi Andrew,

Yes you can modify the State Based Versioning sequence, but it will only
apply to newly created objects in the database. The Revision sequence for
an object is determined via the OIR at the time of creation, once an object
has been created it 'cannot be changed' (usually most things can be changed,
just depends how much money you want to throw at it!!)

So changing the sequence for new objects going forward is certainly possible
... As for changing the sequence for all the existing objects ... As you put
it 'non-trivial'

As Steve points out, you also have to be careful when adding Revisions to
the middle of a sequence ... Though I think it would be OK, you'd just have
to test to be sure.

Hope this helps.
Regards,
Paul
Sent from my iPhone

B
bfrandsen10-Marble
10-Marble
January 6, 2011
Hi
I have expanded my series in StateBasedVersioning.xml file once and it
worked OK for existing objects. You can safely add series in the middle if
you ensure that no objects have used the series following after.
It is normally because old objects runs dry for revisions that you need to
expand, so it is supported for existing objects too.
/Bjarne



Paul Marshall <->
05-01-2011 17:51
Please respond to
Paul Marshall <->


To
Steve Vinyard <->
cc
Andrew Mansfield <->, "-"
<->
Subject
[solutions] - RE: Modifying Revision sequence






Hi Andrew,

Yes you can modify the State Based Versioning sequence, but it will only
apply to newly created objects in the database. The Revision sequence for
an object is determined via the OIR at the time of creation, once an
object has been created it 'cannot be changed' (usually most things can be
changed, just depends how much money you want to throw at it!!)

So changing the sequence for new objects going forward is certainly
possible ... As for changing the sequence for all the existing objects ...
As you put it 'non-trivial'

As Steve points out, you also have to be careful when adding Revisions to
the middle of a sequence ... Though I think it would be OK, you'd just
have to test to be sure.

Hope this helps.
Regards,
Paul
Sent from my iPhone

slapha
slapha15-Moonstone
15-Moonstone
January 6, 2011

One thing we recently did to keep track of Engineering Orders against models was add more versions into the statebasedversioning.xml. This allowed us to release models at the same time as an EO.

What was

<seed name="ASME">

<value> - </value>

<value>A </value>

<value>B </value>

...

Became

<seed name="ASME">

<value> - </value>

<value>-1 </value>

<value>-2 </value>

<value>-3 </value>

<value>-4 </value>

<value>-5 </value>

<value>-6 </value>

<value>A </value>

<value>A1 </value>

...

It worked for us to just add in the new itterations. It will only show up when you go to revise a part, but it shows up for all parts that had that "ASME" series. There are other methods of creating rules in Windchill config files with multiple levels but we weren't able to get it to work how we needed it to. It took quite a bit of testing on a development server toverify everything would work how we expected it too.

From the Windchill "Versioning Schemes Administration" link on the site/utilities page it shows:

"

wt.series.HarvardSeries.seriesNames=MyHarvardSeries
wt.series.HarvardSeries.MyHarvardSeries.delimiter=.
wt.series.HarvardSeries.MyHarvardSeries.depth=16
wt.series.HarvardSeries.MyHarvardSeries.level.1=wt.series.MulticharacterSeries
wt.series.HarvardSeries.MyHarvardSeries.level.2=wt.series.IntegerSeries

In this example, the series levels alternate between a multicharacter series and an integer series. This Harvard series would result in version numbers such as A.1.A.1.

"

Based on how it's written I would think it would be A.1.1 where the last 1 is itteration.

Hope this helps,

Steven LaPha

"The comments and opinions expressed are my own and do not represent the view of United Space Alliance"

Terms & ConditionsAccessibility statement