The Tracker provides invaluable support for analyzing and handling the Events that were fired during the migration. The Tracker remembers results and Events from iteration to iteration and provides delta indicators to signal the overall progress of the migration. The workflow functionality supports the sign-off on all the Events, that was fired. By the go-live point, the status on all events to be either that the Event is not fired anymore, or that the user assigned as responsible for the Event has given it a status Accepted


In this and the following exercises you will have a look at the different tabs in the Tracker. Especially, you will see how you can drill down to a single Business Object and see: 


  • All the Events that was fired for this Business Object
  • Links to all Business Objects that this Business Object is depending on
  • Links to all Business Objects dependent on this Business Objects
  • The Source Data that was extracted from the Staging Tables for this Business Object
  • The Export Result for this Business Export
  • The Target Result for this Business Object


Delta indicators

Generally in lists there is a delta indicator next to each count. The delta indicator compares the current count to the number stored in the current baseline. 


The indicators are:



The current count is zero

The current count is equal to baseline (unchanged)

The current count is less than baseline. Green if this is good, for instance if the count of rejected Business Objects has decreased. Red if bad, for instance if the count of Business Objects that were imported successfully has decreased

The current count is greater than baseline. Green if this is good, for instance if the count of Business Objects that were imported successfully has increased. Red if bad, for instance if the count of rejected Business Objects has increased

The current count is new, that is greater than zero but the baseline does not exist or is zero


User Interface depending on User authorization

As mentioned in the last exercise, you can see the All level in the Partition box because you in migFx are authorized as a Migration Team member. Partition users, from the business(es) being migrated, will not have this global authorization and will only be authorized able to see data for their respective Partitions. 


In several places, the Tracker user interface differs depending on whether you are a Team Member or a Partition User. Below, the User Interface is primarily described as you see it as a Team Member.



Differences for Partition Users are described where relevant and marked like this.



Level

A given Event can be processed at two different levels. Either the processing of the Event takes place in the migration team or it is delegated to users in the respective Partitions.


Team
The Event is processed by the migration team
Delegate
The processing of the Event is delegated to users in the respective Partitions.



User State

When editing the details of a given Event, you - or a Partition User if the Level is Delegate - can change the State of the Event to one of these possible States:


State
Description
Comment
None
No State has been set
New Events are 'born' with this State
Resolved
Some action has been taken and this Event should not occur in the next iteration

Regression
The State was set to Resolved, but the Event occurred anyway in the last iteration
This State is set automatically by the Director on Publish
In Progress
The Event is currently under processing

Accepted
It is accepted that this Event occurs and it will not prevent a final sign-off on the migration

Rejected
The Event Level is Delegate, but a Partition User does not accept the delegation

This State is only available to Partition Users


These are the States that can be set manually on an Event. When the Event is shown in the Events list, this State in combination with the baseline comparison is translated to a List State, see below.


Let's go through the tabs one by one. Please make sure you have selected the Workshop - Training Track in the Track Selector drop down.


Result tab

The Results tab shows the statistics for each root Business Object in the latest migration iteration.


As elsewhere, the Partition Box allows you to see the statistics aggregated for the entire migration or for each partition. The list can be exported to an Excel spreadsheet.


The label of each column should make it clear what the column signify. 


Parameters tab

The parameters tab shows the values that were in effect for the Runtime Parameters during the latest iteration. The Runtime Parameters are the Constants from the Studio that were marked as Runtime.




Events tab 

The Events tab shows an aggregated list of Events for the selected Business Object. The aggregated counts reflect your selection in the Partition Box. You must select both a Partition and a Business Object before the list shows anything. 



You will find that this list is extensively used and is the major entry point once you start to analyze specific events. The columns are


Derived
A checkmark in this column means that the Event is derived from (or caused by) another Event. By default derived Events are hidden from the list. However, if the Event occurs even though the causing Event does not occur, the Event will always be shown regardless.

Check the column header to always show derived events.
Level
Indicates if the processing of the Event takes in the migration team or is delegated to users in the respective Partitions.

Team
The Event is processed by the migration team
Delegate
The processing of the Event is delegated to users in the respective Partitions

Count
The number of Events that occurred in the last iteration. The count changes with the selected Partition. Clicking the count drills down in the aggregation for the Event. See following exercises.
ItemsThe number of Items that is affected by the Event. Given that the same Event may be fired more than once for the same Item, the Item count may - but does not have to be - lesser than the Event count.
This column has been added to the Tracker after the screen shots of the Tracker training exercise was taken and is thus missing from the screen shots
State
The state of the Event processing. See below for more about this State.
Event
The Event code from Studio.
Severity
The Severity of the Event.
Team Anchor
The person in the migration team keeping track of the processing of the Event. The exact meaning depends on whether the Level is Team or Delegate:

