Hi!
I was recently working on a portal and I directly tried to use a!queryRecordType there as Appian advertised in their recent releases but the response time was more than 30 seconds. Sometimes, it was so high that the request was hitting the timeout and the user was shown an error. As part of the query, I had a couple of queries that were getting the data without any heavy filtering or aggregation. If I load that interface directly in my design, the response time was less than 2000ms.
Now my questions are
Discussion posts and replies are publicly visible
I do not see any risk for a vulnerability as Appian is never doing any API calls directly from browser.
Then, IMHO a query taking 2 seconds is not acceptable. Especially not for a portal where I expect more traffic.
I did not do any investigations on portal record query performance recently. Did you consider opening a support case?
2000ms is the total interface load time which includes 4 queries being called via integration, manipulating the data received, and showing the data on the screen.
Correction - It is actually 481ms on the first screen and 635ms on the second screen.
OK, that's more reasonable :-)
CE is definitely underpowered so it's not the best tell for real world performance.
Hi Harshit, i'm a product manager at Appian and it's not expected behavior that a!queryRecordType behaves slowly. Could you please submit a support case with details about your portal so we can investigate this further? Thank you!
I would love to do that. Can you help me with how can I do it? I don't have access to portal forum.
I believe you can submit one here: https://appian.com/support/resources/support.html#:~:text=To%20open%20a%20support%20case,identification%20number%20for%20future%20reference
I am unable to.
UPDATE: This is a known issue within Appian's Engineering team and they will fix it in the next update. SOURCE: community.appian.com/.../125040