Report Errors (How To)
var foo = 'bar";)
- mismatch between custom scripts and workflow (e.g. field id's referenced in custom scripts don't exist in the workflow configuration)
- sql queries on the server deliver wrong data structures, UI components bound to that data crash.
Workflow/Formsettings.xml, custom scripts
If you encounter a bug in a custom workflow, please also submit the workflow.xml/formsettings.xml for this workflow and any custom scriptsthat are used within the workflow.
- When using Internet Explorer, hit F12 to open the integrated developer tools
- When using Firefox, we recommend to install the free Firebug extension, which can also be enabled by hitting F12.
- When using Google Chrome, F12 opens the Chrome Developer Tools.
Then go through the following steps:
- Copy the console error message alongside with the line numbers contained there.
- Also inspect the network panel for any red entries. If you find one, expand it and also perform a screenshot.
Screenshot 2: The network panel indicates that the file nonexisting_customscript.js couldn't be loaded. This is mostly caused by wrong script paths or typos in filenames.
(You might have to reload the page after you opened the developer tools in order to see the network traffic of the page)
Fiddler2 is a free web debugging proxy for windows systems. It captures the HTTP traffic between web client (i.e. browser) and server and is able to export that traffic in a session-based format (.saz - archives). As the whole client-server traffic is captured, SAZ-Archives especially useful for catching client/server errors (i.e. an SQL statement in workflow.xml that doesn't produce the expected output and crashes a grid widget on the client).
If we request you to do so, please generate a SAZ archive using these instructions:
- Install Fiddler (full version) - see the installation instructions
- Open Fiddler and click “Capture Traffic” (F12)
- Open SmartClient or the browser and navigate to the affected workflow page
- Close all other internet-connected apps (e.g. browsers) and clear the session list by clicking the [X] Icon, more detailed instructions can be found here
- Reload the affected page and perform the buggy action (button click)
- After finishing it, move back to Fiddler and choose File > Save > All Sessions...
- Send us the saved .saz file