Use the preconfigured templates

1. From the Main Menu, go to Administration > Application Setup > Attestation > Attestation Models.
2. Select Simple Question Form v2 and click Edit . Workflow Designer opens with the workflow displayed.
3. The workflow consists of a simple_form block with two answers. One answer ends the workflow and the other sends a notification, then ends the workflow. Using the "Do you feel safe at work" example, hover your mouse over the blocks in the image below for sample content and actions.
4. 
3. To open the editor, click Visual Editor from the upper right corner of the page. The main workflow edit page opens.

The simple_form block contains the text and buttons for the question.

1. Select the simple_form block. Notice that the area at the bottom of the screen is dynamic to what you select in the top area.
2. Select Referenced form: Simple question form from the bottom area.
3. 
3. When the Form reference - Simple question form page opens, click Open.
4. Select the question and click the Edit icon.
5. From the General tab, change the label of the question.
6. 
6. Select the Options tab and edit the answers or add additional options. Note that the IDs listed are here are important when posting answers. When finished, click Close.
7. To change a button label, select a button and click the Edit icon, then enter the new label for the button. You can also drag and drop different types of buttons from the list on the left side.
8. 
Caution: When modifying an attestation label, do not change any text enclosed in percentage signs, for example, %tcReview%. This information is a system variable that is used to fetch the appropriate data.
8. When finished, click the Save icon, give your new form a name and description, indicate if this is a new version of the form, and then click Save and close editor to return to the workflow page.

Back on the main workflow page, notice that a notification is configured for a negative answer that links to a generic workflow notification. To define the workflow notification:

1. Select the notification block, then select GenericNotification API Input/Output from the bottom of the page.
2. 
2. In the Change value box, change the notificationName field to use a specific workflow notification. Note that the workflow notification referenced is a generic notification and must be configured as described in Generic notifications. The name of the notification must match here and in the generic notification definition.
3. 
3. When finished, click Save.

Back on the main workflow page for the Simple_question_form, there are four arrows that represent flow sequences.

• Select the first arrow. The Flow condition in the bottom area says No condition configured. The same is true for the last arrow. There is no need to change these.
• Select the second arrow. This one is configured for the positive answer. The Flow condition in the bottom area says Condition configured.
• Select the third arrow. This one is configured for the negative answer .The Flow condition in the bottom area says Condition configured.

To modify the configured flow sequences:

1. Select the arrow for the positive answer and then select Flow condition: Condition configured from the bottom area.
2. On the Sequence flow condition page, click Advanced and then select the Depends on row and do the following:
   1. Depends on: Select Form field and then select didyouhavefuntoday_LABEL from the drop-down list.
   2. Note that you can use either the ID or the Label for the question, but the response must be same (ID or Label).
   2. If it's: Select equal, then click Value and select Yes from the drop-down list.
3. 
3. Click Save when finished.
4. Select the arrow for the negative answer and then select Flow condition: Condition configured from the bottom area. Repeat step 2.
5. Click Save when finished.

1. From the main workflow page, click the checkmark icon to ensure that your configuration is configured properly.
2. Click the Save icon when finished.
3. In the Save Model glance, enter the name, description, and comment for the new form and click Save and Return.
4. From the Attestation Models page, select the new model and click Deploy .
5. In the Business Process glance, enter the name and description of the new form as well as Attestation from the Categories drop-down, start and end dates, Active status and Show in the Action List.
6. 

The new form is now listed on the on the Attestation Workflow page.

1. From the Main Menu, go to Administration > Application Setup > Attestation > Attestation Models.
2. Select Attestation Paycode, click Copy , give the copied model a new name and description, then click Save.
3. Select the copied model and click Edit . Workflow Designer opens with the workflow displayed.
4. 
4. To open the editor, click Visual Editor from the upper right corner of the page. The main workflow edit page opens.

To modify the copied model, you start with the Initialize Variables task, which contains all of the variables that can be modified to tailor the model to meet your business needs.

