Error Handling
This section provides information about the different ways used to handle errors in the integration and also resubmitting the instances after rectifying the errors.
Error Handling Ways
In this integration, all integration flows are asynchronous. This section describes error handling for asynchronous flows.
Asynchronous Flow Error Handling
Technical Fault
This fault occurs when there is a data mismatch or any Xpath related error. When this error occurs, the flow immediately goes to global fault handler and an optional email to the respective user is sent.
Remote Fault
This fault occurs when the target system is down or not accessible. When this error occurs, the flow immediately goes to global fault handler and an optional email is sent to the respective user.
Business Fault
These faults are application-specific faults that occur when there is a problem with the information being processed in the target application due to invalid data or business error validations.
For processing records in a file
When Oracle Utilities Work and Asset Cloud Service returns HTTP status codes 400 or 500, these are considered business faults by the integration. When these errors occur, the flow will not stop but continue to process the next record and the errors will be stored in a temporary error collection. When the file is done processing an optional email is sent with the list of errors to the respective user.
Summary of Integration Error Handling
Integration Process: Job Synchronization (Craft Sync)
Type of error
Action
Notification Type
Retry
Technical or Remote Fault
Process Stop
Email
Resubmit Error Instance From OIC
Business Fault (WACS returns Status Not 400 or 500)
Process Stop
Email
Resubmit Error Instance From OIC
Business Fault (WACS returns Status 400 or 500)
Continue Process
Collect errors and send errors in Email
Data Fix in Integration - Reprocess Job file
 
Data Fix in WACS - Reprocess Job file
 
Integration Process: Absence Synchronization (Leave Sync)
Type of error
Action
Notification Type
Retry
Technical or Remote Fault
Process Stop
Email
Resubmit Error Instance From OIC
Business Fault (WACS returns Status Not 400 or 500)
Process Stop
Email
Resubmit Error Instance From OIC
Business Fault (WACS returns Status 400 or 500)
Continue Process
Collect errors and send errors in Email
Data Fix in Integration - Reprocess Absence file
 
Data Fix in WACS - Reprocess Absence file
Resubmitting the Error Instances in Oracle Integration Cloud
In this integration, all processes are asynchronous flows so the resubmit option is available in Oracle Integration Cloud if the process ends in a fault.
To resubmit the error instances in Oracle Integration Cloud:
1. Login to Oracle Integration Cloud.
2. Navigate Integrations > Monitoring > Errors.
3. Select the integration to resubmit.
4. Click the Resubmit icon.
Reprocess File
To reprocess the Job or Absence file:
1. Login to Oracle Integration Cloud.
2. Navigate to Integrations > Integrations.
• For Job Sync: Navigate to Oracle Utilities HCM WACS Job Sync integration and click Run.
• For Employee Initial Sync: Navigate to Oracle Utilities HCM WACS Employee Initial Sync integration and click Run.
• For Absence Sync: Navigate to Oracle Utilities HCM WACS Absence Sync integration and click Run.
3. Click Submit Now to display the Schedule Parameters.
4. Enter the LastProcessedDocId of the previous file processed.
Note: The Doc ID of the file process from the process completed email or from the instance you want to rerun is displayed. If it is the only file in Oracle UCM, put 0.
5. Click Submit.