W-Error Mechanism and Error Outputs


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

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

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


Error Codes and Classification

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

Error codes and types are as follows.

  1. wrkE_2347
    Error Causes: This error is usually encountered when the fuseaction is false. The module name and the page name are connected with a dot to form the fuseaction: module_name.page_name
    Advices: If fuseaction was sent incorrectly, you can try to edit the link code you clicked. If you think your fuseaction value is correct, you can confirm whether it is available on your system and its accuracy from DevTools > Wo.
     
  2. wrkE_8080
    Error Causes: This error usually occurs when mandatory form - url parameters are not sent or incorrect data type is sent. The cfqueryparam tag is used to assign the parameter value and type while creating the query. This error is encountered if the value parameter in the cfqueryparam tag is not the data type defined in the cfsqltype parameter.                                                                                                            For example value = 'wrk' cfsqltype = 'cf_sql_integer' : In this case, you will get an incorrect data type error because the wrong data type was sent.

    Advices: Check if missing or incorrect data is sent from the url or the form. While assigning parameters in the query; Make sure that in the error line, in the cfqueryparam tag, the value parameter is sent in the desired type in the cfsqltype parameter. Probably integer or float type data type is requested, while the value is sent as string type.
     
  3. wrkE_8180
    Error Causes: This error occurs when an incorrect table name is used in your query or when a table is missing from your database.

    Advices: Make sure you type the table names correctly in your query. Check if the tables used in the query exist in your database. Complete any missing or incorrect tables.
     
  4. wrkE_8180_1
    Error Causes: This error occurs when your query uses an incorrect column name or when some columns are missing from your table.

    Advices: Make sure you type the column names correctly in your query. Check if the columns used in the query exist in your database table. Complete any missing or incorrect columns.
     
  5. wrkE_8181
    Error Causes: This error occurs when the database connection cannot be established. There may be a firewall or VPN on your network that is blocking 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.

    Advices: Disable any VPN that may block your access to the database. Check your firewall settings. Make sure your CF Datasource information is correct on your application server. Verify that your database server is turned on, test whether it responds to requests.
     
  6. wrkE_8280
    Error Causes:This error occurs when using an undefined variable name.

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

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


Feedback

Did you find this content helpful?
Related Contents