Comment 9 for bug 680468

Ok correction, after discussing more with GTK team, the real issue is simply that the clients fail to evaluate the context in some c
cases because it contains this:
  {"search_default_my_leaves": 1,'type':'add',"search_default_department_id": department_id}

Notice the "department_id" variable at the end? This special trick is allowed to access "context_"-prefixed fields from the global session context. But it fails if the HR module was only recently installed, and the session context has not been reloaded since then, and thus does not have any "context_department_id" value.

Hence the strange behavior we were seeing.

Now as to fix this, unfortunately the server does not have any way of notifying the client about new session context items.. the 2 cases where the session context is reloaded are hardcoded: upon login and when clicking on the OK button in the user preferences popup.