Using C4C Health Check
When the configuration of the C4C Health Check has been done you can initiate the C4C Health Check for either the C4C-App Connection or per External Reservation Unit.
Given the nature of the C4C Health Check we suggest that you perform the C4C Health Check per External Reservation Unit unless the C4C-App Connection only has a few External Reservation Units linked to it.
Performing a cross-check for a C4C-App Connection / External Reservation Unit
Procedure
1. Open a Web browser, navigate to Planon and log in.
2. Go to the TSI - C4C Processing.
3. Select the C4C-App Connection / External Reservation Unit for which you want to perform the health check.
4. Click the Perform Health Check action and confirm that the background action will be started.
 | It may take a moment for the health check to complete. This depends on the number of Events and Reservations that are found for the provided period. |
Checking for discrepancies
After performing the Health Check, the discrepancies can be inspected using the TSI - C4C Health Check. The TSI consists of three levels:
• Tasks: C4C Health Check Tasks are linked to a specific C4C-App connection and provide an overview of the External Reservation Units that have been analyzed. For each unit, the task displays the number of discrepancies found per discrepancy type within the selected period.
• Resources: The C4C Health Check Resource is linked to a specific External Reservation Unit and provides a summary of the number of discrepancies identified per discrepancy type for the selected period.
• Items: C4C Health Check Items represent discrepancies identified for an External Reservation Unit during a health check. The following table outlines the various types of discrepancies, when they occur, and the corresponding repair actions that will be taken.
Discrepancy | Occurs | Repair action |
|---|---|---|
Calendar Item data not in-sync | The Reservation has its origin within Planon and there exists a link with an Event in the reservation management system and the data of the Event is not in-sync with the Reservation. | A synchronization flow to update the Calendar Item will be triggered. |
Calendar Item missing | The Reservation has its origin within Planon and there exists no link with an Event in the reservation management system. | The repair action will remove any existing External Reservation for the Reservation and triggers a synchronization flow to create the Calendar Item. |
Calendar Item obsolete | An Event exists in the reservation management system for which the origin is Planon (e.g. transition time, compound-ghost or multi-tenant copy) for which no link is present in Planon. | The related C4C-App will be asked to delete the Event. |
Reservation data not in-sync | The Reservation has its origin outside Planon and there exists a link with an Event in the reservation management system and the data of the Reservation is not in-sync with the Event. | The C4C-App will be asked to update the Reservation. |
Reservation missing | An Event (not originated from Planon) has no link with a Reservation in Planon. | The repair action will remove any existing External Reservation for the Event and the C4C-App will be asked to create the Reservation. |
Reservation obsolete | A Reservation exists for which the origin is outside Planon for no link exists with an Event in the reservation management system. | The C4C-App will be asked to cancel the Reservation. |
Running the repair action for the C4C Health Check Items
Before executing the repair (Clean-up) action, you must manually set the status of the Task and its associated Resource(s) to PREPARED. Once prepared, the repair can be run at three levels:
• Per Task
• Per Resource
• Per Item
After the repair is executed, the results can be reviewed on the level of the C4C Health Check Items.
The status of the Task or Resource provides an indication of the outcome—whether the repair was successful or completed with errors. In the event of a failure, the affected Health Check Items will display a failure reason. These reasons can help identify underlying issues, such as a missing External Account for an Event organizer or overlapping reservations.
If necessary, the repair action can be aborted for a Task or a specific Resource using the corresponding action. Aborting on a Resource level will stop the repair for that Resource and continue with the next one (if any) within the same Task. Aborting a Task will stop the process entirely.