Hi Community
We are getting an Invalid Response error from Case Management Framework. The action we are using is Case_GetActivities in the CaseServicesAPI. This is an error we are picking up in production only and not in any other environment. In addition to that, the error gets caught as a security exception and redirects us to the InvalidPermission screen.We only get this error if a previously closed case is trying to be retrieved on screen. If no closed case is supposed to be shown on the screen, then the action works just fine.
We are running an On-Premises installation and have a different server setup in production compared to our development and test environments.
Is there anyone who has experienced such an error?
Your assistance will be much appreciated.
Hi,
As you mentioned that you are getting error when trying to access the case which is already closed. Most possible reason may be access, as case is already closed so you don't have permission to access it. As this API is for getting active tasks only. Then invalid permission page may be due to application's logic.
regards
"As this API is for getting active tasks only. "
Are you sure about this? Since that's not (clearly) mentioned in the documentation and you can filter by the 'closed' Status of an Activity or Case.
Also, from a business perspective I should be able to retrieve the activities of closed cases.
Have you tried without any filter like get all activities for all the users. Still are you not able to get closed activity. please confirm.
The action works perfectly in our dev and test environments. The data is retrieved successfully. However it is in the production environment where we get an Invalid Response.
The cause could be lots of different environment-specific settings/configs especially with on-premise installations.
We've had issues with the CaseManagement configuration bootstrapping in the past. So first make sure this is properly ran and all necessary entities (like case status) are created.
Could also be helpful to create a simple test screen for debugging.
Also keep in mind as per version 1.5.2 the service actions used for fetching cases and activities require a logged in user: https://www.outsystems.com/forge/component-versions/9179/version/0/platform/