Chile Audit Reports

Configure Access to Integrations.

• Function Access Profiles (FAP): The Retrieve Hidden Paycode Edits via API access control point must be set to Allowed in the FAP assigned to individuals who run the report. See the Function Access Profiles topic.

• Tip: Shift Labels: Configure shift labels that include a suffix, such as _Daily, _Weekly, or _Monthly. Use these shift labels in schedule templates or the Scheduler when you create employee schedules. The suffix indicates the shift type, and is referenced by the Historical Schedule Report when populating the Type( Tipo) column.

  Examples: 9amTo11pm_Daily, 9amTo6pm_Weekly, 7amTo5pm_Monthly.

• Combined paycodes: Configure combined paycodes for each type of paycode represented in the reports. See the Combined Paycodes topic.

  AbsencePayCode

  ApprovedDaysPayCode

  ApprovedHoursPayCode

  CombinedOvertimePayCode

  FullOvertimePayCode

  HalfOvertimePayCode

  OvertimePayCode

  RestPayCode

  UnauthorizedPayCode

  VacationPayCode

  WorkedHoursPayCode

• Integration List Parameters: Create integration list parameters that identify the report output types and audit reports. See the Configure Integration List Parameters topic.

  Name: ChileAuditReports_iPack_v3_ReportOutputFormat

  Description: Output formats applicable to the Chile Audit Reports.

  Parameter values: PDF(default), XLSX.

  Name: ChileAuditReports_iPack_v3_ReportList

  Description: Contains a list of all report names from which a selection is made to run a report.

  Parameter values:

  Parameter values

  Name	Value
  Sundays and Holidays Report	Chile-SundaysandHolidaysWorkingReport
  Historical Schedule Report	Chile-HistoricalScheduleReport
  Daily Working Report	Chile-DailyWorkingHoursReport
  Assistance Report	Chile-AssistanceReport
  Overtime Hours Agreement	Chile-OvertimeHoursAgreement
  Timecard Report	Chile-TimecardReport

  Caution: Parameter values configured in the ChileAuditReports_iPack_v3_ReportList integration list parameter must match the example.

