...
A system action is simply an action sequence that is configured to run either at system start time (i.e. when the application server starts) or session start time (i.e. when the user logs in). The output of a system action is available to other action sequences as input parameters. System actions are configured by adding the appropriate child elements to the <system-action> element in the pentaho.xml file.
------------------- - what to do with this junk? -------------
| Info | ||
|---|---|---|
| ||
TODO |
In addition, the output is available to portlets and/or Servlets/jsps.
(scope="global")
(scope="session").
(org.pentaho.ui.portlet.PentahoPortletSession)
(org.pentaho.core.session.PentahoHttpSession)
--------------------------------------------
| Anchor | ||||
|---|---|---|---|---|
|
The first step in configuring a system action is to locate and edit the pentaho.xml. In the Pentaho Preconfigured Install, the pentaho.xml file is located in the pentaho-demo/system folder.
...
We now have the name of the region that the manager is responsible for, but it is still in the result set. We don't want to keep the relatively "heavy" result set. We only need the string from the result set with the region information. We can use another JavaScript action to get the region string out of our result set, and then store the region string into our session.
In the Process Actions tree control, click on the Add control and select Generate Data From -> JavaScript.
Since we need access to the result set from the previous action, in the Scripts Input, click on the Add control and select RS_MANAGERS_REGION.
Next, add the following code in the JavaScript editor:
...
In order for our getActualsForRegion action sequence to run successfully, we need to configure the userNameToRegion action sequence to run when the user logs in. To do this we need to modify the pentaho.xml file. The pentaho.xml file is located in the system folder of the pentaho-solutions folder of the Pentaho Preconfigured Install. You should recall that in the section Configuring System Actions I discussed adding this xml element:
...