Team
The Team Anchor is responsible for the Event processing
Delegate
The Team Anchor ensures that the Event is processed by the users in the respective Partitions



For Partition users, this column is labeled User and will show 

  • the Team Anchor if Level is Team
  • the responsible Partition User if level is Delegate.


Area
This is basically the Receiver from Studio. Studio Receivers are Source, Migration and Target. It is however possible to assign labels to translate the receivers into something that may make more sense in the specific migration project. For instance Receiver Target could me labelled with the name of the Target System.
Message
This is the Events message text with spaceholders in the Language chosen under the Settings tab. Clicking the Message takes you to the Event detail, where you can comment, change User State and delegate the Event.
Comments
if there are any Comments on the Event, an image will appear in this column. Hovering over the image will display the comments.


The List State

The State shown in the Events list is not the User State set on the Event, but rather the User State in combination with with the baseline comparison. The translation assists in getting a better view of the actual state of the Event in relation to the final sign-off on the migration. In addition, if the Level is Delegate, the list state has special meaning for Team users as the Event may be processed by several Partition Users.


List State
User States and Comments
New
None
The Event occurs in the last iteration and the User State has not been set.

The default Level and Team Anchor for new Events can be set in the Director.
Resolved
Resolved
The User State has manually been set to Resolved. If the events occurs on the next iteration, the Director will automatically change the User State to Regression.
Accepted
Resolved

If the Level is Delegate and all Partition Users have either Accepted or Resolved the Event, any Team user will see the List State Resolved.
Accepted
Accepted
Occurrences of the Event is acceptable and will not hold back a final sign off on the migration.
In Progress
In Progress
Resolution of the Event is in progress.
Regression
Regression
Is automatically set by the Director on Publish, if the User State was set to Resolved and the Event nevertheless occurred in the last iteration.
Waiting
Waiting?


The Waiting list state only occurs for Team users and only if the Level is Delegate.  Waiting means that the team is waiting for the Partition Users to resolve the Event.

Waiting? means that one or more Partition users has set the user State to Rejected. To remove the ?, either ask the Partition Users to change the User State or change the Level to Team.
Done
Done?

This list state means that the Event did not occur in the last iteration, regardless of the User State set for the Event.

Done? means that the User State for the Event is either In Progress or Regression. Set the User State to Resolved to remove the?


However, if the Level is Delegate, any Team user will see the list state Resolved or Waiting regardless of the actual count for the Event and it is up to the Partition Users to resolve the Event.



All Events tab

The All Events lists event for all Business Objects providing an overview of everywhere a given Event occurs.



The columns are basically the same as in the Event list. 

  • Clicking the Business Object column takes you to the Event detail, where you can comment, change User State and delegate the Event. See following exercises
  • Clicking the count drills down in the aggregation for the Event. See following exercises

Search tab

The Search tab allows you to search for specific Business Objects if you now the key or part of the key. The key for a given Business Object is the values of the Interface Fields that were marked as key in the Studio Target Map.



  • First select a Business Object
  • Then enter part of the key and click the Submit button



Translation tab

The Translation tab shows all the Valuesets from Studio that were marked as Translation. Here users can enter data into the Valuesets.




Validation

When landing on the Translation tab, the Summary list is shown for the selected Partition Value. The summary shows the validation statistics for each Valueset.


migFx comes with a utility function that can export the rows for all Translation Valuesets to a file and afterwards to import a file containing validation results for each row. 


For instance, if a Translation Valueset deals with the translation of code values in the Source System to code values in the Target System, the utility can be used to validate that the code values for the Target System do actually exist.

  1. Export the Valuset rows to file using the migFx Utility
  2. Hand this file to proprietary functionality to validate the rows against the Target System and write a file containing the validation results
  3. Import this file using the migFx Utility


Data entry

Click a Valueset to show the content for this Valueset and to enter data. The columns in the list are the columns from the Valueset in Studio with the addition of a column to show a validation indicator and message.



Click these icons to enter data:


Add a new row
Edit row
Delete row



Settings tab

In the settings tab you can currently change the display language for Event messages. In the future more settings may be added.




What happened here?

The purpose of this exercise has been to introduce the different tabs in the Tracker. Along the way the notions of Level, User State and List State were explained. These all provide support for a workflow around the processing and sign-off on the Events in the Tracker.


In the following exercises you will drill down on a specific Event to see more and more detail and you will see how Event details can be edited to process a given Event.