When launched, a business rule can prompt you to enter variable information, called a runtime prompt. The business rule designer sets up runtime prompts. To learn how the display and values of runtime prompts are affected by certain settings and conditions, see “Understanding Runtime Prompts” in the Oracle Hyperion Planning Administrator's Online Help.
Notes:
If a business rule has a runtime prompt and Use Members on Forms is selected, the default member on the runtime prompt window matches the current member in the page or POV axes of the open data form.
Members and substitution variables on the Member Selection page are filtered by your access permissions and limitations set for the runtime prompt (for example, only Descendants of Q1). You cannot select a shared member in a runtime prompt.
If multiple business rules having runtime prompts are launched when saving the data form, enter values for each one successively, using the Next button.
To enter a runtime prompt:
Enter or select the input type specified by the runtime prompt, summarized in the following table:
Note: | Icons display only in Classic view, not in streamlined view. Your administrator determines your view. |
If any runtime prompt values are not valid, correct them.
Symbols indicate whether the values in runtime prompts are valid:
—the runtime prompt values are valid.
—the runtime prompt values are not valid (for example, the entry does not exist in the dimension hierarchy). You cannot launch a business rule until all runtime prompt values are valid.
Optional, for Calculation Manager business rules: To generate a file containing the runtime prompt values, select Create runtime prompt values file.
The file is saved as rule_name.XML, in the HYPERION_HOME/products/planning/RTP/user_name folder. Administrators specify this generated file when launching business rules with the CalcMgrCmdLineLauncher.cmd utility (see the Oracle Hyperion Planning Administrator's Online Help).
If the calculation is successful, the values in the database reflect the calculation results. See also Checking Job Status.
If you are using an Oracle Essbase substitution variable as the runtime prompt value and the value of that substitution variable is outside of the variable limits, the limits are ignored, and the rule launches successfully.