In my last two blog posts about problem solving in OrgVue, I looked at abstracting the problem and six simple checks to help resolve any issues. But sometimes you still can’t work out what’s causing the issue, even after you’ve broken the problem down, and tested all the simple possibilities. In these cases, people often find the most efficient way of getting hold of information is to try the training materials (manual, online videos, forum), then ask an advanced user/superuser, then contact email@example.com if they’re still having trouble.
At this stage, troubleshooting closely resembles the scientific method. First we try to take the observed behaviour and split it into all its component parts. Then we come up with a hypothesis about where the problem might be originating, and test it by making a change, keeping everything else the same and seeing what happens. You might iterate through several theories but as long as you capture all the factors that affect a feature, the potential reasons why each might not be working, and disprove, you’ll discover the reason for failure.
I recently had an issue with an expression not working correctly. After going through the above stages I started to ask questions like:
– “If it doesn’t work in properties; does it work in the Expressions manager?”
– “Can it be broken up into smaller expressions that work individually?”
– “Does it reference any other values or expressions that might be invalid?”
– “Are there any advanced features involved e.g. settemporary, or lookups, that make it look like the problem is with the expression when it’s actually with another feature?”
The more precise you can be when defining the problem, and methodical when testing it, the easier it will be to rule out its possible causes. This also applies when describing issues you can’t solve to the support desk. For example, descriptions like “my data’s been corrupted” or “the screen’s frozen” could be written more specifically as “the cells in my lookup properties are displaying expressions rather than meaningful values” or “I can’t see the text under the donut icons in tree view”.
I hope some of these checks and methods help! If you ever have questions or ideas, the OrgVue forum is a great way for OrgVue users to find technical answers, share best practice and suggest improvements to the product.
Otherwise you can get in touch with me: Ben.Marshall@orgvue.com
Latest posts by Ben Marshall (see all)
- 5 ways to optimise OrgVue - September 9, 2015
- OrgVue Problem Solving #3: Not seeing what you expected? - July 28, 2015
- OrgVue Problem Solving #2: Six simple checks - July 20, 2015