The Alerts Composer in Oracle HCM Cloud is a tool for configuring informational notifications sent via email or worklist, based on predefined events. Event Alerts are triggered by specific application events, such as a new hire or promotion. The question asks about the behavior of these alerts, particularly regarding the modification of triggering criteria.

Option A: Event Alerts are triggered when a specific event occurs in the application. You cannot modify the triggering criteria for notifications.This is the correct answer. Event Alerts in Alerts Composer are based on filters delivered by Oracle, tied to specific events (e.g., employee termination, assignment change). Oracle documentation states that the triggering criteria for these alerts are predefined and cannot be modified by users, as they are linked to system events controlled by Oracle’s seeded configurations. Users can customize notification content (e.g., message text) or recipients, but the event conditions themselves are fixed to ensure system stability and consistency.

Option B: Event Alerts are triggered when a specific event occurs in the application. You can modify the frequency in which the alert is triggered by using the Run Options tab within the alert.This option is incorrect. Alerts Composer does not provide a Run Options tab for Event Alerts, nor does it allow modification of the frequency of event-based triggers. Event Alerts are triggered immediately when the associated event occurs (e.g., a new hire record is saved). While Scheduled Alerts allow frequency settings (e.g., daily or weekly runs), Event Alerts are event-driven, and their triggering is not controlled by a frequency setting, making this option invalid.

Option C: Event Alerts are triggered when a specific event occurs in the application. You can modify the triggering criteria for notifications by modifying the Groovy script within the specific alert.This option is incorrect. Event Alerts in Alerts Composer do not allow modification of triggering criteria via Groovy scripts. Oracle restricts customization of event triggers to maintain system integrity, and Groovy scripts are used in other contexts (e.g., for validations or calculations), not for altering Event Alert conditions. Documentation confirms that triggering criteria are Oracle-delivered and non-editable.

Why this answer?The fixed nature of Event Alert triggers ensures standardized behavior across HCM Cloud implementations. Users can configure aspects like notification templates or recipients, but the core event conditions (e.g., “trigger when an employee is hired”) are locked, aligning with Oracle’s design and making A the correct statement.

References

Oracle Global Human Resources Cloud: Using Global Human Resources, Document ID: docs.oracle.com, Published: 2024-07-02

Section: Alerts Composer: “Event Alerts are based on Oracle-delivered filters and trigger when specific events occur. You can’t modify the triggering criteria.”

Oracle Global Human Resources Cloud: Implementing Global Human Resources, Document ID: docs.oracle.com, Published: 2023-12-12

Section: Configuring Alerts: “Event Alerts use predefined conditions; customization is limited to content and delivery options.”

Oracle Fusion Cloud Human Resources 24C What’s New, Document ID: docs.oracle.com, Published: 2024-08-27

Section: Alerts Enhancements: “Clarifications on Event Alerts and their fixed triggering mechanisms.”