Overtime Exemption

An employee works in the service industry and earns commissions in addition to a base wage.

• Base wage = $10/hour.
• Overtime rate = $15/hour (150%).
• Minimum wage = $8/hour.
• Previous pay period = Week 42.
• Reference period = 7 days (Week 41: 4 —10 October).

On Payroll Monday of Week 43 (the current pay period), the integration evaluates the previous pay period:

Example reference period - Week 41

Date	Hours worked	Overtime hours	Base earnings	Overtime earnings	Commissions
04 Oct	10	—	$100	—	—
05 Oct	8	—	$80	—	$100
06 Oct	8	—	$80	—	$100
07 Oct	8	—	$80	—	$100
08 Oct	6	2	$60	$30	$100
09 Oct	—	8	—	$120	$300
10 Oct	—	—	—	—	—
Subtotals	40	10	$400	$150	$700

The total earnings are $1250 ($400 base + 150 overtime + 700 commissions) for 50 hours (40 worked + 10 overtime).

Example previous pay period - Week 42

Date	Hours worked	Overtime hours	Base earnings	Overtime earnings	Commissions
11 Oct	10	—	$100	—	—
12 Oct	8	—	$80	—	—
13 Oct	8	—	$80	—	—
14 Oct	8	—	$80	—	—
15 Oct	6	2	$60	$30	$50
16 Oct	—	8	—	$120	$100
17 Oct	—	—	—	—	—
Subtotals	40	10	$400	$150	$150

The total earnings are $700 ($400 base + 150 overtime + 150 commissions) for 50 hours (40 worked + 10 overtime).

The integration validates the following conditions:

1. Are commissions greater than 50% of total earnings during the reference period?
   • Total earnings = $1250.
   • 50% of total earnings = $625.
   • Commissions = $700 which is greater than 50% of total earnings.
   • So, this condition is met.
2. Is the average rate of pay greater than 1.5 times the legislated minimum hourly wage for every hour worked during the previous pay period?
   • Average pay rate = $700/50 hours = $14/hour.
   • Minimum hourly wage = $8/hour.
   • Minimum hourly wage X 1.5 = $12/hour which is less than the average pay rate.
   • So, this condition is met.
3. Did the employee work overtime hours during the previous pay period?
   • Overtime = 10 hours.
   • So, this condition is met.

Because all conditions are met, the integration adds an override work-rule transfer to remove overtime hours and overtime earnings on the days worked during the previous pay period (Week 42, Oct 11—16).

The employee's Timecard shows the work-rule transfers, and comments and notes provide details.

Example Timecard and work rule transfers

Before you start

1. Configure Access to Integrations.
2. Deploy the FLSA7iOvertimeExemption_v1 integration; see the Deploy Integrations topic.
3. Combined paycode: Create combined paycodes that hold all paycodes for worked hours, paycodes for commissions, and overtime paycodes to exempt as follows:

   See the Combined Paycodes topic

   1. Select Main Menu  > Administration > Application Setup > Pay Policies > Pay Codes > Combined Pay Codes.
   2. Create a combined paycode to hold all paycodes for worked time such as Regular, Commissions, Overtime. Click Tap New.
   3. In Name, enter Total Worked.
   4. In Apply As Of, select the effective date of the combined paycode.
   5. In Summarize in, select Hours.
   6. Select Visible in Report Options and Report Totals so that the combined paycode is in reports.
   7. Select Visible on Totals Tab in Timecard so that the combined paycode appears in the Totals tab on the Timecard.
   8. In Available Pay Codes, select the paycodes that make up the combined paycode, and click the right arrow to move them to Selected Pay Codes.

      Example: Select Regular, Commissions, and Overtime.

   9. Click Tap Save.
   10. Create a combined paycode to hold all paycodes for commissions. Click Tap New.
   11. In Name, enter Total Commissions.
   12. In Apply As Of, select the effective date of the combined paycode.
   13. In Summarize in, select Money.
   14. Select Visible in Report Options and Report Totals so that the combined paycode is in reports.
   15. Select Visible on Totals Tab in Timecard so that the combined paycode appears in the Totals tab on the Timecard.
   16. In Available Pay Codes, select the paycodes that make up the combined paycode, and click the right arrow to move them to Selected Pay Codes.

       Example: Select Commissions.

   17. Click Tap Save.
   18. Create a combined paycode to hold all overtime paycodes to exempt when all conditions for FLSA Section 7(i) are met. Click Tap New.
   19. In Name, enter Total Overtime.
   20. In Apply As Of, select the effective date of the combined paycode.
   21. In Summarize in, select Hours.
   22. Select Visible in Report Options and Report Totals so that the combined paycode is in reports.
   23. Select Visible on Totals Tab in Timecard so that the combined paycode appears in the Totals tab on the Timecard.
   24. In Available Pay Codes, select the paycodes that make up the combined paycode, and click the right arrow to move them to Selected Pay Codes.

       Example: Select Overtime.

   25. Click Tap Save & Return.
