Enhanced trace files in Content Management 25.2

With the release of Content Management 25.2, we have introduced many new features. However some of the most exciting features for me are ones that are largely hidden away for System Administrators. When a piece of oScript code, or a weblingo file encounters an unhandled exception Content Management generates a trace file.

This trace file outlines the stack functions that were executed along with the variables, and arguments that were passed in. For years they've been key to resolving different errors inside of the product and allowing us to make it more robust.

One of the struggles with Content Management and trace files is that the product is so extensible. There are third party solutions, in-house developed modules, and sometimes custom patches deployed on a given system. Trace files will reference a line of code, which may or may not be the same from one customer system to another customer system. This sometimes results in additional delay trying to understand the delta between one system and another.

In 25.2 we have given them a major face lift. Now trace files will output the section of code around the exception. This includes any code that was overwritten with patches, custom modules, etc. Allowing developers, customers, and support the ability to see what specifically failed with more context and in many cases avoiding the need to boot up Eclipse all together.

The Ripple Effect of Enhanced Traces

This enhancement has profound benefits across the board:

For System Administrators: You get a much clearer initial picture. You can often make a more informed decision about the severity or nature of an issue, and whether to escalate it to your development team or OpenText support with much richer preliminary information.
For Developers (In-house, Partners, or Customizations): This is a massive time saver. No more "is your line 31 the same as my line 31?" You see the exact code, including any custom logic or patches. This drastically cuts down on debugging time, especially when working with code you didn't write or that has been modified by others.
For OpenText Support: We can diagnose issues much faster. With the code snippet included, our support engineers get immediate context, even on heavily customized systems. This reduces the back-and-forth often needed to obtain source code or clarify environment specifics, leading to quicker resolutions for everyone.

The introduction of surrounding code and detailed variable states in trace files for Content Management 25.2 is more than just a convenience; it's a fundamental improvement to the troubleshooting toolkit. It acknowledges the complex, extensible nature of modern enterprise platforms and provides the clarity needed to navigate that complexity efficiently.

So, while it might be a "hidden" feature for some, for those on the front lines of development, administration, and support, this is a welcome ray of light that will undoubtedly make resolving issues faster and more straightforward. We encourage you to explore this new capability when you upgrade and experience the benefits firsthand!

Back to post listing