...
Expand | ||
---|---|---|
| ||
Check the following:
|
Expand | ||
---|---|---|
| ||
Scenario: The error message, “We were not able to complete your request due to a system error. As a result, no action is taken. Please contact Customer Support for further assistance. Reference id : be2fa6ca-c84f-4a8d-b7a7-1462cd0f2267” is displayed in a pop up when performing an action in the end application. Solution: Check the network tab of the browser console to verify the parameters passed for the request. Copy the reference number from the pop up and search for it in all the “.log” files within the work folder path to find the reason for the server side exception. |
Expand | ||
---|---|---|
| ||
Refer Adding a New Language in your Application - from Canvas 18.1 onwards.Application - from Canvas 18.1 onwards. |
Expand | ||
---|---|---|
| ||
Refer Enabling Custom Load Mask. |
Data Rendering or Data Submission
...
Expand | |||||
---|---|---|---|---|---|
| |||||
Check for the following error pattern in the log file:
Solution: Request Modeler assigns a random and unique reference number for each request, which needs to be stored in the REFERENCE column in OD_AUDIT table in CT schema. Check in your code if the request data has been is modified to make the value of REFERENCE_NO column to null. If so, then the insert to the REFERENCE column in the OD_AUDIT table will failmodify the code to make it not null because Request Modeler needs the reference number for internal processing. If you need to use or process a reference for functional logic, use a different column/variable to capture it. |
Expand | |||||
---|---|---|---|---|---|
| |||||
Scenarios:
For above scenarios, check for the following pattern in the error logs:
Solution: For any exception of the above pattern, check the ctdblogs to find the SQL ID of the query that is failing. If the query is related to functional database/schema, fix the query. If the query is within CT or includes a CT table, check if all the incremental scripts were applied properly. Even then if not resolved, inform the CT Platform support team. |
...
Expand | |||||
---|---|---|---|---|---|
| |||||
Check for the following pattern in the error logs:
Solution: Check the stack trace to find the details of the web service that did not return the success responsethe stack trace to find the details of the web service that did not return the success response. |
Expand | ||
---|---|---|
| ||
Scenario: Data persistence is sometimes required at every page while moving to next page as end-users of the application can quit the application at any stage and come back to resume the work. Solution: CT Platform does not maintain the state of each form or page. Implementation team must write code to handle persist data across pages or forms for the required functional behaviour in the application. |
Expand | ||
---|---|---|
| ||
Refer Custom Publisher. |
...
Expand | ||
---|---|---|
| ||
Refer Configuring Request Modeler Actions for Self-Designed FormsModeler Actions for Self-Designed Forms. |
Expand | ||
---|---|---|
| ||
Refer Form Items Event Wiring. |
Expand | ||
---|---|---|
| ||
Refer Form and Form Item APIs. |
Expand | |||||||
---|---|---|---|---|---|---|---|
| Refer Form Items Event Wiring.
| ||||||
Use the following syntax to use the performance timer:
|
Database
Expand | ||
---|---|---|
| ||
Data can be fetched using Instruction classes (Java class) in Canvas. Canvas uses iBatis library for database access. Callable statements can be used to access Stored Procedures and Functions to get the data.
|
...