Action parameters are used to pass data from Oracle BI EE to the operations or processes that are represented by actions:
For actions that invoke Web Service operations, the parameters correspond to the simple types defined as attributes and simple elements (or complex elements deconstructed into their simple type components) within the input message of a Web Service operation and are read from the Web Service Definition Language (WSDL) that defines the operation and any parameters on that operation.
For actions that invoke a Java method, browser script, or server script, the parameters correspond to the arguments on the method.
For actions that navigate to a web page or invoke an HTTP Request, the parameters correspond to the parameters passed through from the URL.
For actions that navigate to BI Content, parameters are automatically passed from the source to the target. When navigating from one analysis to another, if the source row of data contains a field with the same logical name as a field used in a filter on the target analysis, then the value of this field will be passed as a parameter. Note that the operator on the filter should be set to is prompted or is equal to / is in.
When creating a named action or when associating an action with an object (such as a column on an analysis), you can specify whether a parameter is:
Fixed — A fixed parameter can be seen but its value cannot be set by a user.
Hidden — A hidden parameter cannot be seen and its value cannot be set by a user. (Note that hidden does not mean that the parameter is secure.)
Optional — An optional parameter does not require a value in order for the action to be executed.
Note: An action link or conditional action link that is on a displayed total or grand total will not pass a parameter outside of related BI content. |