Looking at the Events panel, you have a list of all Events fired in the lifetime of the project. The message for each Event is presented with the space holders for parameters, the actual parameter values have not been merged into the message.
Here's the Event list in the Workshop track with the Event I0019 highlighted. The Event complains that in 27.838 instances an InterestType is unknown. This affects 22.688 Accounts
At this top level, the parameter values in the event message are represented by the place holder P0
Intermediate Event aggregation
By clicking the Business Object name Account for the Event I0019 you go to the intermediate Event list displaying the actual parameter values.
Even though number of occurrences a quite daunting, the intermediate list shows that the problem is in fact limited to a just few missing InterestTypes.
Item List
Clicking a line in the Intermediate list takes you to the list of items that fired the Event with this value for the message placeholders. This is also the list you will get from the Items menu item
The columns in Item list are:
| Item Id | The internal Id of the Business Object instance in the migration database. Click to proceed to the detail view The migration result for each item is
| ||||||||
| Source Key | The key identifying the item in the Source System. This is the given by the Discriminator defined on the Business Object in the Source Map (here the values for BankId, ClientId and AccountNumber) | ||||||||
| Migration Key | The key in the migration. This is the value of the Target Interface Fields that were marked as Key in the Studio Target Map (here BankId and AccountNumber) |
Detail View
Clicking the Item Id in the Item list proceeds to the detail view. Here all information for one specific Business Object instance is displayed in a consolidated view
| 1 | The same Key information as is visible in the list |
| 2 | Information of the jobs in the Director that ran the Export and Import of this item |
| 3 | The commit ids of the Source- and Target Maps tells you on which basis the item was processed. You can locate these commits in Studio to see the exact state of the maps that were used. A yellow warning means that the user had one or more items in Studio checked out locally, when the engine was generated |
| 4 | Any parent items on which this item is dependent as defined by relationships in the Target Map |
| 5 | Any child items which depend on this item as defined by relationships in the Target Map |
| 6 | All the Events that were fired when this item was migrated |
| 7 | Tabs to show the actual item data that were processed for this item, see below |
Item Data
Use the tabs to get to a consolidated view of relevant data for this specific item.
Here the Portal presents you with all the data that were in use for the entire hierarchy defined in Studio for this Business Object.
This view is data lineage taken to a whole new level and indeed something we are very proud of.
The screenshots above shows the data hierarchies for an Account Business object.
Navigate to a Card item in the Portal and you will easily recognize the hierarchies you have been working on in the Source- and Target Maps.
| Source | The data that was extracted from the Staging database to serve as the foundation for the migration of the item. |
| Interface | The data that was produced by the Source Engine and sent on to the Target Enginethrough the Business Object interface |
| Target | The result produced by the Target Engine, ready for delivery to the Target System(s) |
What happened here?
Hopefully this exercise gave you an impression of how you can drill down in the Event aggregation to end up on a complete view of a single Business Object instance. Along the way the Portal gave you an intermediary list, where parameter values have been merged into the Event messages, giving a nice overview of the discrete values in play.
Finally the Detail View exposes the unique advantages of the Business Object approach of migFx. In the same place you see a consolidated view of one Business Object instance. Right down to all the exact data that flowed through the migration for this one Business Object and the links to related Business Objects.