Property management guidelines

You can consult the following guidelines when working with property management.

  • If database property management is enabled and properties are loaded to the database the Sterling™ Order Management System Software application returns the value set in the database for a property. Even if the customer_overrides.properties file exists, the application continues to return the factory value until the overrides are imported to the database. Therefore, you must import your property overrides specified in customer_overrides.properties to the database to attain the expected behavior.
  • The customer_overrides.properties file approach continues to be supported and as mentioned earlier, the factory value can be overridden by importing customer_overrides.properties. After the import, it is recommended to use the database for further overrides. However, the properties which are not present in the database can continue to be managed in files.
  • The import mode always overwrites the property value in the database with the value set in the customer_overrides.properties file, which means that the values set in the database might be lost if import process is run again. Therefore, it is recommended that you remove the property from the customer_overrides.properties file when you start using the database for managing that property.
  • If a property you use in the customer_overrides.properties file is not found in the default files or database, it cannot be managed using import mode. You must either retain it in the customer_overrides.properties file or insert it into the database using the manageProperty API, along with the proper metadata.
  • The CUSTOM properties used in the customization logic can also be inserted into the database using manageProperty API.
  • The override flags in the property metadata indicates whether a property has been overridden for a server or user.