A Implementation of Multi-Variable and Cascading Triggers

In order to use the multi-variable triggers and cascading triggers features of Advisor applications, use the following installation and implementation instructions.

Caution:

This functionality is highly advanced; use of it may not guarantee referential integrity. Make sure that all feature table items are correctly associated to the multi-variable configuration table. It is highly recommended that you work with a systems integrator if you use this advanced functionality.

To install the module

Modify the Module Registry file (jd/moduleRegistry.htm).
1. Include the Triggers API script file by adding the following script include code:
```
<script src="triggersEvents.js"></script>
```
2. Register the Triggers Module by adding the following call to the registry:
```
ISS.RegisterModule("triggerscode",ISS.GetCSPath()+"triggersCode.htm", ISSStr+".triggerscode", ISS.ON_DEMAND);
```
  Be sure the call is placed before the ”ISS.ModuleRegistrationComplete();” call.
Add the variable APP_EVALUATE_ALL_TABLES to custom/app_config.js as follows. If the variable is already defined, set the value to true.
```
var APP_EVALUATE_ALL_TABLES = true;
```
Modify the Kernel file (kernel.htm).
1. Include the Triggers API script file by adding the following script include code:
```
<script src="cs/triggersAPI.js"></script>
```
2. Create a new hidden frame in the kernel frameset.
  
  Expand the frameset definition to accommodate the extra frame by adding an extra ,* to indicate an extra row.
```
<FRAMESET rows="*,*,*,*,*,*,*,*,*,25%,*,*,*,*" border=0 frameborder=0 framespacing=0>
```
  The frame definition should be as follows:
```
<FRAME marginwidth=0 marginheight=0 src="javascript:''" name="triggerscode" scrolling="no">
```
Upload the (jd/moduleRegistry.htm) and (kernel.htm) into Advisor.

To implement the module

Add the PEP_DATASET_LOADED function to custom/customCode.js as follows. If this function is already defined, modify it to call ISS.Triggers_PreDatasetLoaded and return false, as shown.
```
function PEP_DATASET_LOADED(event,window,data) {
   ISS.Triggers_PreDatasetLoaded(event,window,data);
   return false;
}
```
Add the COP_AfterInputValueSet function to custom/customCode.js. If this function is already defined, modify it to call ISS.Triggers_AfterInputValueSet as shown.
```
function COP_AfterInputValueSet(table,selIndex) {
   ISS.Triggers_AfterInputValueSet(table,selIndex);
}
```
Add the PEP_ENGINE_RESULTS_GENERATED function to custom/customCode.js. If this function is already defined, modify it to call ISS.Triggers_EngineResultsGenerated and return false, as shown.
```
function PEP_ENGINE_RESULTS_GENERATED(event,window,results) {
   ISS.Triggers_EngineResultsGenerated(event,window,results);
   return false;
}
```
Register each multi-variable or cascade trigger construct in the pageset's UI Information file (p100_i.htm). These calls should be placed following the ISS.StartUIInfo() call. One API call is made for each multi-variable or cascade construct.
Verify that the API RegisterPriorityPages is being used in the UI Information file; any location which contains a multi-variable target must be registered as a priority page.