About Runtime Prompts and Approvals Security
Administrators can design runtime prompts to honor Approvals security for members. Doing so prevents planners from changing data in planning units to which they do not have access, according to Approvals rules. For example, the administrator may not want planners to change data after they have promoted the related planning unit. In Oracle Hyperion Calculation Manager, administrators can set runtime Security for a member or members:
-
Approvals: Oracle Hyperion Planning allows a user to change member data if both these conditions are true:
-
The user has write access to the members (as assigned in Planning).
-
If the members belong to a planning unit, the user owns the planning unit.
If both conditions are not met, the user cannot change the members' data.
-
-
Write: Users launching the business rule who have write access to the members (as assigned in Planning) can change its data. The members' Approvals status is ignored.
-
Read: Users launching the business rule have read access to the members (as assigned in Planning). Approvals status is ignored.
-
Use Default: Security is applied to the runtime prompt only if member access is not set to None (that is, either read or write).
When business rules are migrated from an earlier release, they assume this setting.