Sequencing Rules for Flows and Locked Tasks

The tasks in a flow use and build upon the results of previous tasks. To maintain data integrity and prevent deletions, the application determines whether a task should lock the results of previous payroll relationship actions.

Locking the results of payroll relationship actions prevent processing corrective actions, such as retrying a process. You must roll back or mark for retry the process that locks the results.

For example, the Calculate Prepayment process locks the results of the payroll relationship actions calculated in the payroll run. Before you can retry the payroll calculation process, you must roll back or mark for retry the prepayment process.

Reports that Create Locks

Typically, reports temporarily lock results of previous calculations while they run. Some reports do lock results. For example, the payslip report locks archived payment results. You may also create reports for a particular legislative data group that lock the results of periodic and year-end archive tasks.

To correct data for reports that lock results:

1. Roll back the report.

2. Roll back the archive task.

3. Correct the data.

4. Resubmit the report.

Common Locking Scenarios

You receive alerts when you submit a task and can't process payroll relationship records because another process has locked the records. For example, suppose you submit the weekly payroll run, and then submit a flow to calculate QuickPay. The submission is for a payroll relationship for the same payroll and payroll period as the regular payroll run. You receive an alert that the payroll relationship record is locked. You can't start the task to calculate QuickPay until the tasks in the weekly payroll run that use the locked results of the calculations for the payroll run is complete.