• Extensions Tables: Configure the Chile Timecard Report and Chile Audit Report extension tables. See the Extension Tables topic.

  Enter the following in the Commands for execution field for each extension table definition:

  CREATE TABLE chiletimecardreport
  (
  ApplyDate VARCHAR(255),
  TypeOfEntry VARCHAR(255),
  EmployeeNumber VARCHAR(255),
  EmployeeName VARCHAR(255),
  ScheduleStartTime VARCHAR(255),
  ScheduleEndTime VARCHAR(255),
  Exceptions VARCHAR(255),
  InPunch VARCHAR(255),
  AmountOfTimeLateIn VARCHAR(255),
  OutPunch VARCHAR(255),
  AmountOfTimeEarlyOut VARCHAR(255),
  ApprovedHours VARCHAR(255),
  ApprovedDays VARCHAR(255),
  Vacation VARCHAR(255),
  DailyTotals VARCHAR(255),
  UnauthorizedHours VARCHAR(255),
  OvertimePayCode VARCHAR(max),
  OvertimeHours VARCHAR(255),
  UniqueCode VARCHAR(255),
  ExecutionDate VARCHAR(255),
  SumDailyTotals VARCHAR(255),
  SumApprovedHours VARCHAR(255),
  SumApprovedDays VARCHAR(255),
  SumVacation VARCHAR(255),
  SumUnAuth VARCHAR(255),
  SumOvertime VARCHAR(255),
  SumLateIn VARCHAR(255),
  SumLateOut VARCHAR(255)
  ;

  CREATE TABLE chileAuditReport_v2
  (
  EmployeeID VARCHAR(255),
  EmployeeNumber VARCHAR(255),
  CostCenter VARCHAR(255),
  Location VARCHAR(255),
  LaborType VARCHAR(255),
  AdditonalInfo VARCHAR(255),
  ManagerNmae VARCHAR(255),
  FullName VARCHAR(255),
  HSAttendance VARCHAR(255),
  HSAbsence VARCHAR(255),
  HSComments VARCHAR(max),
  HSWorked VARCHAR(255),
  HSJustify VARCHAR(255),
  HSLegend varchar(255),
  HSMonth VARCHAR(255),
  HSMonthWiseData VARCHAR(255),
  HSTotalPeriodData VARCHAR(255),
  HSDayofweek VARCHAR(255),
  HSDate VARCHAR(255),
  HSchOriginalShift VARCHAR(255),
  HSchTypeofShift VARCHAR(255),
  HSchModifiedShift VARCHAR(255),
  HSchChangedby VARCHAR(255),
  HSchComments VARCHAR(max),
  HSchLegend VARCHAR(255),
  HSchShift VARCHAR(255),
  HSchDayOfWeek VARCHAR(255),
  HSchDate VARCHAR(255),
  DWHShift VARCHAR(255),
  DWHPunchout VARCHAR(255),
  DWHScheduledbreak VARCHAR(255),
  DWHPunchoutforbreak VARCHAR(255),
  DWHPunchinafterbreak VARCHAR(255),
  DWHLatepunchin VARCHAR(255),
  DWHEarlypunchout VARCHAR(255),
  DWHEarlypunchoutbreak VARCHAR(255),
  DWHLatepunchinbreak VARCHAR(255),
  DWHOvertimehours VARCHAR(255),
  DWHComments VARCHAR(max),
  DWHWeeklyTotalOvertimehours VARCHAR(255),
  DWHWeeklyTotalLateIn VARCHAR(255),
  DWHWeeklyTotalEarlyOut VARCHAR(255),
  DWHWeeklyTotalEarlyPunchOutBreak VARCHAR(255),
  DWHWeeklyTotalLatePunchInBreak VARCHAR(255),
  DWHMonthlyTotalOvertimehours VARCHAR(255),
  DWHMonthlyTotalLateIn VARCHAR(255),
  DWHMonthlyTotalEarlyOut VARCHAR(255),
  DWHMonthlyTotalEarlyPunchOutBreak VARCHAR(255),
  DWHMonthlyTotalLatePunchInBreak VARCHAR(255),
  DWHMonth VARCHAR(255),
  DWHWeekNumber VARCHAR(255),
  DWHDayofWeek VARCHAR(255),
  DWHDate VARCHAR(255),
  ASAttendance VARCHAR(255),
  ASAbsence VARCHAR(255),
  ASComments VARCHAR(max),
  ASDayofWeek VARCHAR(255),
  ASDate VARCHAR(255),
  OHAFrom VARCHAR(255),
  OHAUntil VARCHAR(255),
  OHAOvertimeType1 VARCHAR(255),
  OHAOvertimeType2 VARCHAR(255),
  reportID VARCHAR(255),
  UniqueCode VARCHAR(255),
  ExecutionDate VARCHAR(255),
  month_number VARCHAR(255),
  ottabledescone VARCHAR(max),
  ottabledesctwo VARCHAR(max),
  ottabledescthree VARCHAR(max),
  ottabledescfour VARCHAR(max)
  ;

Get the URL, User, and Password for the APIGatewayServer.

1. Customize the report labels.

   1. Unzip the shared .zip file.

   2. Navigate to the properties folder, and then open the properties file.

   3. Provide values for the report strings.

   4. Save the changes, and then add the updated file to the .zip file.

   5. Repeat these steps for each Chile Audit Report.

      Chile Sundays and Holidays Working Report

      Chile Sundays and Holidays Working Report - report labels

      .zip file	Chile-SundaysandHolidaysReport.zip
      Properties folder	Report1SundaysandHolidaysReport_v2 -> Properties
      Properties file	report_com.kronos.report.data.design.Report1SundaysandHolidaysReport_v2_strings
      Report strings	Report Title Name of Employee RUT Worker Type Day Date Absence Attendance Comments Report Footer Page number Printed by Hyperfind Timestamp Total Period From and To

      Chile Historical Schedule Report

      Chile Historical Schedule Report - report labels

      .zip file	Chile-HistoricalScheduleReportEmployee.zip
      Properties folder	Report2HistoricalScheduleReportEmployee_v2 -> Properties
      Properties file	report_com.kronos.report.data.design.Report2HistoricalScheduleReportEmployee_v2_strings
      Report strings	Report Title Name of Employee RUT Original shift: shift time Type of shift Change requested by Day of the Week Date Modified shift: shift time Comments Report Footer Page number Printed by Hyperfind Timestamp Total Period From and To

      Chile Daily Working Hours Report

      Chile Daily Working Hours Report - report labels

      .zip file	Chile-DailyWorkingHoursReport.zip
      Properties folder	Report3DailyWorkingHoursReport_v2-> Properties
      Properties file	report_com.kronos.report.data.design.Report3DailyWorkingHoursReport_v2_strings
      Report strings	Report Title Name of Employee RUT Schedule Shift Punch-in Punch-out Day of the Week Date Scheduled break Punch out for break Punch-in after break Late punch-in Early punch-out Early punch-out break Late punch-in break Overtime Comments Weekly Total Total Report Report Footer Page number Printed by Hyperfind Timestamp Total Period From and To

      Chile Assistance Report

      Chile Assistance Report - report labels

      .zip file	Chile-AssistanceReport.zip
      Properties folder	Report4AssistanceReport_v2-> Properties
      Properties file	report_com.kronos.report.data.design.Report4AssistanceReport_v2_strings
      Report strings	Report Title Name of Employee RUT Worker Name Day of the Week Calendar date Absence Attendance Comments Report Footer Page number Printed by Hyperfind Timestamp Total Period From and To

      Chile Overtime Hours Agreement Report

      Overtime Hours Agreement Report - report labels

      .zip file	Chile-OvertimeHoursAgreementReport.zip
      Properties folder	OvertimeHoursAgreementReport_v2 -> Properties
      Properties file	report_com.kronos.report.data.design.OvertimeHoursAgreementReport_v2_strings
      Report strings	Report Title Name of Employee RUT Cost Center Location Manager Name Day of the Week Date Job (Cargo) From Until Column for Overtime type1 Column for Overtime type2 Report Footer Page number Printed by Hyperfind Timestamp Total Period From and To

      Chile Timecard Report

      Chile Timecard Report - report labels

      .zip file	Chile-TimecardReport.zip
      Properties folder	ChileTimecardReport_v1 -> Properties
      Properties file	report_com.kronos.report.data.design.ChileTimecardReport_v1_strings.properties
      Report strings	Company Name Address Line1 Address Line2 Address Line3 Report Title Report Footer

2. Localize the report strings.

   1. Unzip the shared file.

   2. Create a new properties file that adheres to the following naming convention:

      report_com.kronos.report.data.design.<reportName>_v<versionNumber>_strings_<languageCode>_<countryCode>.properties

      Example: report_com.kronos.report.data.design.ChileTimecardReport_v1_strings_fr_FR.properties

   3. Copy each key and value data pair from the strings properties file, and then paste the content into the new file.

   4. Replace all values after the " =" with required locale data, and then save the properties file.

   5. Zip the file after completing and saving all localization.

3. Repeat these steps for each Chile Audit Report.

   Chile Sundays and Holidays Working Report

   Chile Sundays and Holidays Working Report - localized report strings

   .zip file	Chile-SundaysandHolidaysReport.zip
   Properties folder	Report1SundaysandHolidaysReport_v2 -> Properties
   Localized properties file	report_com.kronos.report.data.design.Report1SundaysandHolidaysReport_v2_strings_<languageCode>_<countryCode>

   Chile Historical Schedule Report

   Chile Historical Schedule Report - localized report strings

   .zip file	Chile-HistoricalScheduleReportEmployee.zip
   Properties folder	Report2HistoricalScheduleReportEmployee_v2 -> Properties
   Localized properties file	report_com.kronos.report.data.design. Report2HistoricalScheduleReportEmployee_v2_strings_<languageCode>_<countryCode>

   Chile Daily Working Hours Report

   Daily Working Hours Chile - localized report strings

   .zip file	Chile-DailyWorkingHoursReport.zip
   Properties folder	Report3DailyWorkingHoursReport_v2-> Properties
   Localized properties file	report_com.kronos.report.data.design.ChileTimecardReport_v1_strings_<languageCode>_<countryCode>

   Chile Assistance Report

   Chile Assistance Report - localized report strings

   .zip file	Chile-AssistanceReport.zip
   Properties folder	Report4AssistanceReport_v2-> Properties
   Localized properties file	report_com.kronos.report.data.design. Report4AssistanceReport_v2_strings_<languageCode>_<countryCode>

   Chile Overtime Hours Agreement Report

   Chile Overtime Hours Agreement Report - localized report strings

   .zip file	Chile-OvertimeHoursAgreementReport.zip
   Properties folder	OvertimeHoursAgreementReport_v2 -> Properties
   Localized properties file	report_com.kronos.report.data.design. OvertimeHoursAgreementReport_v2_strings_<languageCode>_<countryCode>

   Chile Timecard Report

   Chile Timecard Report - localized report strings

   .zip file	ChileTimecardReport.zip
   Properties folder	ChileTimecardReport_v1 -> Properties
   Localized properties file	report_com.kronos.report.data.design.ChileTimecardReport_v1_strings_<languageCode>_<countryCode>

   Note:

   Refer to the table for appropriate character sequences to use in the properties file.

   Character sequence

   Properties file character sequence

   Character	Character Sequence
   Space	\
   Colon	\:
   Semicolon	\;
   Blank	\t

   Note:

   • If you plan to test the report in your non-production (NPR) environment before implementation in your production (PRD) environment, you must complete each of the following UKG Pro WFM report configuration steps in both NPR and PRD environments.

   • Manage Read Only Reports must be enabled on the tenant in the NPR environment.

1. Log in to the appropriate tenant.

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

3. Select the Source tenant where the RDO configuration 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.

9. Repeat these steps for each Chile Audit Report.

   • SDM_SundaysHolidaysWorkingReport_RDO.zip

   • SDM_HistoricalScheduleReport_RDO.zip

   • SDM_DailyWorkHours_RDO.zip

   • SDM_AssistanceReport_RDO.zip

   • SDM_OvertimeAgreementReport_RDO.zip

   • SDM_ChileTimecardReport_RDO.zip

1. Go to Main Menu > Administration > Application Setup > Common Setup > Manage Read-Only Report.

2. Click Tap Create, and then select Choose File.

3. Select a Chile Audit Report .zip file, and then click tap Upload.

4. Click Tap Save after the upload completes.

5. Go to Main Menu > Administration > Application Setup > Common Setup > Unpublished Reports.

6. Select the Chile Audit Report, and then click tap Publish.

7. Configure the report-specific fields:

   Report Name<Enter the name as it is configured in the integration list parameter, ChileAuditReports_iPack_v3_ReportList.> Default Output Type: pdf Output formats Category: Custom Reports

   Note: The value entered in Report Name must match the report name configured in the Report List integration control parameter.

8. Click Tap Save to publish the report. See the Unpublished Reports topic.

Configure the branding logo that appears in the report header. After choosing the file, select Use this logo for all reports regardless of the active theme. Report logos are displayed on a white background. See the Themes topic.

1. Login to UKG Pro WFM as a Support User.

2. Go to Main Menu > Administration > Application Setup > Common Setup > Manage Read-Only Report.

3. Select the Chile Audit Report file, and then click tap Review.

4. Select Approve, and then click tap Apply. This action changes the Approval Status from Pending to Approved.

5. Repeat these steps for each Chile Audit Report.

   • Chile-SundaysAndHolidaysWorkingReport

   • Chile-HistoricalScheduleReport

   • Chile-DailyWorkHoursReport

   • Chile-AssistanceReport

   • Chile-OvertimeAgreementReport

   • Chile-TimecardReport

Add each Chile Audit Report to the Report Data Access Profile assigned to individuals who run the report. See the Report Data Access Profiles topic.

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. Make sure that the Account is correct. If not, select the right account.

3. Select the Deploy tab > Integration Packs.
4. From the list in the left column, search for and select the Pro WFM Chile Audit Reports Extension integration.
   Note: If the integration does not display, select Browse Integration Packs to search for and select the iPack.

5. Click Tap Install.

6. From Unattached Environments, select the environment in which to deploy the integration process for the selected integration. Click Tap the double-left arrows button
   
   .

1. Select the environment
   1. Select the Manage tab > Atom Management.
   2. Select your environment.
2. 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: Chile Audit Reports > ChileAuditReports_iPack_v3.

1. Select Connection Settings.

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

   Connection Settings

   Connection Settings for the integration

   Setting	Required	Actions
   ChileAuditReports_iPack_v3_APIGatewayServer	Required	To change the default API gateway server: Clear Use Default. Enter the URL to the server. Example: <tenantURL>/api
   ChileAuditReports_iPack_v3_DatabaseServer	Required	The database server setting defines the connection to the file that contains the records. To change the default server parameters: For each field, clear Use Default. Enter the following values: In User, enter the username for the server. In Password, select <Encrypted>. Enter the password for the server. Click Tap Apply. Enter the Class Name. Enter the Connection URL for the database server.
   ChileAuditReports_iPack_v3_Locale_CRT	Required	Enable Override.

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 ChileAuditReports_iPack_v3_CRTConfig to set process properties that must be configured before the integration can run. This main process starts the integration process and handles errors.

   Process properties

   Process properties

   Process property name	Column header value
   ChileAuditReports_iPack_v3_Locale_CRT	Parameter Name,Locale Policy,Value,Description

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 ChileAuditReports_iPack_v3 table.

3. Select Override, which allows you to:

   • Download the table when you run the integration
   • Edit the table cells in Extensions
4. When you finish, click tap OK.

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

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.

1. In Integration Template, select ChileAuditReports_iPack_v3.
2. Click Tap Assign .
3. In Integration Parameters, you can override default settings. Click Tap Create.
4. Complete the configuration for each integration parameter value.

5. Click Tap Save.

   Repeat this step for each integration parameter that supports the Chile Audit Reports process.

   Integration Parameters

   Integration Parameters

   Parameter name	Description / User prompt / Mandatory	Template parameter	Parameter type
   Locations & Hyperfind	The default Hyperfind or Location query that contains the employees for whom the integration is run. User prompt = Yes Mandatory = Yes	HyperfindAndLocationSelector	Hyperfind
   TimePeriod	The date range or symbolic time period for which the report is run. Supported values include: 0= Previous pay period 1= Current pay period 2= Next pay period 3= Previous schedule period 4= Current schedule period 5= Next schedule period 6= Week to date 7= Last week 8= Yesterday 10= Range of relative dates 11= Specific date 12= Relative specific date 13= Today User prompt = Yes Mandatory = Yes	TimePeriod	Time Period
   Display Break	Determines whether break-related columns are displayed in the Daily Work Hours Report. true(default): break-related columns are displayed. false: break-related columns are not displayed. User prompt = No Mandatory = Yes	Display Break	Boolean
   CustomWorkerType	Defines the value that represents CL-Jornada Excepcional in the Additional Details section of People Information. User prompt = No Mandatory = Yes	CustomWorkerType	Text
   Report - Output Format	Identifies the integration list parameter that defines the audit report output formats. User prompt = Yes Mandatory = Yes	ReportOutputFormat	Dropdown
   Locale	Determines the locale of the output file. User prompt = No Mandatory = No	Locale	Text
   Pay Code - Approved Days Pay Code	The combined paycode that contains approved days. User prompt = No Mandatory = Yes	ApprovedDaysPayCode	Text
   Pay Code - Approved Hours Pay Code	The combined paycode that contains approved hours. User prompt = No Mandatory = Yes	ApprovedHoursPayCode	Text
   Pay Code - Overtime Pay Code	Semicolon-separated (;) list of overtime hours paycodes. User prompt = No Mandatory = Yes	OvertimePayCode	Text
   Pay Code - Punch Receipt Pay Code	Identifies the paycode to which an attached comment stores the punch time in hh:mm:ss format. User prompt = No Mandatory = No Note: If the organization also uses the Chile Punch Receipt extension, this value must match the PayCode parameter value in the Chile Punch Receipt Parameters decision table.	PunchPayCode	Text
   Pay Code - Rest Pay Code	The combined paycode that contains rest days. User prompt = No Mandatory = Yes	RestPayCode	Text
   Paycode - Overtime Pay Code Combined	The combined paycode that contains all overtime hours. User prompt = No Mandatory = Yes	CombinedOvertimePayCode	Text
   Paycode - Half Overtime Pay Code	The combined paycode that contains 50% overtime hours. User prompt = No Mandatory = Yes	HalfOvertimePayCode	Text
   Paycode - Full Overtime Pay Code	The combined paycode that contains 100% overtime hours. User prompt = No Mandatory = Yes	FullOvertimePayCode	Text
   Paycode - Absence Pay Code	Semicolon-separated list of absence paycodes. User prompt = No Mandatory = Yes	AbsencePayCode	Text
   Paycode - Worked Hours Pay Code	The combined paycode that contains all worked hours. User prompt = No Mandatory = Yes	WorkedHoursPayCode	Text
   Pay Code - Unauthorized Pay Code	The combined paycode that contains unauthorized hours. User prompt = No Mandatory = Yes	UnauthorizedPayCode	Text
   Pay Code - Vacation Pay Code	The combined paycode that contains vacation days. User prompt = No Mandatory = Yes	VacationDaysPayCode	Text
   Org Path Levels	Determines the number of business structure levels to display. Default = 2 User prompt = No Mandatory = Yes Note: Org Path Levels do not support text, negative or decimal values.	OrgPathLevelsToDisplay	Number
   Report List	Identifies the integration list parameter that defines the audit report list. Default = ChileAuditReports_iPack_v3_ReportList User prompt = Yes Mandatory = Yes	ReportList	List
   RUT	Defines the value that represents RUT in the Additional Details section of the People Information. Default = RUT User prompt = No Mandatory = Yes	CustomDataType	Text
   Employee Number	A comma-separated list of specific employees for whom the integration is run. When no value is entered, the integration defaults to the Locations & Hyperfind parameter. To process the integration for only a limited group of employees, enter the person numbers as defined in the source system, each separated by a comma (,) but not spaces. User prompt = Yes Mandatory = Yes	Employee IDs	Text

See Configure Access to Integrations .

1. Select the integration:
   1. Select Main Menu Maintenance > Integrations.
   2. Click Tap Run an Integration .
   3. Select the ChileAuditReports_iPack_v3 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 system assigns a default name, which ends with a date and time stamp.
2. Set parameters as follows:
   • Report List: Select a report.
   • Hyperfind: Select a Hyperfind query of employees.
   • 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.

     For 3 employees: 13997,15556,20012

   • Time Period: Select a date range or symbolic period.
   • Report Output Format: Select PDF.
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.

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:

1. 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 ensure that the data has been correctly updated.