This article is an attempt to chart what happens when in the RES Workspace Manager. Working with the product over the years, there’s always been one thing which has been sharpening the learning curve for many who are new to working with Workspace Manager. The topic in question is Cause and Effect: When you cause a change in the configuration, when does it take effect?
This article is my attempt to bridge this gap, by providing you with a quick reference to when what happens.
Until now the fastest method of learning the ways of Workspace Manager is to work with the product in a real-life scenario. Why is this so? It has to do with the way RES develops – or rather grows – the software. A large percentage of the curent featureset in Workspace Manager and the other products exists because of you, our current or prospective customers and partners. If you request it, it makes sense and there is a good business case, there is a high probability that RES Software implements the requested fuctionality. Our blessing is that we have a Product Management team who both master the arts of converting customer-specific requests into generic functionality while also keeping a clear strategy for the products moving forward. If one doesn’t master both, you are likely to end up with a hodge-podge of functionality lacking technical vision…
So, with that in place, let’s rip the hood off Workspace Manager and have a look at what happens when. To make things easier, I’ve created a chart, where we can see which configuration item is processed at what type of trigger event. Below is a preview of this chart (click to enlarge). The full chart can be downloaded as an excel file at the end of this article
A few notes about the chart, although it should be self explanatory.
- First of all, the chart isn’t verified 100%. I’ve created this off the top of my head, and a few good guys have helped out with the sanity check. So rather than sitting on it for another 3 months I’d rather share with you what I know at this point. The lovely thing about blogs are that they can be updated later :-)
- Second, there are comments throughout the spreadsheet that explains the given relationship between the cause and effects. Just mouse over wherever you see a small red triangle and there’s some additional info for you.
- Third, note that I have included the act of refreshing the session as both a configuration item and an actual event. The logic behind this is, you can configure when a session refresh should occur, but also other configuration events may take effect upon a refresh. This essentially means that every item that can occur during a refresh could have a dot in the columbs where a refresh can take place. I think however that would give an unclear picture of cause and effect and would only serve the few who sit and count product compare dots.
Note: If you find any discrepancies or errors in the document, feel free to comment on this article so I can fix it.