Chile Punch Receipt

Comment: Configure a comment with the Paycodes category to which the process adds the checksum value and punch time, in seconds. See the Comments topic.

Paycode: Create a paycode to which the checksum value and punch time comment is added. To prevent confusion, do not select any of the Visible options in the paycode definition. See the Paycode definition topic.

Process Profile: Create a process profile containing the Chile Punch Receipt process. Assign the process profile to employees who punch using a timeclock or timestamp. See the Process Profiles setup page topic.

Attestation Conditions: Create a condition with a type of Always. See the Attestation Conditions topic.

Attestation Buttons: Create two buttons, Punch In and Punch Out; assign each with the Web and Clock display type. See the Attestation Buttons topic.

Attestation Assignments: Create two attestation assignments, one for the Punch In button and the other for the Punch Out button. Assign the ChilePunchReceipt process and the Always condition to each attestation assignment. See the Attestation Assignments topic.

Attestation Profile: Create an attestation profile and select each of the attestation assignments. Assign the attestation profile to employees who punch using a timeclock or timestamp. See the Attestation Profiles topic.

Workflow notifications: Configure generic workflow notifications that facilitate the Chile Punch Receipt process. Design the notifications by combining free text with available custom tags. See the Generic notifications topic. Examples include:

Name: Punch Success Workflow Notification

Name: Punch Failure Workflow Notification

Name: Missed Punch (Late In) Workflow Notification

Name: Punch Verification Workflow Notification

Select Trigger Business Process.

Template: ChilePunchReceipt_v1

Select Trigger Business Process Only.

Business process will run as System User.

Name: Error Workflow Notification

Timekeeping Alert Profile: Create a Late In timekeeping alert profile and select the Late In Workflow Notification. Assign the timekeeping alert profile to the employee Display Profile. See the Configure a timekeeping alert profile topic.

1. Log in to the appropriate tenant.

2. Go to Main Menu > Administration > Setup Data Manager.

3. Select the Source tenant where the Process Model resides, and select the template to copy. It is a .zip file. A message appears in the Source column: Source: Import from <filename>.zip.

4. Click Tap Review and Publish. The Publish Summary panel appears.

5. Review the Publish Summary panel. It lists the items that were extracted from the migration file. If you approve, click tap Publish with Comment or just Publish.

6. Click Tap Go to Publish History at the bottom of the panel to view the status of the data transfer. The Publish History page contains a table that lists the items you have published. If there were errors during the transfer, the button under the Errors column for that row is black.

7. To view details, click tap the appropriate row and click tap View Selected.

8. On the History for publish run page, click tap Show all to view the setup data that you published, and the errors that occurred, if any, listed by item type and name.

1. Go to Main Menu > Administration > Application Setup > Business Process setup > Process Models.

2. Select the ChilePunchReceipt process and click tap Edit. The process model enters edit mode.

3. Select the Decision Tables tab.

4. Click Tap Everyone's, and then select the decision table to edit.

5. Click Tap Decision Table Editor to add or update the rows in the table.

6. Click Tap Save and close.

   Caution:

   • Values entered in the decision tables are case-sensitive, and must match configured values in the application.

   • Do not remove variables, variable names, or variable types from any decision table.

