You may have heard the buzz about a new major release of the most popular content delivery framework for Tridion? Well, get ready: the ever-growing community is about to release DD4T 2.0. In fact, a beta-release of the DD4T 2.0 Templates was released to the public a couple of days ago.
If you are reading this, you probably know that Tridion has an event system which allows you to attach your own custom functionality to pretty much everything that goes down. A typical example is to perform some pre-processing of an item before it is saved.
The customer I work for at the moment had just such a requirement. The only thing was: the pre-processing should only occur if the item in question was updated by SDL’s translation management system. The question is: how can one see that a ‘save’ action was triggered by TMS, and not by a regular user or some other system activity?