Boundary Event is core concept of UI technology in IBM BPM: any visual element (coach view) of screen (coach) can fire such event moving control from current screen to some other place, crossing “screen boundary“. In fact Boundary Event is the only way to make such transition on diagram of coaches. Problem is that IBM BPM event model is trivial and does not allow virtually any interference with event in progress, one cannot change event bubbling or handle it in try-catch manner. Find how I bypassed this limitation and implemented events interceptor.
Winter is coming… actually it has already come bringing constructor’s nightmare. Sudden freezing cold caused unexpected and massive restarts of all field stations. All because of the same hardware reason. Reason impossible to happen. All that because circuit boards were not suited up for real harsh outdoor conditions. 
