Launching Sterling Configurator from Sterling Call Center

Edit online

The logic implemented to launch the Sterling Configurator from the Sterling Call Center application is described in this topic.

Prerequisites

Ensure you perform the following tasks:
  1. Model your products using Visual Modeler
  2. Import configurator models. For more information, see Import a model group or model.
  3. Configure properties to integrate Sterling Configurator with Sterling Call Center
    1. Add the following properties to the customer_overrides.properties file in the <OMS_Runtime>.
      • yfs.yic.omniconfigurator.<ENTERPRISE_CODE>.enabled: Set the value to true or false if you want to enable or disable the Sterling Configurator integration. For example: yfs.yic.omniconfigurator.Matrix.enabled=true
      • yfs.yic.omniconfigurator.<ENTERPRISE_CODE>.url=<OMNI_CONFIGURATOR_URL>: Set the value to the server URL where Sterling Configurator application is hosted. For example: yfs.yic.omniconfigurator.Matrix.url=http://<hostname>:<portnumber>/configurator
      • yfs.yic.omniconfigurator.<ENTERPRISE_CODE>.orgCode=<OMNI_CONFIG_ORG_CODE>: Set the value to the organization code used in Sterling Configurator configuration when creating a storefront. For example: yfs.yic.omniconfigurator.Matrix.orgCode=Matrix
    2. Configure tenant properties appropriately. For more information, see Adapter properties
    3. Build and deploy customizations. For more information see Deploying customization
  4. Integrate Omni-Configurator with Sterling Business Center
  5. Configure bundle products in the Business Center appropriately.

You may customize the Sterling Configurator interface to suit your needs. For more information, see Customizing omni-configurator.

Implementation

A struts action is introduced as a part of the integration logic. The struts action is included in the isccs_core_struts.xml file.

When the CSR clicks “Configure Product” or "Reconfigure Product" button from either the Add Products or Product Details screen, the struts action is called with the CSRF token and following parameters:

  • OrganizationCode - The organization which maintains the catalog.
  • ConfigurationKey – The unique key which holds a reference to the configuration of a product.
  • BOMXML – If ConfigurationKey is NULL, the available BOMXML is passed to allow the user to reconfigure an order line. Either ConfigurationKey or BOMXML is passed in the input.
  • ModelName– Complete path of the model stored for a dynamic bundle. For example, Matrix/RefModels/100008
  • ConfigurationDate – The current date.
Struts action: 
<action name="launchconfig" class="com.ibm.isccs.core.struts.SCCSDefaultStrutsAction">

The success of the struts action is mapped to configuremodel_omni.jsp. The logic to map the parameters and load the contents of the Sterling Configurator is part of the JSP file.