The display and values of runtime prompts are affected by such aspects as:
Whether there are valid members on the data form's Page/POV and whether the Use Members on Data Form and Hide Prompt options on the Business Rule Properties tab are selected (see Setting Business Rule Properties)
Whether the Runtime Prompt option is set during form design or set when designing the runtime prompt (for business rules created with Business Rules, see the Hyperion Business Rules Administrator’s Guide and for business rules created with Calculation Manager, see the Oracle Hyperion Calculation Manager Designer's Guide)
Whether the Use Last Value property is set when designing the business rule
Principles:
When launched from a data form, the values of members in the Page/POV take precedence if the Use Members on Data Form option is selected, regardless of whether the runtime prompt is hidden during design. The business rule is run without displaying the hidden runtime prompt to users, and the runtime prompt values are taken from the Page/POV members.
This is not the case when business rules associated with composite data forms are launched on save or from the left-hand pane or when business rules are launched from the Tools, then Business Rules menu. In these cases, the Use Members on Data Form setting is ignored, hidden runtime prompts get design-time values, and the last saved value takes precedence.
If the Use Last Value option is selected for the runtime prompt at design time, and if any of these conditions exist:
Use Members on Form is not selected
A runtime prompt is launched from the Tools, then Business Rules menu
Values cannot be pre-filled from the context
Then the precedence of runtime prompt values is determined by:
The last saved value takes precedence.
If a ruleset is launched, the value overridden at the ruleset-level at design-time is used.
If a business rule is launched, the value overridden at the rule-level at design-time is used. If it is not overridden at the rule-level, the runtime prompt value at design-time is used.
Runtime prompts that are hidden at design time never use the last saved value. In these cases, the Use Last Value setting is ignored.
The Use Members on Data Form and Hide Prompt options apply only to Member and Cross Dimension runtime prompt types (Cross Dimension runtime prompt types are available only for business rules created with Calculation Manager).
For Cross Dimension runtime prompts: the runtime prompt is not hidden unless all the prompts in the runtime prompt can be pre-filled from the Page/POV. The runtime prompt is displayed with some values pre-filled from the Page/POV and others filled according to Principles 1 and 2.
This table describes the result on runtime prompts of these settings and conditions:
Table 49. How Member Availability and Other Settings Affect Runtime Prompts
Availability of member on the Page/POV | Use Members on Data Form option is selected | Hide Runtime Prompt property is set during runtime prompt design | Hide Prompt option is selected for the data form | Result on Runtime Prompt |
---|---|---|---|---|
The member is available on the Page/POV to use as the runtime prompt value. | Yes | Yes | Yes or No Setting is ignored | The business rule runs without displaying the runtime prompt to users. Instead, the runtime prompt value is taken from the Page/POV member. |
The member is available on the Page/POV to use as the runtime prompt value. | Yes | No | Yes | If all runtime prompts can be pre-filled from the Page/POV context and are valid and within limits, the runtime prompts are not displayed. However, if even one runtime prompt value cannot be pre-filled from the Page/POV context, then all runtime prompts display, with values pre-filled wherever possible. All others follow Principle 2. |
The member is available on the Page/POV to use as the runtime prompt value. | Yes | No | No | The runtime prompt is displayed to users, with values pre-filled from the Page/POV. |
The member is not available on the Page/POV to use as the runtime prompt value. | Yes | Yes | Yes or No Setting is ignored | The business rule displays the runtime prompt to users, with values pre-filled according to Principle 2. For example, the data form context cannot be passed because the dimension of the runtime prompt is on rows or columns, so the Hide Prompt setting is ignored and the runtime prompt displayed. |
The member is not available on the Page/POV to use as the runtime prompt value. | Yes | No | Yes | The runtime prompt is displayed to users, with values pre-filled according to Principle 2. |
The member is not available on the Page/POV to use as the runtime prompt value. | Yes | No | No | The runtime prompt is displayed to users, with values pre-filled according to Principle 2. |
The member is available on the Page/POV to use as the runtime prompt value. | No | Yes | Not available | The business rule runs without displaying the runtime prompt to users. Instead, the design-time values are used. |
The member is available on the Page/POV to use as the runtime prompt value. | No | No | Not available | The runtime prompt is displayed to users, with values pre-filled according to Principle 2. |
The member is not available on the Page/POV to use as the runtime prompt value. | No | Yes | Not available | The business rule runs without displaying the runtime prompt to users. Instead, the design-time values are used. |
The member is not available on the Page/POV to use as the runtime prompt value. | No | No | Not available | The runtime prompt is displayed to users, with values pre-filled according to Principle 2. |
When hidden runtime prompt values are ambiguous, note:
If the data form context cannot be passed in (because the dimension is on the row or column, for example), hidden runtime prompts are displayed.
With hidden Cross Dimension runtime prompt types, if all prompts cannot be passed in from the context, the runtime prompt displays with values pre-filled context values and design time values for dimensions on the row or column. For example, if the Cross Dimension has runtime prompts for Period, Entity, and Scenario, and Entity is defined on the row, then the runtime prompt displays with the POV Scenario -> design time value for Entity -> Page Period.
If the context can be passed in for the runtime prompt value, but it is out of limits, then the runtime prompt is displayed with the context value pre-filled.
If there is more than one runtime prompt of type Member or type Cross Dimension combined, then the runtime prompts are displayed with the context values pre-filled. For example, if there is a member type runtime prompt for the Entity dimension and a Cross Dimension type runtime prompt with one prompt for the Entity dimension, then both runtime prompts are displayed. This rule does not apply to Calculation Manager rulesets or Business Rules sequences
When launched from the Tools, then Business Rules menu, runtime prompts are hidden and the design-time value (overridden at the rule or ruleset level) is used to launch the business rule. In Calculation Manager, a variable cannot be hidden unless a value is provided. If the provided design-time value is out of limits, then the runtime prompt is displayed with the design-time value pre-filled.
Runtime variables that are hidden during design never use the last saved value. The Use Last Value property is ignored, and the values are not saved to the database.