It's all about the answers!

Ask a question

RTC calculated value script is calling issues


Govindaraj Ponnusamy (114) | asked Jun 09 '16, 1:10 a.m.

In RTC we have created two integer customized attribute, if the first attribute value (source) has changed then need to change the second attribute value. As well we can change the second attribute value manually.

RTC calculated value script is calling while changing the source attribute values as well saving the workitem. While calling the script in the Save workitem then it copied the first attribute value instead of my manual entered value 

We have two development and production server, in which the development server it is calling the script only one time while the source attribute values changes and it is not calling the script while saving the workitem.

But in production server the calculated Value script is calling both the time. What is the difference between these two server. If any one is facing the same issue, please suggest me to resolve this issue.

Thanks in Advanced.

Govindaraj.

One answer



permanent link
Ralph Schoon (59.7k23643) | answered Jun 09 '16, 2:59 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
edited Jun 09 '16, 3:00 a.m.
From the documentation https://jazz.net/wiki/bin/view/Main/AttributeCustomization#Calculated_values the calculated script is supposed to run in the following cases:


If you configure a Script-based calculated value, the script will be executed in three cases:

  •     When a work item is created, the script is executed
  •     When a work item is saved, the script is executed to recalculate the value.
  •     When an attribute which the current attribute depends on is changed, the value of the current attribute is recalculated. Depending on the presentations of the two attributes this may not work in all cases.


You can see that your production server is working as it should. I am not sure what is wrong or different on your development server. There is simply not any information here that provides enough to help.

Since calculated values are recalculated that way, it is best to make the calculated attribute read only. If the user is supposed to be able to override the calculated value, add an additional attribute e.g. Correction that the user can write to and that the calculation would prefer, if it is set.

Your answer


Register or to post your answer.