1. Select the Initialize Variables task, then click Initialize Variables to display the following variables:
   • paycode — Defines the paycode to apply in the employee's timecard. The employee must have the permission for the paycode listed in his or her Function Access Control Point and Data Access Profile.
   • Default: Hours Worked
   • commentName — Defines the comment that the employee's note is associated with. This comment is attached to the paycode edit.
   • Default: Empty (text)
   • useTransfer — Indicates whether or not the system should use the transfer specified on the timestamp punch for the paycode edit that is generated by the employee’s Attestation response.
   • Default: false. The system will not use the transfer the employee selects for their timestamp punch but will instead use the employee's Primary Job and Primary Labor Category information for the paycode edit generated from Attestation.
   • If true, the system uses the transfer selected for the timestamp punch for the paycode edit generated by the employee’s Attestation response.
   • question — Defines the text of the question presented to the employee in the first Attestation form.
   • Default: Sample Text - Do you have travel time to report?
   • sendNotification — Defines if a notification is sent based on the workflow configuration.
   • Default: true
   • errorFormText — Can be modified for language or terminology.
   • Default: Sample text - Do you want to enter a new amount?
2. Select a variable and provide the content in the Value field. For example, you can change the text for the attestation question.
3. Repeat for all the variables you want to use.
4. Click Save.

To access the Add Pay Code task, select the Add Pay Code from the workflow and then select AttestationWorkflowAttributes API Input/Output. The input parameters used by the API are listed.

Note: The parameters in this list are informational and are the defaults that support the Hours Worked paycode. The next section explains how they might need to modify these depending on paycode type.

• amountType — Defines the type of paycode used.
• Default: Blank
• paycode
• Default: ${paycode}
• amount
• Default: ${amount}
• endDate
• Default: ${endDate}
• initiator
• Default: ${initiator}
• endDateTime
• Default: blank
• startDateTime
• Default: ${startDateTime}
• commentName
• Default: ${commentName}
• commentNotes
• Default: ${commentNotes}
• transferString
• Default: ${transferString}
• applyDate
• Default: blank
• startDate
• Default: ${startDate}

To define the days that the employee can select when selecting to enter a paycode edit:

1. Select the Prompt Employee Form.
2. In the User Task area, select Referenced form and then select Prompt Employee Form in the Form reference glance, and click Open. The Prompt Employee Form opens:
3. 
4. The Apply Date field is used to put the number of days before and after the current date for the paycode edit to apply to.
   1. Click in the Apply Date field and select the edit icon. The Edit date field 'Apply Date' glance opens. This glance has two tabs: General and Advanced.
   2. Click the Advanced tab and enter a positive number in the Minimum Date Offset and Maximum Date Offsetfields.
   3. Minimum Date (d-M-YYYY) — Do not edit.
   4. Maximum Date (d-M-YYYY) — Do not edit.
   5. Minimum Date Offset (Overrides Minimum Date): Enter the number of days before the current day the employee is punching on. Note that this number should be a positive value.
   6. Maximum Date Offset (Overrides Maximum Date): Enter the number of days after the current day the employee is punching on. Note that this number should be a positive value.
3. Click Close.

If needed, you can change the paycode accessed in the workflow. To do this, you use the Initialize Variable task and Add Pay Code task.

To change to hours-based pay code:

1. Change paycode variable value to name of hours pay code
2. In Initialize Variable task, add a new variable:
   • Variable name: amountType
   • Variable type: string
   • Value: HOUR
2. In Add Pay Code API task, update the input parameters:
   • Update amountType Set from Text: ${amountType}
   • Update startDateTime: Set from Text: blank
   • Update applyDate Set from Text: ${applyDate}

To change to days-based pay code:

1. Change paycode variable value to name of day-based pay code
2. In the Initialize Variable task, add a new variable:
   • Variable name: amountType
   • Variable type: string
   • Value: DAY
2. In the Add Pay Code API task, update the input parameters:
   • Update amountType: Set from Text: ${amountType}
   • Add startDateTime: Set from Text: blank
   • Update applyDate: Set from Text: ${applyDate}

To change to money pay code:

1. Change paycode variable value to the name of a money paycode.
2. In the Initialize Variable task, add a new variable:
   • Variable name: amountType
   • Variable type: string
   • Value: MONEY
2. In the Add Pay Code API task, updatethe input parameters:
   • Update amountType: Set from Text: ${amountType}
   • Add startDateTime: Set from Text: blank
   • Update applyDate: Set from Text: ${applyDate}