7. Repeat the steps for each of the ChilePunchRecipt tables.
   • ChilePunchReceipt_v1_InternalParameters— Controls internal punch receipt parameters.

     Chile Punch Receipt Internal Parameters decision table structure

     Chile Punch Receipt Internal Parameters decision table

     Column	Description
     Admin	Internal user; do not change. Default value: SERVICES-LEVEL3
     InternalEmployeePunch	Employee punch time.
     InternalAlertType	Notification alert type.
     InternalAlertTransactionDate	Notification alert date.
     InternalAlertEmployee	Employee person number.
     InternalUDMDeviceID	Device ID.
     InternalAttestationEmployee	Attestation employee.
     InternalPunchVerificatonData	Punch data.
     TotalizationWaitTime	Totalization wait time.

   • ChilePunchReceipt_v1_Parameters— Controls the punch receipt process.

     Chile Punch Receipt Parameters decision table structure

     Chile Punch Receipt Parameters decision table structure

     Parameter	Description
     PayCode	Paycode name used to capture the punch data.
     PayCodeComment	Comment attached to the punch data paycode.
     PunchVerificationWorkflowNotification	The secondary workflow notification that initiates the business process to send the punch receipt.
     PunchSuccessWorkflowNotification	Punch success workflow notification.
     PunchFailureWorkflowNotification	Punch failure workflow notification.
     MissPunchWorkflowNotification	Missed punch workflow notification.
     ErrorWorkflowNotification	Error workflow notification.
     RUTAdditionalInformationFieldName	An additional field used to capture the employee national identification number

     Note: If the organization also uses the Chile Timecard Report extension, the PayCode parameter value in the ChilePunchReceipt_v1_Parameters must match the Pay Code - Punch Receipt Pay Code integration control parameter.
   • ChilePunchReceipt_v1_Devices— Contains each device where punches are performed.

     Chile Punch Receipt Devices decision table structure

     Chile Punch Receipt Devices decision table structure

     Column	Description
     Device ID	The device ID where the employee punches.
     Device Name	Device name.
     Device Description	Device description.

   • ChilePunchReceipt_v1_Locale— Allows customization of the text in the workflow form and notifications for different locales.

     Chile Punch Receipt Locale decision table structure

     Chile Punch Receipt Locale decision table structure

     Variable name	Variable type	Description
     Key	Text	Internal field label; do not change.
     Locale Policy	Text	Name of the locale policy for which the text applies. When the text applies to all locales, retain the empty value.
     Message	Text	Text displayed in the workflow form or notification.
     Description	Text	(Optional) Additional information.

     Note:

     • Localization of business process workflows remains optional, but is supported.​
     • You can translate some or all messages by adding lines to the table in their preferred translation for specific locales. Decision tables are scanned from top to bottom; therefore, place messages for the most commonly used Locale Policy at the top of the decision table and less-restrictive locale policies at the bottom.
     • Text within tags ("<>") must not be changed.
     • The decision table holds all messages represented with standard English labels; these apply to all locales when the Locale Policy is set to !=empty.
     • Names of the parameters in the decision table column ​Parameter Name must be used as is. If any parameter value needs to be localized for a different Locale Policy, copy the ​Parameter Name​ with the !=empty ​Locale Policy, add a new row to the decision table with the appropriate Locale Policy, and then add the localized value in the Message column.​
     • Decision tables support operators like "Contains," "Starts with," "Ends with," and "Is Not Empty." You can achieve your preferred results by following these examples:
       • To match any non-empty or any string (like *), use the "Is Not Empty" operator.
       • To match a string starting with "ABC" (like "ABC*"), use the "Starts with" operator and set the value to "ABC".
       • To match a string containing "English" as substring, use the "Contains" operator with the value "English".
     • The last row in the decision table must remain empty ("!=empty".)

     Sample Locale key parameters

     Sample Locale key parameters

     Key parameter name value	Use
     DEFAULT_ERROR	Process failure default error.
     VAR_INERNAL_DT_ERROR	The internal parameter decision table contains an invalid value.
     API_ERROR	The API call returns an error.
     INCORRECT_TOTALIZATION_PARAM_ERROR	The totalization parameter value is incorrect.
     VAR_PARAMETER_DT_ERROR	The parameter decision table contains an invalid value.
     INVALID_COMMENT	The comment name is invalid.
     PUNCH_IN	Contains the translation for the In Punch value defined by the PunchSuccessWorkflowNotification parameter in the Parameters decision table.
     PUNCH_OUT	Contains the translation for the Out Punch value defined by the PunchSuccessWorkflowNotification parameter in the Parameters decision table.

1. Go to Main Menu > Administration > Application Setup > Business Process Setup > Process Models.

2. Select the ChilePunchReceipt_v1 model.

3. Click Tap Edit, and then configure the required parameters and deployment dates. Select Notification Templates and Attestation from the Template Categories list.

4. Click Tap Save, and then select Return to deploy.