Business Logic Scripting Examples

Here are a number of general guidelines for Business Logic Scripting:

Global variables

Be sure to initial the global values you declare. The PSL state mechanism cannot save variables with null values

General coding

Before using one of the objects listed below, verify that it exists (using a suitable IsExist method):
- All types of parameter (e.g. table, list, etc.)
- Custom attribute
- Resource
Make sure you provide a Business Logic Module with all the parameters it requires
Before changing a resource name verify which Metrics are using it and update them accordingly

Maps

Use of maps in clustered Metrics: Maps require more calculation effort from the engine, be aware that when you have clustering on a Metric you multiply the effort by the number of cluster items.
Large global maps within the Business Logic of clustered Metrics should be used only after careful consideration. While the Engine is calculating a clustered Metric it is busy loading the global variables from the states for each item in the cluster separately
Be sure to clear out maps and vectors after you are finished with them
If required to use large maps, make sure you manage the map efficiently by dividing it into logical ranges.