Tracking, monitoring and collaborating on Events and results

The Portal component presents the migration results and events. As a web application, it is easily reachable by a wider audience, which may include users from the businesses involved in the migration. The aggregations in the Portal component provide a comprehensive understanding of the overall quality of the migration iteration including baseline comparisons that reveal trends since the last iteration.

In addition, the Portal shows detailed information for each migrated Business Object providing rich support for the users to analyze the results and seek explanations for any issues. 

Finally, the Portal provides collaboration functionality enabling the users to keep track of the state of events (new, fixed, accepted, recurring etc.), to comment on events and to appoint some user to be responsible for resolving the event.

For any type of Business Object, the application presents:

• how many Business Objects of this type that has been migrated successfully and how many were rejected during the migration
• an aggregation of the events that occurred for this type of Business Object

The application enables the user to search or drill down to any specific business object to view: 

• the events that occurred for this Business Object
• links to any related Business Objects (ancestors and/or descendants)
• the data that were produced for each step in the migration process:
  1. the data extracted from the source system
  2. the intermediate result produced by the Export Engine
  3. the result produced by the Target Engine

Translation Tables

A special section of the Portal application showed the Value Sets marked in the mapping as Translation Tables. This enables users in the migration project (for instance users from the involved businesses) to provide the content for these Value Sets, normally to provide translations of terms and values in the source system to the target system.

An option is provided for functionality external to hopp to read these translation tables and to write back a validation state (ok or faulty) combined with a validation message. This is useful to ensure that values manually provided by users actually are correct in terms of the receiving target system.