In IBM Sterling WMS/OMS, refresh Resource is DISABLED (value is N) for security reason as per Default setting in yfs.properties file as per below
## PROPERTY_START
## PROPERTY_NAME: yfs.uidev.refreshResources
## DATABASE_SUPPORT: Y
## EXTENDED_PROPERTY: N
## MODIFIABLE: Y
## MODIFIABLE_AT_RUNTIME: N
## SERVER_OVERRIDE: N
## USER_OVERRIDE: N
## PROPERTY_GROUP: Implementation
## PROPERTY_TYPE: Boolean
## PROPERTY_PERMISSIBLE_VALUES: Y, N
## PROPERTY_DESCRIPTION
## This property can be set to Y when developing and customizing the Application Console UI.
## IMPORTANT: This property should NOT be set to Y for live production systems because the refresh only
## works for a single user development environment.
## Valid values:
## Y: Refresh actions will be available within the Resource Configurator screens. These actions
## can be used to refresh the resources used in the Console UI Framework without having to restart the
## application server.
## N: (default) The actions will be disabled, and it will be necessary to restart the application
## server whenever any resource is changed within the configurator.
yfs.uidev.refreshResources=N
## PROPERTY_END
In case of any new resource/entity creation or modify existing resource/entity we have to click "Refresh resource" button in Application Configurator -> Resource Hierarchy
To Enable it, override the properties in properties/customer_overrides.properties file and then restart Application Server (JBOSS/WebLogic/WebSphere) whichever you use.
#Enable Refresh Resource
yfs.yfs.uidev.refreshResources=Y
Note: In this context, resource which could be Entity/Search View/Details View/List View/API/Action button etc., which is present in Resource Hierarchy. When there is a change happen we have to refresh so that the changes will reflect in Console screen.
Also, after REFRESH we have logout and login again from Console/RF screen. Also, after making changes in properties we have to close the Application Configurator and open it again as a Best Practise.
## PROPERTY_START
## PROPERTY_NAME: yfs.uidev.refreshResources
## DATABASE_SUPPORT: Y
## EXTENDED_PROPERTY: N
## MODIFIABLE: Y
## MODIFIABLE_AT_RUNTIME: N
## SERVER_OVERRIDE: N
## USER_OVERRIDE: N
## PROPERTY_GROUP: Implementation
## PROPERTY_TYPE: Boolean
## PROPERTY_PERMISSIBLE_VALUES: Y, N
## PROPERTY_DESCRIPTION
## This property can be set to Y when developing and customizing the Application Console UI.
## IMPORTANT: This property should NOT be set to Y for live production systems because the refresh only
## works for a single user development environment.
## Valid values:
## Y: Refresh actions will be available within the Resource Configurator screens. These actions
## can be used to refresh the resources used in the Console UI Framework without having to restart the
## application server.
## N: (default) The actions will be disabled, and it will be necessary to restart the application
## server whenever any resource is changed within the configurator.
yfs.uidev.refreshResources=N
## PROPERTY_END
In case of any new resource/entity creation or modify existing resource/entity we have to click "Refresh resource" button in Application Configurator -> Resource Hierarchy
#Enable Refresh Resource
yfs.yfs.uidev.refreshResources=Y
Note: In this context, resource which could be Entity/Search View/Details View/List View/API/Action button etc., which is present in Resource Hierarchy. When there is a change happen we have to refresh so that the changes will reflect in Console screen.
Also, after REFRESH we have logout and login again from Console/RF screen. Also, after making changes in properties we have to close the Application Configurator and open it again as a Best Practise.
