Wiki Detay | wiki workcube

Rapid developments in the software industry can cause errors, regardless of whether it is web, desktop or mobile applications. Errors; It may vary depending on usage, algorithmic problems, syntax or infrastructure. Software manufacturers all over the world try to improve their QA processes in order to keep errors to a minimum, fix them quickly and not to repeat the same mistakes.

Another duty of the application provider is to pre-classify the errors that the application may give, and to provide warnings in a language that the user can understand and, if possible, recommendations for solutions. The last possibility is to ensure that the user can easily report the error he receives to the application provider.

Error outputs have been reclassified in Workcube. Errors that users may encounter for various reasons were classified, and the outputs were displayed in the form of detailed messages, recommendations, and related solution links in a way that users could understand. Thus, the W-Error mechanism emerged, where errors are classified regularly.

Error Codes and Classification

In Workcube, errors are classified according to their source. The most basic error causes are the absence of tables - table columns hosted on your Workcube database server, files incorrectly included in the page, missing workcube objects or missing parameters.

Error codes and types are as follows.

wrkE_2347
Error Reasons: This error is usually encountered when the fuseaction is incorrect. The module name and the page name are connected with a dot to create the fuseaction: module_name.page_name

Recommendations:If the fuseaction is sent incorrectly, you can try to edit the link code you clicked. If you think your fuseaction value is correct, you can check whether it is available on your system and whether it is correct in DevTools>Wo.
wrkE_8080
Error Reasons: This error usually occurs when the mandatory form - url parameters are not sent, or the wrong data type is sent. The cfqueryparam tag is used to assign parameter value and type when creating the query.

If the value parameter in the cfqueryparam tag is not of the data type defined in the cfsqltype parameter, this error is encountered. For example, value = 'wrk', cfsqltype = 'cf_sql_integer': In this case, you will encounter the incorrect data type error because the incorrect data type is sent.

Recommendations: Check whether incomplete or incorrect data has been sent from the URL or form. When assigning parameters within the query; In the line giving the error, in the cfqueryparam tag, make sure that the value parameter is sent with the desired type in the cfsqltype parameter. While an integer or float type data type was probably requested, the value was sent as a string type.
wrkE_8180
Error Causes: This error occurs when an incorrect table name is used in your query, or when a table is missing in your database.

Recommendations: Make sure you typed the table names correctly in your query. Check whether the tables used in the query exist in your database. Complete any missing or incorrect tables.
wrkE_8180_1
Error Reasons: This error occurs when the wrong column name is used in your query or some columns are missing in your table.

Recommendations: Make sure you typed the column names correctly in your query. Check whether the columns used in the query exist in your database table. Complete any missing or incorrect columns.
wrkE_8181
Error Reasons: This error occurs when the database connection cannot be made. There may be a firewall or VPN on your network that blocks database access. Your CF datasource definitions on your application server may be incorrect or user information may have changed. Your database server may be down or not responding to requests.

Recommendations: If you have a VPN that may prevent you from accessing the database, disable it. Check your firewall settings. Make sure your CF Datasource information is correct on your application server. Verify that your database server is open, test whether it responds to requests.
wrkE_8280
Error Reasons: This error occurs when an undefined variable name is used.

Recommendations: Check whether the variable is defined. Make sure the variable name is used correctly.
wrkE_8280_1
Error Reasons: This error usually occurs when the file to be included in the page is not found in the relevant directory.

Recommendations: Make sure that the directory information of the file to be included is written correctly. Check whether the file you want to be included is in the current directory.

Click the link below to watch the video explaining how to examine a sample error output and send it to Workcube Support using the report problem button.
>> https://www.loom.com/share/4204e343d0254678946688ccfdea139a

Tips

Record was not found

Feedback

Did you find this content helpful?

Please Write Your Feedback!

Name*

Last Name*

Email *

About Workcube Objects

Error Reports

Provides reports of errors occurring on the system.

Type: Report Version: Catalsyt v5 Licence: Standard Author: Workcube Core