Designer troubleshooting
Usually problems with the designer occur when JavaScript libraries are initialized incorrectly.
For Designer versions that come with Workflow Engine 3.0 and later
The following libraries are required by Designer:
In order to troubleshoot Designer, open the browser console by pressing the F12 button. Copy the error text and send it to us.
1. A conflict between Semantic UI and Bootstrap is possible
Styles and JavaScript libraries may conflict with each other. If you are using Designer in a Multipage Application (MPA) and if Bootstrap's JavaScript code is not called from the Designer page, then you should not face any issues. In Single Page Applications (SPA) and on mixed MPA pages you should load JavaScript libraries in the following order: first, you should load the Semantic UI library and then Bootstrap. In this case, there will be no conflicts leading to the inoperability of Designer or Bootstrap. The CSS load order does not matter since the CSS conflict has been eliminated in Designer's CSS.
A universal method for resolving conflicts between CSS Frameworks and the Designer is proposed in this article
For Designer versions that come with Workflow Engine versions earlier than 3.0
The following libraries are required by Designer:
In order to troubleshoot Designer, open the browser console by pressing the F12 button.
Here's a list of typical errors:
- Error: "Object does not support property or method 'dialog'"
You haven't initialized JQuery UI or you have included JQuery UI twice.
- Error: "Unhandled exception at line 5, column ....... in ...../Scripts/workflowdesigner.min.js"
You are using an incompatible version of jQuery.
- Problems with mouse control in Chrome
In some cases AdBlock blocks some mouse events.
To resolve the issue you need to disable AdBlock and restart your browser.
- Error: "Object doesn't support property or method 'addEventListener'" in InternetExplorer
Follow these instructions.
- Error: "0x... - JavaScript runtime error: Unspecified error." from kinetic.js library
This happens when the library can't download images. Check that the path to images configured for the Designer object
at imagefolder: '/images/'
property exists and contains images for Designer.