1Z0-548 · Question #49
HR department of the XYZ company has two types of users: HR Administrator and Head of Department (HoD), using the HR Executive and HR Manager responsibilities, respectively. The HoD wants to ensure th
The correct answer is B. Create a new form using Custom form (Navigation: Security > Customform) under the HR. Option B is correct because in Oracle HRMS, the Custom Form (Security > Custom Form) allows you to define form-level access restrictions - including query-only/read-only mode - per responsibility. Since the Grade Description form and taskflow differ between the two responsibiliti
Question
HR department of the XYZ company has two types of users: HR Administrator and Head of Department (HoD), using the HR Executive and HR Manager responsibilities, respectively. The HoD wants to ensure that the HR Administrator has read-only access to the Grade Description form (Navigation: Work Structures > Grade > Description). Assuming that the Grade Description form and Taskflow associated with both the responsibilities are different, how can this be done?
Options
- AAdd the parameter QUERY_ONLY=YES to the Grade Description form associated with the HR
- BCreate a new form using Custom form (Navigation: Security > Customform) under the HR
- CUse HR Security profile to make the Grade Description form as read-only.
- DHR Forms cannot be made read-only.
- EExclude the Grade Description function in the HR Executive responsibility.
How the community answered
(24 responses)- A13% (3)
- B75% (18)
- C4% (1)
- D8% (2)
Explanation
Option B is correct because in Oracle HRMS, the Custom Form (Security > Custom Form) allows you to define form-level access restrictions - including query-only/read-only mode - per responsibility. Since the Grade Description form and taskflow differ between the two responsibilities, creating a Custom Form entry under the HR Executive responsibility and marking it as query-only grants the HR Administrator read-only access without affecting the HoD's full access.
Why the distractors fail:
- A - Adding
QUERY_ONLY=YESas a parameter applies the restriction at the form/function level globally, not per-responsibility; it would affect all users of that form, not just the HR Administrator. - C - HR Security Profiles control data-level security (which rows/records a user can see), not form-level access permissions like read-only.
- D - Factually incorrect; Oracle HRMS forms can indeed be made read-only via Custom Form configuration.
- E - Excluding the function removes access entirely (no access), which is more restrictive than read-only (query-only access), making it the wrong solution.
Memory tip: Think of it as "Custom Form = Custom Rules per Responsibility." When you need to tweak how a form behaves for one group without touching another, Custom Form is your targeted scalpel - while QUERY_ONLY and function exclusion are blunt instruments that affect everyone.
Topics
Community Discussion
No community discussion yet for this question.