My team would like the URL parameters in Experience Builder to be enhanced. We would like the URL parameters to be simplified with similar functionality to what existed in Web App Builder, and we would like references to specific widgets and data sources to be removed from the URL parameters.
Below are two examples of the difference in URL parameters between Web App Builder (WAB) and Experience Builder (ExB):
This URL parameter selects “Well” records by the specified “API”. The main difference is the reference to “dataSource_4” in ExB.
- WAB: .../?query=Well;API%20IN(0403051203)
- ExB: .../#data_s=where%3AdataSource_4-Well-0%3AAPI%20IN%20('0403051203')
This URL parameter selects “Treatment Well” record/s based on the specified “TreatmentKey”. For ExB, extra parameters need to be included to turn on and off the necessary layers. In WAB the layers turn on and off automatically without specification in the URL.
- WAB: .../?query=Treatment%20Well;TreatmentKey%20IN%20(1433)
- ExB: .../#data_s=where%3AdataSource_4-WellStimulation-0%3ATreatmentKey%20IN%20(1433)&widget_37=layer_visibility:%7B%22widget_37-dataSource_4%22%3A%7B%22widget_37-dataSource_4-WellStimulation%22%3Atrue%2C%22widget_37-dataSource_4-WellStimulation-0%22%3Atrue%2C%22widget_37-dataSource_4-WellStimulation-1%22%3Afalse%2C%22widget_37-dataSource_4-WellStimulation-5%22%3Afalse%7D%7D
These longer URL parameters make it difficult for users to decipher what is being executed and to modify the inputs for their own use. Extra parameters must be included in the URL to create the same functionally as what was available in WAB. For example, specifying “widget_37=layer_visibility” to turn on layers that are being selected.
Furthermore, we are concerned with the specific calls to widgets and data sources. We use these URLs in other applications and staff often bookmark specific URLs. We are concerned if there are changes to the web map and/or app that these variables will change and break our existing URLs. In WAB we do not have to specify the specific widgets or data sources, allowing more flexibility when making updates and less chance of breaking existing workflows.