4. Comment: Configure a comment to identify the overtime exemptions.

   See the Comments topic.

   1. Select Main Menu  > Administration > Application Setup > Common Setup > Comments.
   2. Click Tap New.
   3. In Comment Text, enter Adjusted by FLSA 7i Integration.
   4. In Available Categories, select Punches and click tap the right arrow  to move it to Selected Categories.
   5. Click Tap Save.
5. Get the URL for the APIGatewayServer for the tenant.

Select the environment

1. Open the Integration Template Designer: Select Main Menu  > Administration > Application Setup > Integrations Setup > Design Integration Templates.

   Note: If prompted, enter your Username and Password. Click Tap Log in.

2. Select the Manage tab > Atom Management.
3. Select your environment.

Select environment extensions

1. In Administration, click tap Environment Extensions.
2. In Process Filter, click tap the magnifying glass . It can take several seconds before the button becomes active.
3. Scroll to and select the integration pack: FLSA7i Overtime Exemption > FLSA7iOvertimeExemption_v1.

Caution: If you select Use Default for the connection settings and process properties, ensure that Value is blank. If Value is not blank, that value overrides the default value whether or not Use Default is selected or cleared. Example: If the default value is abc, but Value shows xyz, the integration uses xyz regardless of the setting of Use Default.

Configure connection settings

1. Select Connection Settings.

2. From the Connection dropdown list, select and configure the following:

   Connection Settings

   Setting	Required	Actions
   APIGatewayServer	Required	To change the default API gateway server: Clear Use Default. Enter the URL to the server. Example: <tenantURL>/api

Configure process properties

1. Select Process Properties.

   Caution: Do not edit the default values of the AuthenticationProperties. By default, cookies are enabled and set the values for authentication properties.

