We have a workflow for a part request, We want to measure the efficiency of the whole process.like the time taken by Part Request Object in diff states.
So I added a timestamp(after every Set State) and was able to capture it into a Workflow variable......Now I am just to get that value for timestamp posted to an external attribute so that I can use it in my report manager or adv search....Could anyone please advise ?
The LIFECYCLEHISTORY table includes the timestamp for all state changes, so an easier way to approach this type of reporting is to join LIFECYCLEHISTORY to the request and then report on "created" which is when it arrived at the state of interest. Need to add and join LIFECYCLEHISTORY once for each state of interest.
Thanks for the reply mike, If I understand correctly does the lifecycle history table is like :
If this is the table which I need to consider then that would solve my problem. Thanks again for your help.
Thanks for the help Mike, I have a question.
What is the actual difference between created and Modified by timestamp. It seems that the create timestamp is always constant for a given PR object across various iteration or versions. It’s the actual time of creation(of the object not the iteration).
Does it actually changes for each iteration of the object, with the created by date of when they actually got created?
But whereas modified by timestamp is only considered when someone(thing) actually modifies the object.
But wherever there is a state change, both the methods wont be in picture, right?
The PR object I am dealing with is versioned and Iterated.
Not too sure. May be a variety of situations depending on object type. Create generally refers to the Iteration / Revision (e.g. when Checked in for a Document/Part). Modify could mean Iterate but also could mean Move, State change, rename, lifecycle re-assign, etc. Would be nice to have a listing of this from PTC. Need to study the database table (UpdatestampA2) to really know.