In many cases, data from fields on the UI must be passed directly to the API. A simple example is any detail screen with editable input fields. These fields must be passed to a save API in order to update the entered data in the application's database. This save API takes a specific XML structure as input. The fields on the detail screen should have XML binding that matches the input to the API.
In the Resource Hierarchy tree, the Input Namespace field in the action resource should be set appropriately to verify that the correct data from the console is passed to the save API.
Since all of the input fields on the screen have XML bindings for the input to the same API, they all have the same XML root element name in the binding. This root element name of the XML bindings is known as the namespace of that input field. Therefore, when that save action is invoked on the user interface, an XML is formed from all of the input fields containing the namespace specified for that action in the Resource Hierarchy tree. This XML is then passed to the API configured under that save action.
Another place where input namespace is frequently used is for user interface screens that have search criteria. The search criteria is passed to list APIs to fetch the data based on the search criteria entered. All the search criteria fields should have XML binding matching the input to the list API. The root element name of this XML is the namespace that should be specified for the list view that is shown when the user runs the search.