C_THR81 Employee Central Core Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Configure a Business Rule on the Job Information object that triggers on the 'onSave' event and validates that the Contract End Date is not empty when Employment Type is 'Temporary'.

  Why this is correct

  To enforce that Contract End Date is entered when Employment Type is Temporary, a validation Business Rule on the onSave event is needed. This rule checks if Employment Type equals Temporary and if Contract End Date is empty, then raises an error. This prevents saving the record without the required contract end date, ensuring data completeness.

• ✗

  Configure a Business Rule on the Job Information object that triggers on the 'onInit' event to set the Probation End Date when the record is loaded.

  Why it's wrong here

  An onInit Business Rule executes when the portlet is initialized, not when the Employment Type changes. It would not respond to the user changing the Employment Type to Temporary. While it could set a default date, it would not dynamically update based on the selection. The requirement is to set the date upon change, so an onChange rule is needed, not onInit.

• ✗

  Create a Propagation rule on the Job Information object to copy the Employment Type value to the Probation End Date field.

  Why it's wrong here

  Propagation rules copy values from one field to another but cannot calculate dates or set conditional values. Copying Employment Type to Probation End Date would not achieve the 90-day calculation and would result in an invalid date value. Propagation is not suitable for date arithmetic or conditional logic; it is used for defaulting or synchronizing identical data types.

• ✗

  Use a Picklist Center configuration to make the Contract End Date field mandatory when Employment Type is 'Temporary'.

  Why it's wrong here

  Picklist Center manages picklist values and dependencies, not field-level mandatory enforcement based on another field's value. It cannot conditionally require the Contract End Date field. Mandatory field logic based on conditions is typically handled by Business Rules or field configuration settings, not by Picklist Center, which focuses on the list of values, not field properties.

• ✓

  Create a Business Rule on the Job Information object that triggers on the 'onChange' event of the Employment Type field and sets the Probation End Date using the 'addDays' function.

  Why this is correct

  To automatically set the Probation End Date based on Employment Type change, a Business Rule triggered on the onChange event of the Employment Type field is appropriate. The rule can use the addDays function to calculate 90 days from the start date and assign it to the Probation End Date field. This ensures the date is set dynamically when the employment type changes to Temporary.