The Tracker supports a workflow around the Events to ensure that all Events are being considered and that all Events are subject to a final sign-off. This means that before the migrations goes live, all Events should either be resolved so they do no longer occur or be accepted. Accepting an Event means actively acknowledging that the Event occurs and that this is acceptable when going live.


In this exercise  we will look at how to use the Event Editor to:

  • Change the User State
  • Delegate the Event processing to Partition Users
  • Comment events
  • Mark Events as derived from other Events



Note that the Event Editor is different depending on whether you are a Team user or a Partition User


The exercise is rooted in the Event I0022 Interest {0} with default rate {1} has been created on the Business Object Customer



Event Editor

In order to display the Event Editor for the Event, click the Event message.



The Event Editor shows static information from the Event itself that cannot be modified:

  • The Business Object Name
  • The Event Message
  • The Event Severity
  • The Event Area
  • The Count, Baseline Count and Delta

In addition the Event Editor shows the history of all the modifications that was done to the Event by users and also by the Director when publishing


The Event Editor is different depending on whether you are a Team User or a Partition User.



Team User

You are a Team User, so this section corresponds to the Event Editor as you see it.


In addition to the above, for a Team User the Event Editor contains a Partition box showing the count and User State for the Event for the different Partitions 


In the Event Editor you can modify


Team Anchor
You can choose yourself or another Team member to be Team Anchor. Unfortunately in your Training setup there is only you in the team.

Note that in the Director it is possible - per Business Object - to identify a Team User that will automatically be designated Team Anchor for new Events on publish
User State
As Team User, you can set the User State. The available User States are explained in a previous exercise.

If the Event is Delegated to Partition Users (see below) the User State becomes read only and cannot be modified.
Derived From
Choose another Event in the drop down that is the cause of this Event.

Marking an Event Derived like this will normally hide the Event in the Event list, unless the Derived filter is deactivated. However, if in the last iteration there are zero occurrences of the selected, causing Event but there are occurrences of this Event, this Event will not be hidden in the list regardless of the filter setting.
Delegate to Partition User
A check mark here means that the processing and sign-off of the Event is delegated to the users in the businesses involved in the migration. This means that it will be the Partition User that will set the User State for the Event for their respective partitions.

If the Event is delegated the User State becomes read only at Team Level and cannot be modified here
Comments
You can enter comments that will be visible to all Team and Partition Users



Partition User

A Partition User can always enter comments that are visible to Team Users and users in the same Partition, but not to users in other Partitions. Note, that since you are logged on as a Team User, you will not be able to see the Event Editor in this Partition User state.


Team Level

If the Level of the Event is Team, then the Event Editor for the remaining part is read-only for the Partition User and is basically just showing the Team status of the Event plus comments from Team Users and other users in the same Partition.



Delegated Level

If the Level of the Event is Delegate, then the Partition User can 

  • Select a user from the Partition as responsible 
  • Set the User State of the Event for this Partition




What happened here?

In this exercise you saw how the Event Editor allows Team and Partition Users to collaborate on the resolution and sign-off on Events. The end goal is to ensure that all Events are processed and either resolved or accepted before go-live.


The Event Editor behaves differently for Team and Partition Users and for each again differently depending on whether Level is Team or Delegate.


In these last 3 exercises we have presented the Tracker, in the next exercise you get the chance to try it out by processing the Events that occurred duringthe Card migration