Support Of Siebel Product Configurator User Interface Modifications
(Doc ID 967322.1)
Last updated on APRIL 30, 2018
Applies to:Siebel eConfigurator - Version 7.5.2  and later
Siebel Product Configurator - Version 7.5.2  and later
Information in this document applies to any platform.
User Interface Artifacts - Definition
This document is applicable to user interface artifacts of the Siebel Product Configurator. The purpose of this document is to clarify Oracle’s support policy with respect to customizations done to following artifacts:
- Siebel Web Templates (SWT):
These files have following naming convention: eCfg<name of function>.swt (i.e. eCfgProductSingleJS.swt). They can be found in directories
- siebsrvr/webtemplates for server installation
- <client directory>/webtemplates for dedicated client installation
User Interface Artifacts - Technology
In addition Siebel web technology, which is implemented by the SWSE and the Siebel Web Engine, is invoked after a user constructs a user interface for each customizable product using specific Siebel Web Templates and the views of the screen ‘Administration – Product Administration’ which are specific to building the user interface. A key feature includes the ability not to define a customer user interface for a given product but instead to allow the application to render a ‘default’ user interface. All of these features are described in details in Siebel Product Administration Guide. The ‘default’ user interface is important because its controls will be referred later again.
User Interface Artifacts – Supported Modifications
All modifications implemented through the instructions found in the Siebel Product Administration Bookshelf will be fully supported by all Oracle support agreements. This includes what is found in the following chapters:
- Creating Custom Configurator User Interfaces
- Configurator UI Properties
- Configurator Web Templates
User Interface Artifacts – Support Process for User Interface Customizations
Customers should be prepared to work with Oracle Support in the following manner when product defects arise using a custom user interface.
- If the outcome is still reproducible with the ‘Test UI’, using default UI artifacts, then a technical service request should be created with all necessary documentation.
- The customer should test the undesirable outcome with a standard user interface to determine if the outcome is still reproducible. The easiest way to do this is to create a ‘Test UI’ which uses the default controls as specified in Siebel Product Administration Guide.
- If the outcome cannot be reproduced with a ‘Test UI’ because of the depth and breadth of customizations, then the customer must back out the latest set of changes in an effort to begin a debugging process of the UI. At this point, the customer may want to involve expertise from a consulting organization to efficiently address the issue.**
- Additionally, the Oracle Advanced Customer Support account management may want a service request created for tracking purposes.
** Options include Oracle Advanced Solution Support Engineering
User Interface Customizations – Reason for Oracle’s Position
The skill set necessary to support the Siebel Product Configurator requires a large body of product knowledge and domain expertise. The expertise crosses business and technical acumen including different sub-systems of the underlying Siebel stack. The Oracle Siebel Support team expects all support engineers to engage with customers at sufficient levels to meet service level agreements and ensure customer satisfaction.
Note: The eco-system has developed a number of best practices and guidelines that customers can attain through a consulting engagement.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|User Interface Artifacts - Definition|
|User Interface Artifacts - Technology|
|User Interface Artifacts – Supported Modifications|
|User Interface Artifacts – Customizations|
|User Interface Artifacts – Support Process for User Interface Customizations|
|User Interface Customizations – Reason for Oracle’s Position|