Hi Gerry,

after saving the setting and verifying it is set, scripting should work. This flag is however totally unrelated from the Eclipse UI supporting the configuration. What version of the eclipse client and the server are you running? I think in RTC2 there was no UI but in 3.0.x there certainly should be UI support in Process configuration>Project Configuration>Configuration Data>Work Items>Attribute Customizations.

You should be able to do the upload them etc. There should be 5 entries available to configure default values etc. However without setting the flag they will not run in the embedded engine on the client or server.

You should look at this page: https://jazz.net/wiki/bin/view/Main/AttributeCustomizationExamples

If you have heavily customized ClearQuest the functionality provided today might not be sufficient to do what you did with the hooks. You might need custom server extensions. My general advice would be also to stay as close to the built in RTC capabilities as possible. It would also make sense to review the current process and look at areas that could be made leaner. The most successfull implementations I have seen have followed both angles.

This is however very dependent on your environment. Do you have consultants to review what you attempt?

Hi Ralph,

After the change Gerry has made to the server configuration and extensive research, I was able to make Java Script based customization work, but only by manually modifying the Process Configuration Source.
I've upgraded though to the RTC client 3.0.1.2 and I've got the UI support for customization in place.

As a side note, do you happen to know if Sametime 8.5.x is supported in RTC 3.0.1.x? I've seen this question posted in lots of forums but I haven't seen any answer.

Thanks!

Hi Gerry,

strange, I have been able to work with scripting since some time. At least 3.0.1 had the UI.

Hi Ralph,

As a side note, do you happen to know if Sametime 8.5.x is supported in RTC 3.0.1.x? I've seen this question posted in lots of forums but I haven't seen any answer.

Thanks!

I haven't set up the integration since I am running so many versions of the client. I also use the Integrated Notes ST client. However, I couldn't find any hint which integrations are supported in the release notes. That information can be found in the client (when setting up the integration using the help link). I did not have time to install 3.0.1.2 so I suggest to check there. My client still says 7.5 and 8.0.x

You could also create a work item against RTC, Client or documentation to ask adding this information to the release notes.

3.0.1.2 is a service release, fixes can be found on the download page. So I guess no changes. However, since we use it internally I am wondering if it just works with the currently deployed ST.

Steps to fix this probles:
- In the seccion Attributes, remove the Calculate Value from each Attribute
- Delete the Calculated Value
- In the tab Links, save the javascript file as another name (the file name has to be different)
- Delete the javascript file from Attachments
- In the Tab Process Configuration, define again the calculated Value
- Assign the new file (the renamed file) to Local File Path
- In the seccion Attributes, re-assign again the Calculate Value to each Attribute

The problem is a bug, if we keep the same file, the system (RTC) doesn't reload the link files, then we have to change the source file and then all will be rebuilded automatically.

I finally have found the cause of the problem:
All javascript files (links) come together in a single temporary file com.ibm.team.workitem.service.internal.rest . IScriptProviderService

The classes are in alphabetical order. If you have a javascript with errors, none of the following classes are loaded, even if your code is correct.

Recommendation:
If you are creating a class, try to assign a name starting with the letter "a" with the purpose of occupy the first place the file.
Otherwise, if you are a member of a TeamArea, maybe a class created by someone doesn't allow your class is loaded correctly.

Thanks for sharing Boris.