2. Select FLSA7iOvertimeExemption_v1_ProcessProperties to set process properties that must be configured before the integration can run.

   Process Properties

   Property	Required	Actions
   Reference Period	Required	The number of days before the start date of the previous pay period that the integration validates for worked hours and commissions. Default = 28 days. (Optional) To change the number of days: Clear Use Default. Enter the number of days to validate from 1 to 365 days. Note: To evaluate commissions, the reference period can be as short as one month but cannot be longer than one year.
   Hyperfind	Required	Default = 1 (shown as blank) which indicates All Home and includes all active employees. To use a Hyperfind query for another group of employees: Clear Use Default. Enter the ID of the Hyperfind. Note: Ad-hoc Hyperfinds are not supported. All Home does not include terminated and inactive employees even if they have totals during the period. To include these totals, configure a Hyperfind that includes terminated and inactive employees and select that Hyperfind in this process property. The maximum number of employees in a Hyperfind is 3500. To process more employee records, divide the population into smaller Hyperfinds to run sequentially.
   Individual Employee ID	Not required	Default = Include all employees. To process data for only a limited group of employees: Clear Use Default.  Enter the person numbers, as defined in the source system, each separated by a comma (,) but no spaces. Example: 13997,15556,20012
   Total Worked	Required	The combined paycode that holds all paycodes for worked time such as Regular, Commissions, Overtime. Default = Total Worked. (Optional) To change the paycode: Clear Use Default. Enter the name of the paycode.
   Total Commissions	Required	The combined paycode that holds all paycodes for commissions. Default = Total Commissions. (Optional) To change the paycode: Clear Use Default. Enter the name of the paycode.
   Total Overtime	Required	The combined paycode that holds all overtime paycodes to exempt when all conditions for FLSA Section 7(i) are met. Default = Total Overtime. (Optional) To change the paycode: Clear Use Default. Enter the name of the paycode.
   Average Rate of Pay Multiplier	Not required	The average multiplier for the calculation of the average rate of pay for overtime hours. The multiplier value is used as follows: Average rate of pay > Multiplier x Minimum wage rate Default = 1.5 times the base rate of pay. (Optional) To change the multiplier: Clear Use Default. Enter the multiplier.
   Earnings Percentage	Not required	The percentage for the calculation of the earned commissions. Default = 50% of the base rate of pay. (Optional) To change the percentage: Clear Use Default. Enter the percentage.
   Comment	Required	The comment that identifies the overtime exemptions for the override exemption. Default = Adjusted by FLSA 7i Integration. To change the comment: Clear Use Default. Enter the comment.
   Comment Note	Not required	A note is free text that you use to show the amounts for the comment with the override exemption. Default = Reference Period: #referenceperiod#||Total Earnings: #earnings#||Commissions Earned: #commissions#||State Minimum Wage Reference: #staterate#||Previous Pay Period Average Rate of Pay: #actualrate#. To change the note: Clear Use Default. Enter the note but keep the #referenceperiod#, #earnings#, #commissions#, #staterate#, and #actualrate# placeholders. The integration completes these placeholders with the actual dates and amounts as follows: #referenceperiod#: Reference period dates in the format MM/DD/YYYY—MM/DD/YYYY #earnings#: Total Worked paycode wage for the reference period #commissions#: Total Commissions paycode wage for the reference period #staterate#: Minimum hourly wage rate = value from cross-reference table X Average rate of pay multiplier. #actualrate#: The employee's average rate of pay from the previous pay period ||: The integration displays text after this character in another note.
   Total Worked Threshold	Not required	The minimum time that is required in the Timecard for the Total Worked (hours) paycode to be eligible for the overtime exemption. Default = 00:01 (1 minute). To change the threshold: Clear Use Default. Enter the length of time. Use the format hh:mm.
   Override Workrule Suffix	Required	A suffix for override work rules. Default = blank. To add suffixes for override work rules: Clear Use Default.  Enter the suffixes, each separated by a comma (,) but no spaces. Example: _OTExempt,_OTOverride,_WithoutOTWorkrule
   Process Signed-Off Period	Not required	Whether to process data for signed-off periods. Default = False. To change the value: Clear Use Default. Enter one of the following: True = Process data for signed-off periods. False = Do not process data for signed-off periods.
   Totalization Wait Time	Not required	How long to wait to run the integration again for employees whose override work rules during the previous pay period were rolled back. Default = 600 seconds. To change the wait time: Clear Use Default. Enter the number of seconds for the integration to wait before checking totalization again. This parameter has no maximum value.
   Totalization Retry Count	Not required	The maximum number of times to run the integration again when employee records were not totalized. Default = 5 retries. To change the number of retries: Clear Use Default. Enter the number of retries. This parameter has no maximum value.

Configure cross-reference tables

Cross-reference tables (CRT) are the look-up tables that the integrations use to translate parameter values. One or more data values from the source system can be used to assign one or more parameters in the destination system.

1. Select Cross Reference.

2. From the Cross Reference dropdown list, select the following tables:

   FLSA7iOvertimeExemption_v1_MinimumBaseWageByLocation_CRT: Maps the minimum wage rates to locations in the business structure.

   Column headers and definitions:

   VerID — Version number for the minimum wage at the location. Start at 1 and increment sequentially by location.

   Location — The business structure path for the location.

   Minimum Wage Hourly Rate — The legislated minimum hourly wage.

   Start Date — The effective start date of the base wage rate at the location.

   End Date — The effective end date of the base wage rate at the location.

3. Select Override to:

   • Download the tables when you run the integration
   • Edit the table cells in Extensions
4. Enter the names and types of the paycodes.
5. When you finish, click tap OK.

API details

API name	Section	Type	Resource path	Location
Execute Hyperfind	Commons	POST	/v1/commons/hyperfind/execute	_Execute-Hyperfind
Retrieve Timecards	Timekeeping	POST	/v1/timekeeping/timecard/multi_read	_GetTimeCardMetricsDataPP _GetReRunEmployees
Submit Integration Details	Platform	POST	/v1/platform/integration_executions	_SubmitIntegrationDetails
Process Callback	Platform	POST	/v1/platform/integrations/update_status	_WFDCallback
Retrieve Comments	Commons	GET	/v1/commons/comments	_RetrieveComment
Retrieve Persons	People	POST	/v1/commons/persons/extensions/multi_read	_GetEmpDetails
Update Timecard	Timekeeping	POST	/v1/timekeeping/timecard	_UpdatePunches
Retrieve Data	Commons	POST	/v1/commons/data/multi_read	_GetEmpDetails
Retrieve Paycodes	Timekeeping	POST	/v1/timekeeping/setup/pay_codes/multi_read	_RetrievePayCode
Retrieve All Work Rules	Timekeeping	GET	/v1/timekeeping/setup/full_work_rules	_Non-DynamicCaches
Retrieve Timecard Data—Multiple Employees	Timekeeping	POST	/v1/timekeeping/timecard_metrics/multi_read	_GetTimeCardMetricsDataReferencePeriod _GetTimeCardMetricsDataPP
Bulk Enable Edits	Timekeeping	POST	/v1/timekeeping/enable_edits/import	_EnableHistoricalCorrection

