Unexpected status change, any logic in this?

#Date & TimeUserActionNote
2010-06-15 12:15:15 Christer OhlinOwn
22010-06-04 09:49:20Christer OhlinStatus Change Status of Revision 02 changed to: in work
2010-06-04 09:49:20 Christer OhlinStatus Trigger Released ownership
2010-06-04 09:49:20Christer OhlinDisown
12010-06-04 09:49:20Christer OhlinCheck In Rev: 02, Status:released RELEASED
2010-06-04 09:46:50Christer Ohlin Own
2010-06-04 09:37:27Christer OhlinStatus Trigger Released ownership
2010-06-04 09:37:27Christer OhlinChrister Ohlin Status Trigger Released ownership
2010-06-04 09:37:27Christer OhlinDisown

A file has been checked in , at point 1 above, and status changed to released. But at point 2, after disown, PDMW, changes the status back to in work? The very same second. Why? Comments appreciated.

Thanks in advance/ Staffan Holm

SolidworksWorkgroup Pdm
Answers 8
SF
SF 2010-06-23 Best Answer

What does your Lifecycles look like?

JH
JH 2010-06-23

Check your settings in the Vault Administrator - it's possible a checkin is affecting the status.

SH
SH 2010-06-23

Perhaps I should add that this happens only occasionally, most of the time, the status set at check in and remains as it should. Checked in with status released and still released two seconds later...

The lifecycle statuses are:

  • in work
  • for review
  • released
  • obsolete

And when a document at the released status before check in is next checked in, change the document status to in work.

Lifecycle settings as this:

comment imagecomment imagecomment imagecomment image
SF
SF 2010-06-23

Hmm... I might be missing something, but that is acting as expected.

SH
SH 2010-06-23

99 times of 100 (or something) a file that is checked in as released remains as released until next check in. But what happens occassionally is that a file that is checked in as released turns out to be in status in work. (As in the table above) For some reason the system decides that this time I jump to status in work?

What is set in the vault admin is (I hope); When a file with status released is next time checked in it is forced to go to status in work. This is at least the intention and how it works 99 times of 100.  ?

SH
SH 2012-03-22

The problem is that the status changes at check in (correct, as set in vault admin)  and then changes status without check in. In vault admin we have set that the status should change to, in this case, status in work at next check in. Not a ghost status change. If you look at the time log in the table above you see that the status changes two times in same second.

This happens very seldom but it has happened also after I wrote the first question.

JH
JH 2012-03-22

According to the time/date between your last 2 entrees, they are almost 2 years apart. If the problem is still persisting you should definately get your VAR to solve the problem.

SH
SH 2014-06-25

Closing of my old question.

PDMW does as it is told to do. But I didn't realize this. The issue described above happens when going from status Released to status Released - a status change that is out of normal sequence. Thanks for your answers Jesse and Jeff.