Self-check: from a submitted absence to an entitlement

Four questions on what deferred processing changes, which process confirms a deferred absence and which of its parameters can silently skip it, what an update does to an approval, and which rule keeps an entitlement alive after termination.

4 questionsPass mark 70%Back to the lesson
  • Explain what deferred processing changes
  • Name the confirmation process and its parameters
  • Explain approvals reset on update
  • Explain payable after termination

Every incorrect option names the misconception it represents. A wrong answer tells you which model of the process you reached for, which is the part that is worth correcting.

1. Deferred processing is enabled on an absence type. A worker submits an absence. What has happened to their entitlement at that moment?

Explain what deferred processing changes · targets: Treating a submitted absence as a complete one, because the absence is visible on the calendar and looks done.

2. An absence was submitted a week ago, is approved, and has no entitlement. The absence type has deferred processing enabled. What is the diagnosis, and what must be checked before running anything?

Name the confirmation process and its parameters · targets: Running the process with the default record selection and concluding that the absence was evaluated, when the selection never matched it.

3. Updating an already scheduled absence leaves the manager approval it already has, so a date correction does not re-open the approval.

Explain approvals reset on update · targets: Assuming an update is a correction of data only, and not a re-entry into the approval flow.

4. A worker is terminated while a statutory qualification entitlement is still running. Which rule decides whether they are still paid for it?

Explain payable after termination · targets: Assuming termination ends every entitlement, and treating the unpaid remainder as a payroll error.