After the integrations are deployed and the connection settings and process properties are configured, install the integrations to make them available for running or scheduling.

1. Select Main Menu  > Administration > Application Setup > Integrations Setup > Install Integrations.
2. Click Tap Create .
3. Enter an appropriate, unique, and descriptive Integration Name.
4. (Optional) Enter a Description.
5. Do not select API Integration.
6. In File Access, select None to not select a connection.
7. (Optional) If the person who runs the integration doesn't have full access to integrations, select Execute Integration with System Account. This allows the integration access to all APIs in the FAP, and the relevant permissions and data, regardless of the FAP and GDAP of the person who runs the integration.

8. (Optional) Select Re-Run to allow repeated runs of the integration with the same parameter values as the previous run.

9. Email Notifications

   (Optional)

   1. Select Yes to send email and control center notifications for integration runs.
   2. Enter the email addresses of the recipients for the following types of run status. For multiple recipients, separate the addresses by a comma, but no spaces:

      In Progress — The integration run started and has not finished.

      Completed — The integration ran successfully without errors.

      Failed — The integration ran successfully, but one or more records have errors. The integration run is treated as failed. If Abort on Failure is configured in an integration set, the integration set stops.

      Completed with Errors — The integration run has errors or could not run.

10. In Skip Configuration, select None (default) to allow multiple integrations to run at the same time or with the same data without restrictions.
11. Do not select Allow Minute Interval.
12. Integration template and parameters
    1. In Integration Template, select FLSA7iOvertimeExemption_v1.
    2. Click Tap Assign .
    3. In Integration Parameters, you can override default settings. Specify the following parameters:

       (Required) Specify the number of days before the start date of the previous pay period that the integration validates for worked hours and commissions:

       Click Tap Create .

       Reference Period

       Parameter Name	(Required) Enter Reference Period.
       Description	(Optional)
       Template Parameter	(Required) Select Reference Period.
       Parameter Type	(Required) Select Numeric.
       Default Value	(Optional) Enter 28.
       User Prompted	If the value does not need to be changed when the integration runs, select No.

       Click Tap Save.

       (Required) Specify the default hyperfind query that contains the employees:

       Click Tap Create .

       Hyperfind

       Parameter Name: (Required) Enter Hyperfind.

       Description: (Optional)

       Template Parameter: (Required) Select Hyperfind.

       Parameter Type: (Required) Select Hyperfind.

       Default Value: (Optional) Enter the name of a hyperfind query or 1 for All Home.

       User Prompted:

       • To prompt the person who manually runs the integration to set this parameter, select Yes.

       • If the value does not need to be changed when the integration runs, select No.

       Click Tap Save.

       (Optional) Specify whether to process data for a limited group of employees:

       Click Tap Create .

       Individual Employee IDs

       Parameter Name: (Required) Enter Individual Employee IDs.

       Description: (Optional)

       Template Parameter: (Required) Select Individual Employee IDs.

       Parameter Type: (Required) Select Text.

       Default Value: (Optional) Can be a single or multiple values separated by commas (,) and no spaces. Leave blank to process data for all employees.

       User Prompted:

       • To prompt the person who manually runs the integration to set this parameter, select Yes.

       • If the value does not need to be changed when the integration runs, select No.

       Click Tap Save.

       (Required) Specify the combined paycode that holds all paycodes for worked time such as Regular, Commissions, Overtime:

       Click Tap Create .

       Total Worked

       Parameter Name	(Required) Enter Total Worked.
       Description	(Optional)
       Template Parameter	(Required) Select Total Worked.
       Parameter Type	(Required) Select Text.
       Default Value	(Optional) Enter Total Worked.
       User Prompted	If the value does not need to be changed when the integration runs, select No.

       Click Tap Save.

       (Required) Specify the combined paycode that holds all paycodes for commissions:

       Click Tap Create .

       Total Commissions

       Parameter Name	(Required) Enter Total Commissions.
       Description	(Optional)
       Template Parameter	(Required) Select Total Commissions.
       Parameter Type	(Required) Select Text.
       Default Value	(Optional) Enter Total Commissions
       User Prompted	If the value does not need to be changed when the integration runs, select No.

       Click Tap Save.

       (Required) Specify the combined paycode that holds all overtime paycodes to exempt when all conditions for FLSA Section 7(i) are met:

       Click Tap Create .

       Total Overtime

       Parameter Name	(Required) Enter Total Overtime.
       Description	(Optional)
       Template Parameter	(Required) Select Total Overtime.
       Parameter Type	(Required) Select Text.
       Default Value	(Optional) Enter Total Overtime.
       User Prompted	If the value does not need to be changed when the integration runs, select No.

       Click Tap Save.

       (Optional) Specify the average multiplier rate for the calculation of the average rate of pay for overtime hours:

       Click Tap Create .

       Average Rate of Pay Multiplier

       Parameter Name	(Required) Enter Average Rate of Pay Multiplier.
       Description	(Optional)
       Template Parameter	(Required) Select Average Rate of Pay Multiplier.
       Parameter Type	(Required) Select Text.
       Default Value	(Optional) Enter 1.5.
       User Prompted	If the value does not need to be changed when the integration runs, select No.

       Click Tap Save.

       (Optional) Specify the percentage for the calculation of the earned commissions:

       Click Tap Create .

       Earnings Percentage

       Parameter Name	(Required) Enter Earnings Percentage
       Description	(Optional)
       Template Parameter	(Required) Select Earnings Percentage.
       Parameter Type	(Required) Select Text.
       Default Value	(Optional) Enter 50.
       User Prompted	If the value does not need to be changed when the integration runs, select No.

       Click Tap Save.

       (Required) Specify the comment that identifies the paycode for the override exemption:

       Click Tap Create .

       Comment

       Parameter Name	(Required) Enter Comment.
       Description	(Optional)
       Template Parameter	(Required) Select Comment.
       Parameter Type	(Required) Select Text.
       Default Value	(Optional) Enter Adjustment by FLSA 7i Integration.
       User Prompted	If the value does not need to be changed when the integration runs, select No.

       Click Tap Save.

       (Optional) Specify the note that adds details to the comment about the amounts for the override exemption:

       Click Tap Create .

       Comment Note

       Parameter Name	(Required) Enter Comment Note.
       Description	(Optional)
       Template Parameter	(Required) Select Comment Note.
       Parameter Type	(Required) Select Text.
       Default Value	(Optional) Enter Reference Period: #referenceperiod#||Total Earnings: #earnings#||Commissions Earned: #commissions#||State Minimum Wage Reference: #staterate#||Previous Pay Period Average Rate of Pay: #actualrate#.
       User Prompted	If the value does not need to be changed when the integration runs, select No.

       Click Tap Save.

       (Optional) Specify the minimum time that is required in the Timecard for the Total Worked (hours) paycode to be eligible for the overtime exemption:

       Click Tap Create .

       Total Worked Threshold

       Parameter Name	(Required) Enter Total Worked Threshold.
       Description	(Optional)
       Template Parameter	(Required) Select Total Worked Threshold.
       Parameter Type	(Required) Select Text.
       Default Value	(Optional) Enter 00:01 (1 minute) or another time in hh:mm format.
       User Prompted	If the value does not need to be changed when the integration runs, select No.

       Click Tap Save.

       (Required) Specify a suffix for values of override work rules:

       Click Tap Create .

       Override Workrule Suffix

       Parameter Name	(Required) Enter Override Workrule Suffix.
       Description	(Optional)
       Template Parameter	(Required) Select Override Workrule Suffix.
       Parameter Type	(Required) Select Text.
       Default Value	(Optional) Enter _OTExempt. If you enter more than one suffix, separate each by a comma (,) but no spaces.
       User Prompted	If the value does not need to be changed when the integration runs, select No.

       Click Tap Save.

       Specify whether to process data for signed-off time periods:

       Click Tap Create .

       Process Signed-Off Period

       Parameter Name	(Required) Enter Process Signed-Off Period.
       Description	(Optional)
       Template Parameter	(Required) Select Process Signed-Off Period.
       Parameter Type	(Required) Select Boolean.
       Default Value	(Optional) Enter false.
       User Prompted	If the value does not need to be changed when the integration runs, select No.

       Click Tap Save.

       (Optional) Specify how long to wait to run the integration again for employees whose override work rules during the previous pay period were rolled back:

       Click Tap Create .

       Totalization Wait Time

       Parameter Name	(Required) Enter Totalization Wait Time.
       Description	(Optional)
       Template Parameter	(Required) Select Totalization Wait Time.
       Parameter Type	(Required) Select Text.
       Default Value	(Optional) Enter 600 seconds.
       User Prompted	If the value does not need to be changed when the integration runs, select No.

       Click Tap Save.

       (Optional) Specify the maximum number of times to run the integration again when employee records were not totalized:

       Click Tap Create .

       Totalization Retry Count

       Parameter Name	(Required) Enter Totalization Retry Count.
       Description	(Optional)
       Template Parameter	(Required) Select Totalization Retry Count.
       Parameter Type	(Required) Select Text.
       Default Value	(Optional) Enter 5.
       User Prompted	If the value does not need to be changed when the integration runs, select No.

       Click Tap Save.

