Bypass FAP/DAP validation

By default, during Attestation The act of confirming or attesting that something is true. For example, when punching out, users may need to attest that they took their meal breaks. the system validates whether an employee has the permissions (FAPs and DAPs) needed to edit paycodes A category of time or money that employees earn, for example, Regular Hours, Bonus, or Sick. and timecards. These permissions can be required depending on the information provided during the punch The entries on a timecard that mark the beginning (in-punch) or end (out-punch) of a work interval, such as the beginning of a shift or transfer..

You can configure an Attestation workflow to skip FAP and DAP validation, providing an enhanced employee experience that streamlines the Attestation process. When this functionality is enabled, the system bypasses validation of these FAPs and DAPs:

  • Employee FAPs
    • Allow negatives in My Timecard
    • Approval in My Timecard (Add)
    • Cancel meal deductions in My Timecard
    • Cancel meal deductions in Time Stamp
    • Comments in My Timecard
    • Hours Worked amount in My Timecard
    • Notes for Comments in My Timecard
    • Paycodes in My Timecard (Edit)
    • Punch edits in My Timecard
    • Transfers
      • Perform cost center transfers
      • Perform labor category transfers
      • Perform work rule transfers
      • Perform job transfers

  • DAPs

    • Pay Code edits

Setup

Setting up your system to bypass permissions validation during Attestation involves these steps:

  1. From the Main Menu, go to Administration > Application Setup > Access Profiles > Function Access Profiles > Employee > Attestation.
  2. Set Allow bypass of timecard permissions during Attestation to Allowed.
  3. Click Tap Save.

Note: This step is required only if the Add Paycode and Approve Timecard Attestation API tasks configured in your Attestation models have not already been updated. See Before you begin: inspect Attestation API tasks.

To determine whether or not you need to update Attestation models, inspect either the Add Paycode Attestation API task or the Approve Timecard Attestation API task in any Attestation models that use them, as summarized here:

  •  Attestation models that use the Add Paycode API task:
    • Attestation Paycode
    • Complex Meal Form with Paycode
  • Attestation models that use the Approve Timecard API task:
    • Time Review Form
    • Timecard Approve

This example shows how to inspect the Add Paycode Attestation API task:

  1. From the Main Menu, go to Administration > Application Setup > Attestation > Attestation Models.
  2. Select one of these Attestation models and click tap Edit .
    • Attestation Paycode
    • Complex Meal Form with Paycode
  3. In the Workflow Designer, click tap Visual Editor.

    The Visual Editor appears.

  4. Locate and click the Add Paycode API task.
  5. In the details panel at the bottom of the Visual Editor, click tap AttestationWorkflowAttributesAPI.
  6. In the Change value for "AttestationWorkflowAttributesAPI" dialog that appears, scroll through list of input parameters.
  7. Is the Set from Text value specified for the attestationProcessId input parameter?
    • If yes, the Attestation models have already been updated, and the system will bypass the FAPs and DAPs listed here during Attestation if you have configured the FAP as specified previously.
    • If no, you must manually update the Attestation models as described in the following procedure, How to update Attestation models
Note:

Use this procedure to update these Attestation models:

  • Attestation Paycode
  • Complex Meal Form with Paycode 
  • Time Review Form
  • Timecard Approve

Make backup copies of each of these models before continuing.

  1. From the Main Menu, go to Administration > Application Setup > Attestation > Attestation Models.
  2. Select the Attestation model whose API task you want to update and click tap Edit .
  3. In the Workflow Designer, click tap Visual Editor.
  4. Locate and click tap the API task.
  5. In the details panel at the bottom of the Visual Editor, click tap AttestationWorkflowAttributesAPI.
  6. In the Change value for "AttestationWorkflowAttributesAPI" dialog that appears:
    1. Click the Set from Text value specified for each input parameter.
    2. Copy and paste the value into Notepad or a similar text editor.
    3. Save the text file containing the parameter values. You will need to specify values for these input parameters later in this procedure.
    4. Close the Change value for "AttestationWorkflowAttributesAPI" dialog.
  7. In the Visual Editor:
    1. Make note of any Sequence Flows leading to or leaving from the API task you need to update. You will need to reconfigure these Sequence Flows later in this procedure.
    2. Make note of any Boundary Error Events configured for the API task. You will need to reconfigure them later in this procedure.

      Note: Sequence Flows and Boundary events are sometimes deleted from the Attestation model when you delete the associated API task. You will need to recreate deleted Sequence Flows and Boundary events after you have added the new API task.

    3. Delete the API task from the model.
  8. In the editor's workflow stencil set:
    1. Expand the Kronos APIs list.
    2. Drag AttestationWorkflowAttributesAPI and drop it on the Visual Editor canvas.
  9. Configure the newly added API task:
    1. Click the API task you just added to the model.
    2. In the details panel at the bottom of the Visual Editor, click tap Name.
    3. In the Name field, enter the name of the API task you just deleted from the Attestation model: Add Paycode or Approve Timecard, as required by the Attestation model you are editing.
    4. Next, click tap AttestationWorkflowAttributesAPI.
    5. In the Change value for "AttestationWorkflowAttributesAPI" dialog that appears:
      1. Configure values for previously existing parameters using the list of parameter values you saved in Notepad (see Step 6).
      2. Specify the value for the attestationProcessId parameter as ${attestationProcessId}.
      3. Click Tap Save.
  10. Reconfigure the Sequence Flows to and from the newly added API task.
  11. Reconfigure any Boundary Error Events required for the newly added API task.
  12. Validate the updated model and ensure that it has no errors.
  13. Save the model and deploy it.
  14. In Attestation Assignments (Administration > Application Setup > Attestation > Attestation Assignments), remove the assignment for the old Attestation model and assign the updated Attestation model. See Attestation Assignments for more information.
  15. Repeat this procedure in the remaining Attestation models.