Although we have attempted to keep the UI reference implementation as pure as possible, it is still necessary to use some non-MDEX Engine URL parameters to maintain application state independent of the MDEX Engine query.
It is important, when building your own application,
that you remove these parameters (unless they are required by your
application). For example, if the MDEX Engine location is specified in a
configuration file, it is no longer necessary to maintain or support the
eneHost
and
enePort
parameters.
The non-MDEX Engine URL parameters that are used in the UI reference implementation are described in the following table:
Parameter |
Description |
---|---|
Used by the
This parameter is particularly useful during development, but should be removed from a production deployment. | |
Used by the
As with
| |
Used by
This parameter is useful for data inspection where different data sets may require different property keys to name the records. You should remove the
| |
Provides a simple means of hiding properties for each record
in the
| |
Provides a simple means of hiding the data that is returned
with each supplemental object in the
| |
Provides a simple means of hiding the data that is returned
with each supplemental merchandising object in the |