"Whoops..." error when calling the viflow 7 WebModel
Applies to: viflow 7 | Article: 1344211 | Updated on 05.04.2024
Use web server for the WebModel
Please note that only the (now discontinued and no longer supported by Microsoft!) Internet Explorer can display the local viflow 7 WebModel stored on a file server. If you try to open the local WebModel e.g. with the browsers Google Chrome or Mozilla Firefox, you will get the error message below.
For more information about the location of the viflow WebModel and the compatible browsers, please refer to the article ››› Internet Explorer will be discontinued.
If the message Whoops! We are sorry – WebModel cannot be displayed appears, this can have various causes.
To fix the error and check the WebModel, go through the following steps:
1st step: Reset WebModel
Click on reset link {{1}} 
in the message. This resets the WebModel and then reloads it.
Is the WebModel displayed correctly now?
Step 2 Clear browser cache
To ensure that the WebModel is not displayed correctly by loading outdated data from the browser cache, you should delete the cache of the browser you are using.
Clearing the cache and cookies differs depending on the browser, but is basically the same:
Tip - Check the web model
If you open the WebModel in an incognito window or in a corresponding mode of the browser, the cache or saved cookies will not be accessed. In this way you can quickly check whether the WebModel is basically working. If the WebModel is displayed in this mode, the error must be caused by the web server or the IT infrastructure used.
You can find the corresponding mode in the following browsers, for example:
- Microsoft Edge : Settings and more - New InPrivate window
- Google Chrome : Customize and manage under Google Chrome - New incognito window
- Mozilla Firefox: Open menu - New private window
Learn more about caching
For more information about caching and deleting the cache on the web server, see the article ››› Disabling caching for viflow WebModels.
Is the WebModel not displayed after deleting the cache or in incognito mode?
Then please continue with step 3.
3rd step: Checking the process model
If the error persists despite the cache being emptied and the WebModel being reset, the viflow process model should be checked for empty objects. Empty objects prevent the WebModel from being displayed correctly and, in rare cases, can be caused by importing objects or other actions in viflow.
Checking the viflow process model for empty objects
- Open your process model (either the process model file (*.vfpx) or the viflow SQL database).
- Navigate to File - Information - Clean Process Model.
- Select the object types on the left one after the other and click on the List tab.
If there are empty objects, they usually appear at the top {{2}}. - Highlight the empty objects and click Finish to delete them.
- Now open the recycle bin ( View – Window – Recycle bin ) and finally delete all empty objects from the process model.
- Export the process model again and see if it can be viewed now.
Is the WebModel displayed now?
If the WebModel is still not displayed despite the measures described above, this is probably due to other software configurations (firewall, blocked Javascript, etc.).
In this case, please contact your IT administration or our support team at ››› support@viflow.de.