You can customize the visibility of the default next-generation Order Hub features
to suit your business needs. Hide the features that are not applicable or used by completing this
task.
Procedure
-
Find the feature ID of the feature that you want to hide. The value can be located as an id in
the features.json file in the om-orderhub-base container
under the /opt/app-root/src/shell-ui/assets/features.json path.
-
Create a custom features.json file and add an entry for the feature that
you want to hide.
For example, to hide the Safety stock rules menu, create a
features.json
with the following code:
[
{
"id": "oms-inventory-ss-rules",
"hidden": "true"
}
]
For more information, see Creating the features.json files.
-
Test your changes by copying the features.json file into the base
container.
docker exec om-orderhub-base bash -c 'mkdir -p /opt/app-root/src/shell-ui/assets/custom'
docker cp path to features.json om-orderhub-base:/opt/app-root/src/shell-ui/assets/custom/
-
Build your changes.
./build-customization.sh build-image image_name image_tag ui-modules
For
example:
./build-customization.sh build-image om-orderhub-ext custom buc-app-settings
If you do not have any customized modules, you do not have to specify
ui-modules.
For example:
./build-customization.sh build-image om-orderhub-ext custom
For more information, see Building customizations in next-generation Order Hub.
-
Deploy your changes. For more information, see Deployment process.