38
Views
2
Comments
Solved
[OutTracker] OutTracker error when using browser's back button
outtracker
Reactive icon
Forge asset by OutSystems
Application Type
Reactive
Service Studio Version
11.54.20 (Build 62656)
Platform Version
11.21.0 (Build 39357)

Problem:

The error: "Error executing query." occurs on /OutTracker/RequestList after selecting an existing ticket, viewing the case details, and then using the browsers back button instead of the internal "Back To Requests List" button.

All references are up to date. 

Unfortunately I cannot look into what is happening on Case_GetCases, as CaseServices_API is a locked module such that a local copy cannot even be made, let alone debugging.

It does not appear to be a timeout, as the duration of requests to Case_GetCases on Service Actions Log in ServiceCenter appear to be about the same regardless of rather or not the error is being generated versus when there is no error with the request.



Steps to recreate:

  1. Install OutTracker into your freshly activated sandbox. (It should auto-install all of the dependencies.)
  2. Update references in the 2 modules that have out of date references due to OutSystems UI updates.
  3. Install the default bootstrap data. (It may have already been installed but this is a step I took... Doubt it's actually necessary.)
  4. Log in as the bootstrap requester Anthony Hanks.
  5. Click any of the available requests.
  6. Use Chrome's Back button instead of 'Back to Requests List' button.
  7. Enjoy your new error popup 'Error executing query' and having no further way to resolve the issue due to the locked module.



Full error detail:

Full Environment Information:
eSpaceVer: Id=130, 
PubId=0, 
CompiledWith=11.21.0.39357
RequestUrl: http://qhfcif002.outsystemscloud.com/CaseServices_API/serviceapi/Case_GetCases (Method: POST)
AppDomain: /LM/W3SVC/5/ROOT/CaseServices_API-33-133363040897406806
FilePath: C:\OutSystems\Sandboxes\QHFCIF002\Platform Server\running\CaseServices_API\
ClientIp: 127.0.0.1Locale: en-US
DateFormat: yyyy-MM-dd
PID: 33092 ('w3wp', Started='8/11/2023 1:23:24 PM', Priv=929Mb, Virt=2116568Mb)
TID: 58
Thread Name:
.NET: 4.0.30319.42000

Stack:
Error executing query.   
   at ssCaseServices_API.Actions.ActionException_Manage(HeContext heContext, String inParamAllExceptions, String inParamActionName, String inParamActionGroup, STPayloadDatetimeStructure inParamDateTime, String inParamContext)   
   at ssCaseServices_API.ServiceAPIController.Flows.ActionCase_GetCases(HeContext heContext, STCaseScopeStructure inParamCaseScope, STCaseSearchCriteriaStructure inParamCaseSearchCriteria, RLCaseSortList inParamSortFieldList, Boolean inParamIncludeCounters, Int32 inParamPageNumber, Int32 inParamMaxResultsPerPage, RLSearch_CaseDetailsList& outParamCaseResults, Int64& outParamTotalResults, RLCaseCounterList& outParamCaseCounters)   
   at ssCaseServices_API.ServiceAPIController.ServiceAPICase_GetCases()

2024-09-19 13-52-30
Kavinilammurugu (Kavin)
Solution

Hi Braxton,

I did some checking and found that this issue is caused by re-initialization of SortFieldList.
You can find the OnInitialize action having an append to initialize the default sort field. 
Chrome Browser's Back button have the old values and also executes the OnInitialize again so the SortFieldList gets appended again with same sort field which causes the issue. 


Please try adding a Listclear before the ListAppend in OnInitialize Action as per the screenshot given below.

Before adding ListClear, I did a test by adding an expression somewhere in the TaskList screen to show the SortFieldList content or Length. when clicked on Back To Task List, the length on the SortFieldList would be 1. when clicked on Chrome back button, the length on the SortFieldList would be 2. 

Please check and let me know if this resolves the "Error executing query." . 

2023-09-06 23-22-11
Brax

That did it! And in hindsight it's definitely something I should have noticed with a simple debug haha.


Thanks for helping with my brain fog!

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.