I am involved, between others, in a PS 2003 -> PS 2007 migration project. We are close to the end, however, we had a request from the end users to have on the 'My tasks' page a web part having the folowing features:
-
displays in a grid for a selectable month and year all the tasks assigned to the current user were the user reported work effort
-
tasks are grouped by projects
-
for every task and every day of the selected month the reported work is displayed with different color depending on the status of the reported data: saved, submitted for approval, approved
The big challenge was the last requirement above, to find out the status of the task timephased data (data reorted per day); I will peresent to you the steps I took to solve that problem.
1. The programmability of PS 2007 goes through the PSI web services. The classes from the SDK should be touched only if you create Project Server extensions. The first step was to use the ReadResourceAssignments method of the Resource PSI web service to obtain the assignment for the current user.
2. Iterate though all the assignments and get the timephased data for every of them for each day of the current month using the ReadStatusTimephasedData method of the Statusing PSI web service, then feed a DataTable which will be the datasource of a Asp.Net data grid with the timpehased data. For every of the assignments call the ReadAssignmentHistory method of the Statusing PSI web service.
3. And here is the hard part: I tried to iterate through the transactions of the assignment history for the assignments obtained in teh iteration above and call the ReadTransactionDetails method of the Statusing PSI web service, in order to try find out the status of the timephased data for every day. The problem is that for the majority of the history entries (transactions), this web service method call fails with a general unhandled exception. I figured out, that for those transations represented by AssnHistoryDataSet.HistoryRow instances the TASK_CHANGE_DATA attributes is null. This might be or not the reason for the failure.
I started to crawl through the code of Project Server assemblies using reflection, and I figured out that an AssnHistoryDataSet.HistoryRow instance represents all the timephased data submitted using the Save button from the MyTasks page from the project web access and the ASSN_CHANGE_DATA attribute contains all the timephased changes which came with that save. The changes are in the form of binary serialisation of the Microsoft.Office.Project.SvrDataEdit.ChangeLog internal class which contains a list of the Microsoft.Office.Project.SvrDataEdit.Change internal class instances, which contains in the Value attribute a Microsoft.Office.Project.SvrDataEdit.PeriodData internal class instance which in turn has the Start, End and Value attributes. Additionally, the ASSN_TRANS_ACTION_ENUM of the history object means 'Submitted' if 0, 'Approved' if 1 and 'Rejected' if 2. If ASSN_TRANS_ACTION_ENUM is 0, then the ASSN_CHANGE_DATA contains all the unapproved submitted data on the date of creation of the history entry, in PeriodData instances. If 1, then contains all the approved data in the momentof creation of the history entry.
To make it more complicated, if a user saves multiple changes on My Tasks page using the Save button and then submits them for approval, all those changes are logged as Microsoft.Office.Project.SvrDataEdit.PeriodData instances for every changed day.
See below the code to deserialise the change log for a transaction and save it in a custom list containing custom HistoryEntry classes.
Object obj = fomBytesMethod.Invoke(null, new object[] { new ByteArray(byteData) });
int count = (int)changeLogType.InvokeMember("Count", BindingFlags.Default | BindingFlags.GetProperty, null, obj, null);
List<HistoryEntry> assignmentTimephasedData = new List<HistoryEntry>();
for (int idx = 0; idx < count; idx++)
{
object change = changeLogType.InvokeMember("Item", BindingFlags.Default | BindingFlags.GetProperty, null, obj, new object[] { idx });
object changeValue = changeType.InvokeMember("Value", BindingFlags.Default | BindingFlags.GetProperty, null, change, null);
DateTime startDate = (DateTime)periodDataType.InvokeMember("Start", BindingFlags.Default | BindingFlags.GetProperty, null, changeValue, null);
DateTime endDate = (DateTime)periodDataType.InvokeMember("End", BindingFlags.Default | BindingFlags.GetProperty, null, changeValue, null);
double changeValueValue = (double)periodDataType.InvokeMember("Value", BindingFlags.Default | BindingFlags.GetProperty, null, changeValue, null);
HistoryEntry historyEntry = new HistoryEntry(startDate, endDate, changeValueValue);
assignmentTimephasedData.Add(historyEntry);
}
In order to obtain the status of a reported timpehased data for an assignment (for example, I have 4 hours reported actual work for 8th of Feb for the 'Create Users Page' assignment) we have to iterate through all transactions (history) for that assignment, in chronological order, get the latest PeriodData data instance for that day, and depending on the ASSN_TRANS_ACTION_ENUM value we can say that we have an 'Approved' or 'Submitted' status. If there is no value for that day in the transaction history or the latest value obtained from the transaction history is different then the one obtained from the timephased data returned via the ReadStatusTimephasedData web method, then the status of the timephased data is 'Saved'. All the logic doing this kinda staff in the Project Server assemblies are obfuscated, it was challenging to sort all these things out. Hope this helps!