1. From the Main Menu, go to Administration > Application Setup > Attestation > Attestation Models.
2. Select Complex Meal Form with Paycode, click Copy , give the copied model a new name and description, then click Save.
3. Select the copied model and click Edit . Workflow Designer opens with the workflow displayed.
4. 
4. To open the editor, click Visual Editor from the upper right corner of the page. The main workflow edit page opens.

To modify the copied model, you start with the Initialize Variables task, which contains all of the variables that can be modified to tailor the model to meet your business needs.

1. Select the Initialize Variables task, then click Initialize Variables to display the following variables:
   • paycode — Defines the paycode to apply in the employee's timecard. The employee must have the permission for the paycode listed in his or her Function Access Control Point and Data Access Profile.
   • Default: Hours Worked
   • amount — Used to define the amount of the automatic paycode edit based on the employee's answer.
   • Default: 1
   • commentName — Defines the comment that the employee's note is associated with. This comment is attached to the paycode edit.
   • Default: Empty (text)

   • useShiftStartDate — Defines if the paycode edit is applied to the day the shift starts. If the shift crosses the midnight divide, this can be set to be false to have the paycode edit applied to the date the timestamp punch occurs.

     Default: true

   • useTransfer — Indicates whether or not the system should use the transfer specified on the timestamp punch for the paycode edit that is generated by the employee’s Attestation response.
   • Default: false. The system will not use the transfer the employee selects for their timestamp punch but will instead use the employee's Primary Job and Primary Labor Category information for the paycode edit generated from Attestation.
   • If true, the system uses the transfer selected for the timestamp punch for the paycode edit generated by the employee’s Attestation response.
   • firstQuestion — Defines the text of the question presented to the employee in the first Attestation form.
   • Default: Sample Text - Did you take all of your breaks?
   • SecondQuestion — Defines the text of the question presented to the employee in the second Attestation form.
   • Default: Sample text - Why?
   • sendNotification — Defines if a notification is sent based on the workflow configuration.
   • Default: true
   • errorFormText — Can be modified for language or terminology.
   • Default: Sample text - Do you want to enter a new amount?
2. Select a variable and provide the content in the Value field. For example, you could edit the question.
3. Repeat for all the variables you want to use.
4. Click Save.

To access the Add Pay Code task, select the Add Pay Code from the workflow and then select AttestationWorkflowAttributes API Input/Output. The input parameters used by the API are listed.

Note: The parameters in this list are informational and are the defaults that support the Hours Worked paycode. The next section explains how they might need to modify these depending on paycode type.

• amountType — Defines the type of paycode used.
• Default: Blank
• paycode
• Default: ${paycode}
• amount
• Default: ${amount}
• endDate
• Default: ${endDate}
• initiator
• Default: ${initiator}
• endDateTime
• Default: blank
• startDateTime
• Default: ${startDateTime}
• commentName
• Default: ${commentName}
• commentNotes
• Default: ${commentNotes}
• transferString
• Default: ${transferString}
• applyDate
• Default: blank
• startDate
• Default: ${startDate}

If needed, you can change the paycode accessed in the workflow. To do this, you use the Initialize Variable task and Add Pay Code task.

To change to hours-based paycode:

1. Change the paycode variable value to name of the hours paycode.
2. In the Initialize Variables task, add a new variable:
   • Variable name: amountType
   • Variable type: string
   • Value: HOUR
2. In the Add Pay Codes API task, update the input parameters:
   • Update amountType: Set from Text: ${amountType}
   • Update startDateTime: Set from Text: blank
   • Update applyDate: Set from Text: ${applyDate}

To change to days-based pay code:

1. Change the paycode variable value to the name of a day-based paycode
2. In the Initialize Variables task, add a new variable:
   • Variable name: amountType
   • Variable type: string
   • Value: DAY
2. In the Add Pay Codes API task, update the input parameters:
   • Update amountType: Set from Text: ${amountType}
   • Add startDateTime: Set from Text: blank
   • Update applyDate: Set from Text: ${applyDate}

To change to money pay code:

1. Change the paycode variable value to the name of a money paycode.
2. In the Initialize Variables task, add a new variable:
   • Variable name: amountType
   • Variable type: string
   • Value: MONEY
