Enabling development mode

About this task

You can use the Sterling™ Field Sales application in the development mode, where all JS and CSS files are loaded as non-minified files. This helps you to debug the application in runtime.

Procedure

Enable the development mode for the Sterling Field Sales application in one of the following ways:
  • Through JVM Argument

    Specify the JVM argument, devmode. This argument can have either true or false as the value. For example, devmode=true

    • If Ddevmode=true and customization is enabled through customer_overrides.properties, the application considers the customizations in the ifs-dev-ext directory.
    • If Ddevmode is not enabled and customization is enabled through the customer_overrides.properties, the application considers the customizations in the ifs-ext directory.
    • If customization is disabled in the customer_overrides.properties and devmode is enabled, the application considers the customizations in the ifs-dev directory.
  • Through request parameter
    Specify the request parameter before the # in the application URL. If the JVM argument is not passed, pass the request parameter to enable the development mode as shown in the following example:
    https://<hostname:port>/<context>/?devmode=true#

What to do next

Note: If devmode is not enabled, skip the steps mentioned in this section.
  1. Once you are ready with your customization changes and you want to deploy the changes in a production environment, build the development mode UI artifacts by running the gulp build-dev command from the <cpq_temp>/IBMFieldSales_UI directory.
  2. The development mode UI artifacts are built in the <cpq_temp>/IBMFieldSales_UI/build-dev directory. Copy the contents of this directory, excluding the index.html file, to the <INSTALL_DIR>/repository/eardata/ifs/extn/ifs-dev-ext directory. Create the ifs-dev-ext directory, if it does not exist.