You can set a busy state for each SAPUI5 control. This function adapts to the space available on the UI.
When to Use
Use the busy state of the control if:
- The operation takes more than one second (busy state set at control level)
- You want to indicate that data is loading on a table or on a list after performing a search or filtering (set the busy state at table or list level).
Do not use the busy state if:
- The operation lasts less than one second.
- You expect several busy states at once. In this case, consider setting the busy state at a higher level or container.
- You’re loading an app from the launchpad or navigating from an app to another. Use placeholder loading instead (when available in your framework).
Avoid showing multiple busy states at once. If you expect multiple busy states on various controls, you can set the busy state on a control or container above.
In some cases, however, it makes sense to allow multiple busy states. For example, a page could contain a form and several tables that load asynchronously. In this case, it does not make sense to set the busy state at page level until all the data is loaded as the user can start filling out the form which is already available. Response times may vary due to table data retrieval from different services.
Try to enable as much as possible on one screen, so the user can start working while the rest of the data is being loaded in the background. Set the busy state for those UI elements that will require some time to load.
Want to dive deeper? Follow the links below to find out more about related controls, the SAPUI5 implementation, and the visual design.