Is it possible to control the execution order of attribute calculations in RTC?
I'm trying to capture the date that a work item was last moved to "Reopen" state as a calculated attribute. Because the calculation script has no knowledge of previous state, I've seen recommended workarounds using a second calculated attribute to capture the previous state. However, for this to work, the script for capturing the "LastReopenDate" has to run before the script that updates the "PreviousState". Is there any way to control this order? If not, is there still a way to make this approach work, or does this need to be done as a work item save follow-up action (using API extension)?
|
Accepted answer
I don't know the official answer. But from my observation, the order of the calculated value provider scripts are triggered follows the alphabetical order of the attribute id.
Ralph Schoon selected this answer as the correct answer
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
Thanks Lily! You are a huge help! This was the information I was missing.