2. In the Add Pay Codes API task, update the input parameters:
   • Update amountType: Set from Text: ${amountType}
   • Add startDateTime: Set from Text: blank
   • Update applyDate: Set from Text: ${applyDate}

1. From the Main Menu, go to Administration > Application Setup > Attestation > Attestation Models.
2. Select Fix Missing Punch, click Copy , give the copied model a new name and description, then click Save.
3. Select the copied model and click Edit . Workflow Designer opens with the workflow displayed.
4. 
4. To open the editor, click Visual Editor from the upper right corner of the page. The main workflow edit page opens.

Instead of modifying the text boxes within the workflow, you should define variables in the Initialize Variables task, which contains all of the variables that can be modified to tailor the model to meet your business needs.

1. Select the Initialize Variables task, then click Initialize Variables to display the following variables:
   •  marginDays — Defines the days before and after the exception, for example:
   • 0 — The day of the exception
   • 1 — One day before and after the day of the exception
   • 2 — Two days before and after the day of the exception
   • 3 — Three days before and after the day of the exception
   • missingPunchQuestion — Defines the question that appears in the Attestation panel when there is a missing punch. The default text is: "You currently have ${totalNumberMissingPunches} missing punches. in your timecard. Would you like to fix them?"
   • workflowError — Defines the lead-in sentence when the system encounters an error. The default value is: "The workflow encountered the following:" then the system add the an error message if applicable.
   • attestationPunchComment — The default value is "&EMPLOYEE_FIX_MISSING_PUNCH." This causes an automatic comment to be generated in the timecard: "Missed punch fixed by employee." This is required for a note to appear. Do not delete this.
   • punchSummaryLabel — Defines the lead-in sentence before the summary of missing punches by date. The default value is "Summary of Punches by Date:" and the system then lists all the punches that need to be fixed on that day.
   • currentPunchToFixLabel — Defines the lead-in sentence before the specific punch to fix is displayed. The default value is "Current Punch to Fix:" and the system then lists the punch that needs to be fixed.
   • fixMissingInPunchForAbsenceSpan — This is used when there is a full day of missing punches because of an absence. The default value is "You are fixing the missing in-punch for the absence span:" and the system lists the in-punch for the span.
   • fixMissingOutPunchForAbsenceSpan — This is used when there is a full day of missing punches because of an absence. The default value is "You are fixing the missing out-punch for the absence span:" and the system lists the out-punch for the span.
   • punchDateLabel — Default value is Punch Date.
   • punchTimeLabel — Default value is Punch Time.
   • notesLabel — Default value is Notes.
   • punchSubmittedForManagerApproval — This is used when manager approval is required after the employee fixes the missing punch. The default value is " Your fixed punches will be submitted for approval."
   • punchSubmissionError — This is used when the employee makes a mistake correcting the punches. The system generates and error message and displays the text in this variable. The default value is "None of your punches were saved."
   • requiresNotesOnClock — This setting is for a future release and is set to "false." Do not change it.
2. If necessary, select a variable and change the content in the Value field. For example, you could edit the question.
3. Repeat for all the variables you want to use.
4. Click Save.

1. From the Main Menu, go to Administration > Application Setup > Attestation > Attestation Models.
2. Select Geolocation Consent Form V2, click Copy, give the copied model a new name and description, then click Save.
3. Select the copied model and click Edit. Workflow Designer opens with the workflow displayed.
4. 
4. To open the editor, click Visual Editor from the upper right corner of the page. The main workflow edit page opens.

To modify the copied model, you start with the Initialize Variables task, which contains all of the variables that can be modified to tailor the model to meet your business needs.

1. Select the Initialize Variables task, then click in the Initialize Variables field to open the Change value for "Initialize Variables" box:
   • Geolocationquestion — Defines the text of the question presented to the employee in the Geolocation Consent form.
   • Default: Sample text - Do you agree to your geolocation data being collected when you punch?
   • sendNotification — Defines whether a notification is sent based on the workflow notification.
   • Default: true
     Set to false if you do not want a notification to be sent to the manager upon the employee answering no to the question.
   • notificationName — References a specific workflow notification. The notification name must match the name of the notification to be sent.
   • Default: Attestation_notification
2. To modify the Geolocation Consent form question, select the Geolocationquestion variable and provide the content in the Value field.
3. Repeat for all the variables you want to use.
4. Click Save.