13. Click Tap Save.
14. Make sure that the generic data access profiles (GDAP) allow access by the people who need to run the installed integrations. Select Administration > Application Setup > Integrations Setup > Access Profiles; see Configure Access to Integrations.

Run integrations to test that the configuration is set up correctly.

Run the integration

1. Select the integration:
   1. Select Main Menu  > Maintenance > Integrations. 
   2. Click Tap Run an Integration . 
   3. Select the FLSA7iOvertimeExemption_v1 integration from the list. Click Tap Select. 
   4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.
2. Set parameters as follows:
   • Hyperfind: Select a hyperfind query of employees.
   • Individual Employee ID: To process data for only a limited group of employees, enter the person numbers, as defined in the source system, each separated by a comma (,) but no spaces.

     Example: For 3 employees: 13997,15556,20012

3. Select the following:

   • Run Integration: If this is the first time this integration is being run.
   • Re-Run: If this integration has been run before, and the status is not In-Progress, you can run the integration again without entering the parameter values again. Click Tap Yes to continue, or No to not run the integration and to return to the parameter settings.

4. Wait for the confirmation that the integration completed or failed. Close the panel.
5. Click Tap Refresh . 
6. To see details, select the integration run. Select Run Summary.

Check the results

Status indicators

•  In-Progress: The run of this integration has not yet completed.
•  Completed: The integration ran successfully without errors.
•  Scheduled: This integration is scheduled to run later or repeatedly.
• (Grayed out) Scheduled but Deleted: This integration is scheduled to run, but the integration template has been deleted. When it runs, it will generate an error. To prevent this error, delete the scheduled integration run.
•  Completed with Errors: The integration ran successfully, but one or more records have errors. The integration run is treated as failed. If Abort on Failure is configured in an integration set, the integration set stops.
•  Failed: The integration run has errors or could not run.
• To troubleshoot and resolve errors, do the following:

  Check the Run Summary for details.

  • To troubleshoot all types of errors, or if the Run Summary shows a large number of errors, click tap Go to Additional Details (if available), or click tap the Source File to open and examine the input source file.
  • (Only for import integrations) To troubleshoot and resubmit integrations that have transactional or data errors, click tap Go to Transaction Assistant.

To check the results in more detail, do the following:

1. To see detailed results, click tap the tile for the integration run.
2. Click Tap Run Summary to see the results of the integration run.

   Example Run Summary details

   Note: The available details vary by integration and configuration.

   • Integration Run Name: Name of this run of the integration.
   • Process Name: Name of any integration set that includes this integration.
   • Integration Name: Name of the installed integration.
   • Integration Reference ID: Unique identifier for this integration run (to help in troubleshooting errors).
   • User: The person or user account that ran the integration.
   • Integration Type: Import, Export, or None
   • Start Date: Date and time when the integration run started.
   • End Date: Date and time when the integration run finished.
   • Status: In-Progress, Completed, Completed with Errors, or Failed.
   • Records Processed: Number of records that were processed.
   • Records Created: Number of records that were created.
   • Errors: Number of records that failed.
   • Source Files, Output File, and Error Files: For file-based import integrations, use Manage SFTP to access the source and output files on the inbound (source) and outbound (destination) SFTP folders. See the Manage SFTP topic.
3. Log in to the destination system and make sure that the data has been correctly updated.