I use the default Scrum template as the starting point. The material presented was tested on RTC 4.0.3 and RTC 4.0.5 though should be pertinent to RTC 4.x with the understanding that screen captures may differ slightly between versions.
Process Enactment Workshop for CLM 2012, Lab 5 A larger treatment of the topic, updated in 2013. wiki page on Attribute Customization This has some important information about the JavaScript API and the sorts of things you can and cannot safely do from it. article on Customization of Work Items in Rational Team Concert. If this link doesn’t go to a useful page, just search the RTC help on “customizing attributes”. Info center topics on Customizing Attributes Depending on when you read this, topics can get reorganized. This article will refer to some of these rather than repeating them. These references are valuable and worth bookmarking if you will be working in this area often. Good material about attribute customizations already exists. This article actually uncovers one of those seams and has to work around it (as part of the example). (3) There are limitations in the WorkItem JavaScript API, some of which are noted below by reference, some of which you may discover on your own, especially if you ignore the references and just dive in. Depending on your environment, scripted customizations may be more difficult for you. (2) Support for debugging in clients varies. If you are doing something involved, consider writing a server-side contribution in Java. If you find yourself writing a lot of scripted customizations, you could be headed for performance issues. If you write some poorly performing JavaScript that is invoked on every work item save/retrieve, all of your users will suffer and there’s nothing IBM Rational can do to help you. Warnings: (1) You need to accept responsibility for what you do to your system. This article is intended to provide that example. #JS SCRIPT DEBUGGER HOW TO#
I think the question often comes up in the forum because there isn’t a simple end-to-end example illustrating the various aspects of being successful with scripted attribute customizations: creating appropriate attributes, configuring them correctly, establishing appropriate dependencies and, often, how to investigate (debug) when things don’t seem to be working. Attribute customizations (along with other features for customizing the product) are there to help you fit it to your team’s needs. Do you think that Time Remaining should be set to zero when a task is closed? Rational Team Concert doesn’t do that automatically because perhaps not everyone wants that (and it’s difficult to undo default behaviors). Wanting to use them makes sense - it’s a powerful and simple way to improve the way you work. JavaScript Attribute Customization questions come up in the /forum relatively often. Debugging attribute customization scripts – an example
0 kommentar(er)
