This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice This article is not considered official documentation for K2 software and is provided “as is” with no warranties.


By default K2 will use Obfuscation to mask the name of the SmartObject method being called. When capturing network traffic, this presents the method name in the following manner when inspecting the call:

<brokerpackage><smartobject guid="4787b518-752c-4341-8dab-a3b0da106c97" resultname="Primary_4787b518-752c-4341-8dab-a3b0da106c97_4787b518-752c-4341-8dab-a3b0da106c97"><method name="sLDxN7SZYHV07HzCXT3DsDq5N2WIiBv7MTrss6scU7WNNSjxj7qsB6JdtmA1


This article shows you how to run a fiddler trace and capture the actual method name being called, when needed for troubleshooting purposes.

Troubleshooting Steps

By adding and setting the Obfuscation value to false, one can run a fiddler trace and capture the actual method name being called for troubleshooting purposes. The following key can be added in the web.config file found in the following path:

C:\Program Files (x86)\K2 blackpearl\K2 smartforms Runtime

Opening the web.cofig file, add the following key under <appSettings>:

<add key="Forms.Runtime.ObfuscateMethodNames" value="false" />  

After making the changes and saving the web.config file, perform an IISReset, restart K2 services , and re-run the fiddler trace in order to capture the method name in a readable format:

<brokerpackage><smartobject guid="4787b518-752c-4341-8dab-a3b0da106c97" resultname="Primary_4787b518-752c-4341-8dab-a3b0da106c97_4787b518-752c-4341-8dab-a3b0da106c97"><method name="GetUsers"/>...