Keep screens responsive with modern web requests
Also listed as: Modern web requests (Fetch API)
What is it?
Everyday screen actions, such as save, search, delete and wizard steps, send requests to the server. Xelence will send them using the Fetch API, the current standard way for web pages to talk to a server without holding up the screen.
Why does it matter?
Older request methods can leave screens waiting on the server, which makes them feel slow when the system is busy.
More responsive screens under load, and a web layer that stays in line with current browser standards.
Getting it into your solution
- Needs an upgrade to the Xelence release
Start thinking about
- Do your Xelence screens use custom scripts that make their own server calls?
- Which screens do staff find slowest at busy times?
- When would a move to Xelence 10.0 fit your release calendar?
Terms used on this card
- API
- A defined way for two software systems to exchange data or request actions from each other.
- Asynchronous processing
- Running long tasks in the background, so people and other work don't have to wait for them to finish.
- Wizard
- A form that guides someone through several steps, one screen at a time.