I need to know exactly what status is associated with a particular version of the code or file.Not considering the "Chronology".Is there any other way to get this information?
Would the History dialog have what you need?
Good morning Jeff,
this is my problem. The ePDM read only the "Actual State" of the Part Number in any version it is.
If I have, for example:
0A00012 (version) 1 -> (state) Modify
0A00012 (version) 2 -> (state) Approved
0A00012 (version) 3 -> (state) Modify
for ePDM the state is only "Modify", because it is the last (actual) state.
I need, for a Company Tool (developed like custom in ePDM) to know that in the version 1 the state was in "Modify", in the version 2 the state was in "Approved" and so on..
An SQL query (probably) that compare one to one the version whit it's real flow state.
Ours suppliers said that is not possible, because the flow like the revision are not in connection with the version and that the ePDM know only the version of code.
I hope my explain is clear.
thank you for your reply and for reply of everyone.
Only modifying a file and checking it in will create a new version. Changing state doesn't necessarily modify the file. If I understand correctly it sounds like you want a different version for each state change? If that is so then you could add an action to update a data card variable in each transition. That will modify the file and thus create a new version. That would create the possibility to have a report you want. Perhaps?
For SQL query, you would use the TransitionHistory table. It has the transitionID and file version for each state change for all documents.
SELECT [DocumentID] ,[RevNr] ,[Date] ,[UserID] ,[Comment] ,[FileSize] ,[FileDate] ,[Root] ,[WebRoot] ,[ProjectName] ,[FlushedDate] ,[LockDate] ,[ActiveConfigurationID] ,[VersionUID] ,[FileTimeStamp] ,[IsOverwritten] FROM [SWPDM_2021Beta1Std].[dbo].[Revisions]
I would say that Mike's response is correct. The only trouble is that when a data card value is updated during a transition it happens after the transition is made. So in the following example the Transition from WIP to SME happened at version 9, but the check in happened right after that making the part version 10.
To get it to check out/in before the transition you would have to create a dispatch.
Then you could have it check the file out, modify a variable and check it back in.
Retrieving data ...