If you only need to know when the current state occured, then use the
Created or Modified attribute on the Phase object via the Current Phase
link. For simplicity, I joined Phase to Life Cycle Managed via the
Current Phase Link. Then I selected the Phase.Last Modifed to display at
the date at which the object changed to its current state.
If the object is in a terminal state (i.e. Completed or
Canceled/Rejected), then you can use the different from object Created to
the Lated Phase's Last Modified to calcuate the cycle time for that
object.
I also find that using the following functions in the SELECT Tree help a
lot.
First, for dates, I use the Left Trim function. This gets rid of the
annoying seconds and minutes, but leaves the day, month, and year.
Second, I use the Round function on top of the Time Difference(days) to
display the difference from something like Created to Phase.Last Modified
so that the days actually show as whole numbers on the report.
Third, using Round on top of Time Difference(days) on top of the System
Date function followed by something like Phase.Last Modified for the
latest phase gives you the difference of the date the object changed into
its current state to todays date in whole number days.
You can use the difference from Created to latest phase modified for cycle
time calulations. And you can use the difference from Today's system date
to latest phase modified for how long an object has been in some
non-terminal state like Under Review or whatever.
Using the Latest Phase link to the Phase object is easienr and faster than
trying to get all lifecycle hitory objects and then trying to figure out
the latest one.
Al Anderson
Solar Turbines Incorporated
"Lockwood,Mike,IRVINE,R&D" <mike.lockwood@alconlabs.com>
08/25/2011 11:41 AM
Please respond to
"Lockwood,Mike,IRVINE,R&D" <mike.lockwood@alconlabs.com>
To
Brian Wilson <briwilson@coca-cola.com>, "-"
<->
cc
Subject
[solutions] - RE: QB State Change Date