Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 12 Scorecards : Understanding and Working With Scorecards

Understanding and Working With Scorecards
A scorecard is a special type of concept. A scorecard serves as a set of static variables that is available throughout the project. You can use a scorecard resource to track key performance indicators or any other information.
Unlike concepts and events, each scorecard resource is itself a single instance — it is not a description for creation of instances. You create the scorecard at design time. Its values can be viewed and updated using rules.
It is more accurate to say there is one instance of a scorecard per inference agent. Each inference agent in an application has its own instance of the score card. Scorecards are not shared between agents.
Any agent that uses scorecards, and also uses Cache OM, must be assigned a unique key so that the correct scorecard can be retrieved from the cache. The key is set in the Processing Unit tab of the CDD. See Chapter 3, CDD Configuration Procedures in TIBCO BusinessEvents Administration.
It is not necessary to add scorecards to the declaration of a rule. Because there is only one instance of each scorecard in a deployed TIBCO BusinessEvents agent, any change causes all rules that use the scorecard in their conditions to be evaluated.
See Also
Chapter 24, Diagrams for information on using scorecard dependency diagrams.
Adding a Scorecard
Configuring a scorecard is similar to configuring a concept, except that scorecards don’t have relationships.
1.
In Studio Explorer, right click the folder where you want to store the scorecard and select New > Scorecard. You see the New Scorecard Wizard.
2.
You can’t change the name in the editor. To change the name of any project element, right-click the element in Studio Explorer and select Refactor > Rename. See Chapter 4, Element Refactoring Operations for more details.
3.
Click Finish. You see the Scorecard Editor.
4.
5.
Using a Scorecard in Rules
After configuring a scorecard resource, use rules to gather the information you need in the scorecard. To access the scorecard in a rule, use this syntax:
folder.folder.scorecard.property
For Example:
int i = SalesFolder.StatsScorecard.numOrdersProperty;
Scorecard Resource Reference
Scorecard configuration is the same as concept configuration, except that scorecards have no relationships with each other. Scorecards, therefore, have none of the properties used for setting up relationships. Scorecard properties can be of any primitive type.
See Concept Resource Reference for details about scorecard properties

Copyright © TIBCO Software Inc. All Rights Reserved